# CVE-2026-4295: Arbitrary code execution via crafted project files in Kiro IDE

> Remote attackers can execute arbitrary code by tricking users into opening malicious project files that bypass workspace trust protections in Kiro IDE.

- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Mar 2026
- **Updated:** 18 Mar 2026
- **Also known as:** GHSA-qpcc-2ccj-gp68

## What is CVE-2026-4295?

CVE-2026-4295 is a high-severity code injection vulnerability in AWS Kiro IDE, published on 17 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Improper trust boundary enforcement in Kiro IDE before version 0.8.0 on all supported platforms might allow a remote unauthenticated threat actor to execute arbitrary code via maliciously crafted project directory files that bypass workspace trust protections when a local user opens the directory.

To remediate this issue, users should upgrade to version 0.8.0 or higher.

Weakness: CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

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


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

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

## Is CVE-2026-4295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-4295 is a high-severity code injection vulnerability in AWS Kiro IDE, published on 17 Mar 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-4295 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-4295/ (Markdown: https://insights.sbomify.com/CVE-2026-4295/index.md)
```

## Sources

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

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