# CVE-2026-18657: Kiro CLI uncontrolled search path element on Windows

Source: https://junglewise.ai/threats/cve-2026-18657-kiro-cli-uncontrolled-search-path-element-on-windows  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-08-04. Updated: 2026-09-25  
License: CC BY 4.0 with a link back

CVE-2026-18657 · Severity: high · CVSS 7.8 · Published 2026-08-04

Kiro CLI is a command-line tool for working with development projects. A flaw in how it searches for executables on Windows allows an attacker to place a malicious executable in a project directory, which gets executed when a user runs Kiro CLI in that directory, bypassing workspace trust protections. An unauthenticated attacker can achieve this remotely by distributing a maliciously crafted project.

Technologies: [Microsoft Windows](https://junglewise.ai/threats/technologies/windows). Vendors: [Microsoft](https://junglewise.ai/threats/vendors/microsoft).

## Quick answers

**Is CVE-2026-18657 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-18657 being exploited in the wild.

**How severe is CVE-2026-18657?** High severity, with a CVSS score of 7.8, published 4 August 2026.

**Which products and versions are affected?** Kiro CLI before 2.10.0.

**Is there a fix for CVE-2026-18657?** A patch was published on 2026-06-26: Version 2.10.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-18657 attacked?** It is attacked with local access, in a software library.

**Am I affected by CVE-2026-18657?** Check whether you run Microsoft Windows. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

The vulnerability is an uncontrolled search path element (CWE-426) in Kiro CLI versions before 2.10.0 on Windows. When Kiro CLI starts in a directory, it resolves executable names by searching the current working directory before system paths, allowing an attacker to place a malicious executable in a project directory that will be executed instead of the legitimate system executable. The attack bypasses workspace trust protections and requires only that a local user starts Kiro CLI in a directory containing the malicious project. An unauthenticated attacker can distribute such projects to achieve arbitrary code execution with the privileges of the local user. The issue is fixed in version 2.10.0 and later.

## Affected products

- Kiro CLI before 2.10.0

## Timeline

- 2026-08-04: disclosed
- 2026-06-26: patched: Version 2.10.0 released

## References

- [https://aws.amazon.com/security/security-bulletins/2026-074-aws/](https://aws.amazon.com/security/security-bulletins/2026-074-aws/)
- [https://kiro.dev/changelog/cli/2-10/](https://kiro.dev/changelog/cli/2-10/)

## Related threats

- [Windows BitLocker heap buffer overflow with physical attack](https://junglewise.ai/threats/cve-2026-97015-heap-based-buffer-overflow-in-windows-bitlocker-allows-an)
- [Microsoft Windows Shell type confusion privilege elevation](https://junglewise.ai/threats/cve-2026-97013-access-of-resource-using-incompatible-type-type-confusion-in)
- [Microsoft Windows VMSwitch out-of-bounds read privilege escalation](https://junglewise.ai/threats/cve-2026-97002-out-of-bounds-read-in-windows-vmswitch-allows-an-authorized)
- [Microsoft Windows USM Communication Manager null pointer dereference](https://junglewise.ai/threats/cve-2026-97000-null-pointer-dereference-in-windows-usm-communication-manager)
- [Microsoft Windows Winsock use after free privilege escalation](https://junglewise.ai/threats/cve-2026-96994-use-after-free-in-winsock-allows-an-authorized-attacker-to)