dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-5429

HIGH · 7.8 CVSS v3.1 Published 2026-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unsanitized input during web page generation in the Kiro Agent webview in Kiro IDE before version 0.8.140 allows a remote unauthenticated threat actor to execute arbitrary code via a potentially damaging crafted color theme name when a local user opens the workspace. This issue requires the user to trust the workspace when prompted. To remediate this issue, users should upgrade to version 0.8.140.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kiro IDE before version 0.8.140 contains a code injection vulnerability in its Agent webview component. When processing color theme names during web page generation, the application fails to sanitize input, allowing a remote unauthenticated attacker to embed malicious code in a crafted theme name. Exploitation requires the victim to open a malicious workspace and trust it when prompted, after which arbitrary code execution occurs.

MitigationUpgrade Kiro IDE to version 0.8.140 or later. Users should exercise caution when prompted to trust untrusted workspaces.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Kiro IDE is installed
    Locate the Kiro IDE installation. On typical systems, look for the executable or check installed programs. On Linux, run 'which kiro' or check /opt/kiro. On Windows, check Program Files. On macOS, check Applications folder.
    Affected if Kiro IDE is not installed on the system
  2. Determine installed Kiro IDE version
    Run Kiro IDE and navigate to Help > About, or run 'kiro --version' from command line if supported. Alternatively, check the version metadata in the application binary or installation directory.
    Affected if The installed version is lower than 0.8.140 (e.g., 0.8.100, 0.8.50, etc.)
  3. Identify workspaces with custom theme configurations
    Locate workspace configuration files. These are typically stored in the workspace directory as .kiro, settings.json, or similar configuration files containing 'theme' or 'colorTheme' entries. Search for files containing theme name definitions within workspace folders.
    Affected if Any workspace contains a theme configuration entry with a non-standard or suspiciously formatted theme name (e.g., containing HTML-like characters or unusually long strings)
  4. Check if Agent webview feature is used
    Review workspace settings or Kiro IDE preferences to determine if the Agent webview component is enabled. This may appear as a setting like 'enableAgent', 'webview', or similar in the workspace or global configuration files.
    Affected if The Agent webview feature is enabled and the user has interacted with or opened affected workspace files

A user is affected if Kiro IDE version is below 0.8.140 AND they have opened and trusted a workspace containing a maliciously crafted theme configuration that triggers the unsanitized render in the Agent webview.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Kiro IDE to version 0.8.140 or later. Users should exercise caution when prompted to trust untrusted workspaces.

Recommended fix High confidence

0.8.140

  1. Check the currently installed version of Kiro IDE
  2. Upgrade Kiro IDE to version 0.8.140 or later
  3. Restart Kiro IDE and verify the new version is running
  4. Exercise caution when opening untrusted workspaces and only trust workspaces when prompted

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5429 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data