Is CVE-2026-124848 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-124848 being exploited in the wild.

How severe is CVE-2026-124848?

High severity, with a CVSS score of 5.5, published 10 November 2026.

How is CVE-2026-124848 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-124848?

Check whether you run Amazon AWS or AWS Kiro CLI at an affected version. 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.

CVE-2026-124848: AWS Kiro CLI incorrect default permissions on session files

CVE-2026-124848 · Severity: high · CVSS 5.5 · Published 2026-11-10

Kiro CLI is a terminal-based AI coding assistant that stores session transcripts and user prompts on disk. Before version 2.27.0, these files were created with overly permissive permissions, allowing any local user on the same machine to read them—potentially exposing credentials, source code, and sensitive API interactions stored in the session history.

Technologies: Amazon AWS. Vendors: Amazon, AWS.

Quick answers

Is CVE-2026-124848 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-124848 being exploited in the wild.
How severe is CVE-2026-124848?: High severity, with a CVSS score of 5.5, published 10 November 2026.
Which products and versions are affected?: AWS Kiro CLI 1.16.0 to 2.26.x.
Is there a fix for CVE-2026-124848?: Yes: fixed in Kiro CLI 2.27.0. Until then: Until upgrading, run "chmod -R go-rwx ~/.kiro" on macOS and Linux to restrict session files to the owner, and set "umask 077" in the shell before launching Kiro CLI to ensure new files are created owner-only. Users of legacy Amazon Q Developer CLI 1.16.0–1.19.x should also run "chmod go-rwx ~/.aws/amazonq/.cli_bash_history". Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-124848 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-124848?: Check whether you run Amazon AWS or AWS Kiro CLI at an affected version. 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.

How to fix

Fixed in: Kiro CLI 2.27.0

Until upgrading, run "chmod -R go-rwx ~/.kiro" on macOS and Linux to restrict session files to the owner, and set "umask 077" in the shell before launching Kiro CLI to ensure new files are created owner-only. Users of legacy Amazon Q Developer CLI 1.16.0–1.19.x should also run "chmod go-rwx ~/.aws/amazonq/.cli_bash_history".

Technical details

Kiro CLI (versions 1.16.0 through 2.26.x) created local session storage files with world-readable permissions on macOS and Linux. An attacker with local access can read session transcript and prompt history files in ~/.kiro/ and ~/.aws/amazonq/, extracting credentials, source code, and model responses. This is a local privilege disclosure vulnerability requiring no authentication but does require pre-existing local access to the host.

Affected products

AWS Kiro CLI 1.16.0 to 2.26.x

Timeline

2026-11-10: disclosed

References

https://aws.amazon.com/security/security-bulletins/rss/2026-178-aws/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.