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


- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-9857-5m9p-q7m3

## What is CVE-2026-124848?

CVE-2026-124848 is a medium-severity vulnerability in Amazon Kiro CLI, published on 10 Nov 2026. 

### Official description

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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-124848?


## How do I fix CVE-2026-124848?

No fix has been published for CVE-2026-124848 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124848 being exploited?

There is no known exploitation of CVE-2026-124848 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124848 and fix it if it is affected.

What it is: CVE-2026-124848 is a medium-severity vulnerability in Amazon Kiro CLI, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124848 in the wild and no public exploit code.

Affected product: Amazon Kiro CLI. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124848/ (Markdown: https://insights.sbomify.com/CVE-2026-124848/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124848
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124848
- OSV: https://osv.dev/vulnerability/CVE-2026-124848

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124848/
Summaries are generated and may contain mistakes; the official description above is the record.