Read the docs

Incorrect default permissions expose Kiro CLI session transcripts

Priority LOW 29CWE-276Published · Updated

Key facts

Attack vector
Local
Privileges required
Low
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and Linux creates local session storage files with incorrect default permissions. An unauthenticated local user on the same host could read the user's session transcripts and prompt history, including any credentials or source code they contain. This is caused by incorrect default permissions (CWE-276).

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

Description from the CNA

Incorrect default file permissions in Kiro CLI (formerly Amazon Q Developer CLI) before version 2.27.0 on macOS and Linux might allow other local users on the same host to read a user's session transcripts and prompt history, including any credentials or source code they contain. The CLI created its local session storage files with permissions that made them readable by all local users. To remediate this issue, users should upgrade to Kiro CLI version 2.27.0 or later and launch it once. Users who ran Amazon Q Developer CLI 1.16.0 through 1.19.x should also delete the ~/.aws/amazonq/.cli_bash_history file or restrict it to the owner.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00109 1st percentileScored 2026-11-16
Fix Fixed Kiro CLI (Amazon): 2.27.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
AWSKiro CLI1.16.0 to before 2.27.02.27.0Patch availableCNA
  • Kiro CLI VendorAWS Affected 1.16.0 to before 2.27.0 Fixed in 2.27.0 Patch available CNA

Remediation

Upgrade Kiro CLI to version 2.27.0 or later and launch it once. Users who ran Amazon Q Developer CLI 1.16.0 through 1.19.x should also delete the ~/.aws/amazonq/.cli_bash_history file or restrict it to the owner.

Written with Claude Haiku 5.5 from the sources below · 2026-11-11

  • Fix · CNA Kiro CLI (Amazon) Fixed in 2.27.0

Timeline

  1. 2026-11-10 Threatist record created from CVE-2026-124848
  2. 2026-11-10 Alias added: GHSA-9857-5m9p-q7m3
  3. 2026-11-12 Priority changed: MEDIUM → LOW
  4. 2026-11-16 CISA SSVC decision points changed

References

  • TI-2026-23989 Incorrect resource transfer in Linux kernel algif_aead KEVCVSS 3.1HIGH 7.8
  • TI-2023-23979 HTTP/2 request cancellation lets attackers exhaust server resources KEVCVSS 3.1HIGH 7.5
  • TI-2024-18648 Amazon AWS Amplify CLI before 12.10.1 incorrectly configures the role trust policy of IAM… CVSS 3.1CRITICAL 9.8
  • TI-2024-05929 Openssh: regresshion - race condition in ssh allows rce/dos CVSS 3.1HIGH 8.1
  • TI-2025-03847 Input validation issue in AWS Amplify Studio UI component properties CVSS 4.0CRITICAL 9.0
  • TI-2026-11603 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF CVSS 4.0HIGH 7.9
See all 397 →

Sources