LiveActive security incident?Get immediate response
CVE Record

CVE-2026-0830: Command Injection in Kiro GitLab Merge Request Helper

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.

HighCVSS 8.4Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2026-0830 affects AWS Kiro IDE before version 0.6.18. A malicious workspace folder name could trigger command injection in the GitLab Merge Request helper when a user opens that workspace. Business urgency is high for teams using Kiro because successful exploitation could run arbitrary commands on a developer workstation.

Executive priority

Patch promptly where Kiro is used by engineering teams. This is not described as remotely exploitable without user action, but developer workstations often hold credentials and source access, making arbitrary command execution a meaningful business risk.

Technical view

The issue is CWE-78 command injection in Kiro IDE’s GitLab Merge-Request helper. The published CVSS 4.0 score is 8.4, with local attack vector and required user interaction. The described trigger is processing specially crafted workspace folder names in Kiro versions before 0.6.18.

Likely exposure

Exposure is most likely on developer workstations running Kiro IDE before 0.6.18, especially where users open untrusted or externally supplied workspace folders. The source bundle does not identify server-side exposure or affected products beyond Kiro IDE.

Exploitation context

Sources describe exploitation requiring a user to open a maliciously crafted workspace. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Treat untrusted project workspaces as the key risk path.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, AWS bulletin, and Kiro changelog reference. No exploit details, public exploitation claims, or compensating controls beyond updating are provided in the source bundle.

Mitigation direction

  • Update Kiro IDE to the latest version, at least beyond the affected pre-0.6.18 releases.
  • Prioritize updates on developer machines handling external repositories or shared workspaces.
  • Review AWS and Kiro vendor guidance for any additional recommendations.

Validation and detection

  • Inventory endpoints with Kiro IDE installed.
  • Confirm installed Kiro versions are 0.6.18 or later.
  • Check whether developers open untrusted workspace folders in Kiro.
  • Review the AWS bulletin and Kiro changelog for environment-specific guidance.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-78: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-0830 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.4High
CVSS 4.0 vector shape for CVE-2026-0830Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AWSKiro IDE0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-78 · source CWE mapping

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.