CVE-2026-124848: Incorrect default permissions on session transcripts and prompt history in Kiro CLI

Q: Who is exposed to this issue?

Users of Kiro CLI before version 2.27.0 on macOS or Linux are exposed if other local users can access the same host. The risk is that those users can read session transcripts and prompt history stored with overly permissive permissions.

Q: What does an attacker need to exploit it?

An attacker needs local access as another user on the affected macOS or Linux host. No user interaction is required, but the attacker must be able to read the affected local storage files.

Q: Are credentials or source code at risk?

They may be, if they were included in session transcripts or prompt history. The affected files can contain credentials or source code entered or recorded during CLI use.

Q: What should be done if the CLI was previously used?

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

Published Nov 10, 2026

Updated

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/.clibashhistory file or restrict it to the owner.

Affected Software

1 affected component

Amazon Kiro Cli<2.27.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

Upgrade
Upgrade Kiro CLI to a version that resolves this vulnerability.
Fixed in 2.27.0
Operational
After upgrading, launch Kiro CLI once. If Amazon Q Developer CLI 1.16.0 through 1.19.x was used, delete ~/.aws/amazonq/.cli_bash_history or restrict the file to the owner.

Event History

Nov 10, 2026

CVE Published

via MITRE·08:03 PM

Data Sourced

via MITRE·08:03 PM

DescriptionSeverityWeakness

Frequently Asked Questions

Who is exposed to this issue?

Users of Kiro CLI before version 2.27.0 on macOS or Linux are exposed if other local users can access the same host. The risk is that those users can read session transcripts and prompt history stored with overly permissive permissions.

What does an attacker need to exploit it?

An attacker needs local access as another user on the affected macOS or Linux host. No user interaction is required, but the attacker must be able to read the affected local storage files.

Are credentials or source code at risk?

They may be, if they were included in session transcripts or prompt history. The affected files can contain credentials or source code entered or recorded during CLI use.

What should be done if the CLI was previously used?

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

CVE-2026-124848: Incorrect default permissions on session transcripts and prompt history in Kiro CLI

Affected Software

Remediation

Event History

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

Are credentials or source code at risk?

What should be done if the CLI was previously used?

Company

Resources

Contact

Frequently Asked Questions

Who is exposed to this issue?

What does an attacker need to exploit it?

Are credentials or source code at risk?

What should be done if the CLI was previously used?