Kiro IdeApplication · Amazon

CVE-2026-0830

HIGH · 7.8 CVSS v3.1 Published 2026-01-09

Fix available

A fix is available. Upgrade to 0.6.18 or later.

See remediation →

81/100

Remediation priority · High

No privileges

Official description

NVD · unedited

Processing specially crafted workspace folder names could allow for arbitrary command injection in the Kiro GitLab Merge-Request helper in Kiro IDE before version 0.6.18 when opening maliciously crafted workspaces. To mitigate, users should update to the latest version.

Technical summary

dbcve analysis · high confidence

Kiro IDE contains a command injection vulnerability in its GitLab Merge-Request helper component. The vulnerability is triggered when processing specially crafted workspace folder names, allowing an attacker to inject arbitrary commands via malicious workspace paths. The attack requires the user to open a maliciously crafted workspace, indicating a low-complexity attack vector with user interaction requirement.

MitigationUsers should update Kiro IDE to version 0.6.18 or later to remediate this vulnerability. As a precautionary measure, avoid opening workspace folders from untrusted or unknown sources.

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

Affected products & versions

NVD · CPE data

Kiro IdeApplication

Affected:< 0.6.18

CVSS breakdown

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?

dbcve checks

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

Verify Kiro IDE is installed

Check if the Kiro IDE application exists on the system - look for the Kiro binary or application in standard installation directories

Affected if Kiro IDE is present on the system
Determine installed Kiro IDE version

Run the version check command for Kiro IDE (typically --version or -v flag, or check the About section in the IDE)

Affected if The installed version is lower than 0.6.18
Check if GitLab Merge-Request helper is configured

Inspect Kiro IDE settings or configuration files for GitLab integration - look for MR helper, GitLab helper, or merge request related configurations

Affected if GitLab Merge-Request helper feature is enabled or configured in Kiro IDE settings
Review recently opened workspaces

Check workspace history or recent files list in Kiro IDE for any workspace folders with unusual, unexpected, or suspicious names

Affected if A workspace with a maliciously crafted folder name was opened in Kiro IDE

A user is affected if they have Kiro IDE installed with version lower than 0.6.18 and have opened a workspace with a specially crafted malicious folder name using the GitLab Merge-Request helper feature.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 0.6.18 or later

Fixed in 0.6.18

Interim mitigation

Users should update Kiro IDE to version 0.6.18 or later to remediate this vulnerability. As a precautionary measure, avoid opening workspace folders from untrusted or unknown sources.

Recommended fix High confidence

0.6.18

Check current Kiro IDE version by opening the application and navigating to the About or Preferences section
Download Kiro IDE version 0.6.18 or later from the official source at kiro.dev
Install the update following the standard installation process for your operating system
Verify the installation by checking the version number in the application
Restart the application to ensure the update is fully applied

Caveat Review release notes at kiro.dev for any breaking changes between your current version and 0.6.18

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

Fix this in Kiro Ide Scoped from the published advisory

Consultation2.0 h
Implementation1.0 h
Testing2.0 h
Review / QA1.0 h

6.0 hours of engineering $1,060

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-0830 — 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

Primary sources

aws.amazon.comVendor Advisory
kiro.devRelease Notes
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-0830?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 0.6.18 or later

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 1.3%

Affects: Kiro Ide

Remediation

A high-priority fix

Fix this in Kiro Ide 6 hrs · Low

Typical engagement from $1,060

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-0830 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References