CVE-2026-124848 amazon kiro cli: Incorrect Default Permissions

6.8 mediumEPSS 0.1%

Medium (6.8) in amazon kiro cli. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page

Severity
Ask an AI about this CVE
Affected
Versions
Attack patterns (CAPEC)
References
Your exposure

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.

Severity

CVSS 4.0

6.8 medium

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

5.5 medium

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS: 0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE: CWE-276 Incorrect Default Permissions
OWASP Top 10: A01:2025 Broken Access Control
Published: 2026-11-10 20:19 UTC
Modified: 2026-11-12 19:24 UTC
Assigned by: AMZN (CNA)
NVD analysis: Awaiting analysis
Record from: the NVD, synced 2026-11-12 19:53 UTC

Ask an AI about this CVE

ChatGPT Claude Google AI Mode

Show the prompt

Explain CVE-2026-124848 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-124848?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-124848?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-124848 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-124848](https://cve.bz/cve/badge/CVE-2026-124848.svg)](https://cve.bz/cve/CVE-2026-124848)

HTML:

<a href="https://cve.bz/cve/CVE-2026-124848"><img src="https://cve.bz/cve/badge/CVE-2026-124848.svg" alt="CVE-2026-124848"></a>

Affected

amazon:kiro cli

Versions

From the CNA's record in the CVE List.

Product	Affected
Amazon Kiro CLI	from 1.16.0 before 2.27.0

Attack patterns (CAPEC)

CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stack JSON