Arbitrary tool execution via piped approval input
Published May 22, 2026 · Updated May 22, 2026
Missing authorization in Kiro CLI before 1.28.0 allows local users to execute arbitrary tools through content piped over standard input. The tool authorization prompt consumes bytes from the same redirected input stream as untrusted prompt content without validating their source. Exploitation requires a user to pipe attacker-crafted content into the CLI, after which embedded approval input can authorize shell commands without separate consent.
Summary
What happened
Missing authorization in Kiro CLI before 1.28.0 allows local users to execute arbitrary tools through content piped over standard input. The tool authorization prompt consumes bytes from the same redirected input stream as untrusted prompt content without validating their source. Exploitation requires a user to pipe attacker-crafted content into the CLI, after which embedded approval input can authorize shell commands without separate consent.
The record
- CVE
- CVE-2026-9255
- Published
- May 22, 2026
- Updated
- May 22, 2026
- Vendor
- Amazon Web Services
- Product
- Kiro CLI
- Classifications
- CWE-862, CAPEC-233, T1059
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 22, 2026CVE publishedPublication date reported by the CVE source.
- May 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.28.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo