# CVE-2026-11931: Insecure Permissions on Authentication Token Cache File in Kiro IDE

> Local attackers can read authentication tokens from Kiro IDE due to insecure file permissions, potentially leading to account takeover.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jun 2026
- **Updated:** 15 Jun 2026
- **Also known as:** GHSA-vjw4-v5gx-3v45

## What is CVE-2026-11931?

CVE-2026-11931 is a medium-severity vulnerability in AWS Kiro IDE, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect default permissions in Kiro IDE on macOS and Linux before version 0.11.133 could expose the authentication token cache file to other local users or processes via world-readable permissions (0644) instead of owner-restricted permissions (0600).

To remediate this issue, users should upgrade to Kiro IDE version 0.11.133 or later. After upgrading and restarting the application, the cache file permissions are automatically updated on the next token refresh. Users operating in a multi-user environment can invalidate existing tokens by reauthenticating.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2026-11931 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11931 is a medium-severity vulnerability in AWS Kiro IDE, published on 15 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11931 in the wild and no public exploit code.

Affected product: AWS Kiro IDE. 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-11931/ (Markdown: https://insights.sbomify.com/CVE-2026-11931/index.md)
```

## Sources

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

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