AWS Kiro CLI up to 1.27.x authorization

Summaryinfo

A vulnerability was found in AWS Kiro CLI up to 1.27.x. It has been classified as problematic. This issue affects some unknown processing. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2026-9255. Local access is required to approach this attack. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in AWS Kiro CLI up to 1.27.x. It has been rated as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Missing input source validation in the tool authorization prompt in Kiro CLI before 1.28.0 allows a local attacker to execute arbitrary tools, including shell commands, without user approval by crafting content that is piped to kiro-cli via stdin. We recommend you to upgrade to kiro-cli version 1.28.0 or later.

The advisory is shared at kiro.dev. The identification of this vulnerability is CVE-2026-9255 since 05/21/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.28.0 eliminates this vulnerability. The upgrade is hosted for download at kiro.dev.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-31471). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• AWS

Name

• Kiro CLI

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion