CVE-2026-124848mediumData leakage2026-11-10
CVE-2026-124848: Kiro CLI (formerly Amazon Q Developer CLI) left session transcripts and prompt history readable by other local users
Kiro CLI before 2.27.0 on macOS and Linux created its session transcript and prompt history files with permissions that let other local users on the same machine read them, including any credentials or source code in them. Upgrade to 2.27.0 and launch it once; if you used Amazon Q Developer CLI 1.16.0 to 1.19.x, also delete or lock down ~/.aws/amazonq/.cli_bash_history.
What it is
The CLI's local session storage files were created readable by all local users (CWE-276, incorrect default permissions).
AWS bulletin 2026-178-AWS says another local user on a shared host could read a user's transcripts and prompt history.
Kiro CLI 2.27.0's changelog lists 'Local state permissions: Kiro home state and previous session data use owner-only access'.
How to check
- Run kiro-cli --version (or q --version for older installs) and see whether it is below 2.27.0.
- Matters most on shared machines, jump hosts and multi-user dev boxes.
How to fix
- Upgrade to Kiro CLI 2.27.0 or later and launch it once so it fixes the file permissions.
- If you ran Amazon Q Developer CLI 1.16.0 through 1.19.x, delete ~/.aws/amazonq/.cli_bash_history or run chmod go-rwx on it.
- If secrets were pasted into prompts on a shared host, rotate them.
chmod go-rwx ~/.aws/amazonq/.cli_bash_history 2>/dev/null
ls -l ~/.aws/amazonq/Sources
More advisories for this tool