# CVE-2026-10591: Kiro IDE Insufficient File Write Restrictions to Execution-Sensitive Paths


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-83m8-c7v3-rw3w

## What is CVE-2026-10591?

CVE-2026-10591 is a high-severity vulnerability in AWS Kiro IDE, published on 2 Jun 2026. 

### Official description

Insufficient access control restrictions in the file write tool in Amazon Kiro IDE before version 0.11 might allow remote unauthenticated actors to execute arbitrary commands via crafted instructions that cause writes to execution-sensitive paths  (such as .vscode/tasks.json), enabling auto-execution on folder open.

To remediate this issue, users should upgrade to Kiro IDE version 0.11 or later.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Amazon Kiro Ide.

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

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

## Is CVE-2026-10591 being exploited?

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

## Other vulnerabilities in AWS Kiro IDE

- [CVE-2026-18656](https://insights.sbomify.com/CVE-2026-18656/): Executable Resolution from Untrusted Project Directory in Kiro IDE on Windows (high 8.5)
- [CVE-2026-0830](https://insights.sbomify.com/CVE-2026-0830/): Command Injection in Kiro GitLab Merge Request Helper (high 8.4)
- [CVE-2026-89332](https://insights.sbomify.com/CVE-2026-89332/): Kiro IDE Sensitive Workspace Data Exfiltration via Agent-Written Workspace Configuration (medium 6.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10591 is a high-severity vulnerability in AWS Kiro IDE, published on 2 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-10591 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-10591/ (Markdown: https://insights.sbomify.com/CVE-2026-10591/index.md)
```

## Sources

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

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