Skip to main content
VulnerabilityPublished

CVE-2026-18657: AWS Kiro CLI · Uncontrolled Search Path Element

Affects AWS Kiro CLISource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 2.10.0 soon.

Data as of 2 Nov 2026, 22:58 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.10.0
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade Kiro CLI and amazon/kiro-cli to 2.10.0.

Affected software

ProductAffectedFixed in
AmazonKiro CLIAffected
  • <2.10.0
Fixed in
  • 2.10.0
npmamazon/kiro-clipkg:npm/amazon/kiro-cliOther threatsAffected
  • <2.10.0
Fixed in
  • 2.10.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Amazon Kiro CLI to version 2.10.0 or later, where this vulnerability is fixed. No other mitigation or temporary workaround is indicated in the vendor advisory. Patch status is confirmed by the vendor advisory at https://aws.amazon.com/security/security-bulletins/2026-074-aws/.

Description

An uncontrolled search path element in Kiro CLI before version 2.10.0 on Windows might allow a remote unauthenticated actor to execute arbitrary code via a maliciously crafted project directory containing an executable that bypasses workspace trust protections when a local user starts Kiro CLI in the directory. To remediate this issue, users should upgrade to version 2.10.0 or higher.

References

Community reviews

Loading reviews…