What is the CVSS score of CVE-2026-4295?

CVE-2026-4295 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-4295?

Yes, a public proof-of-concept exploit is available for CVE-2026-4295. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-4295?

Within 24 hours: Inventory all Kiro IDE installations across development teams and identify current versions. Within 7 days: Upgrade all instances to Kiro IDE 0.8.0 or later; validate upgrade completion across all developers and CI/CD pipelines. Within 30 days: Conduct code review of any projects opened in Kiro IDE from untrusted sources since last verified clean version; scan development systems for indicators of compromise.

Kiro Ide CVE-2026-4295

Q: Which versions of Kiro Ide are affected by CVE-2026-4295?

Kiro IDE versions prior to 0.8.0 contain a trust boundary enforcement flaw that allows remote attackers to execute arbitrary code when users open malicious project directories, directly circumventing…. A patch is available.

EUVD-2026-12638 HIGH

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

2026-03-17 AMZN

RCE AWS Kiro Ide

7.8

CVSS 3.1 · NVD

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Craft malicious project directory files
Exploit

User opens directory in Kiro IDE
Execution

Bypass workspace trust boundary
Impact

Execute arbitrary code with user privileges

Vulnerability Assessment

Weakness	CWE CWE-829 OWASP Top 10:2025 A08:2025 - Software or Data Integrity Failures ASVS 5.0 V15 - Secure Coding and Architecture Trusted source inclusion only
Exploitation Conditions	Local user must open a maliciously crafted project directory in Kiro IDE versions before 0.8.0. Attacker cannot exploit remotely; victim interaction (opening the directory) is required. Affects all supported platforms.
Impact	The CVSS 7.8 score reflects a high severity due to potential for full system compromise (C:H/I:H/A:H), but real-world risk is moderated by requiring local access (AV:L) and user interaction (UI:R). The attack requires no privileges (PR:N) and has low complexity (AC:L), making it straightforward once an attacker can deliver malicious project files. The vulnerability is not listed in CISA KEV indicating no known active exploitation, and no public proof-of-concept has been identified. The SSVC framework would likely categorize this as requiring prompt attention due to the potential for automated exploitation once a user opens the malicious directory, though the local vector and user interaction requirements limit mass exploitation potential.
Exploit ScenarioDerived	An attacker creates a malicious project directory containing specially crafted configuration or script files that exploit the improper trust boundary enforcement. When a developer downloads and opens this project in a vulnerable version of Kiro IDE, the malicious code executes with the user's privileges, potentially installing backdoors or stealing sensitive data. The attack requires the victim to actively open the malicious project, making social engineering or supply chain compromise likely attack vectors.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 17, 2026

A trust boundary enforcement vulnerability in Kiro IDE allows remote attackers to execute arbitrary code when a local user opens a maliciously crafted project directory. The vulnerability affects all versions of Kiro IDE prior to 0.8.0 on all supported platforms and bypasses workspace trust protections designed to prevent unauthorized code execution. While not currently listed in CISA KEV or showing high EPSS scores, the vulnerability enables remote code execution through local user interaction.

RemediationAI

Users should immediately upgrade Kiro IDE to version 0.8.0 or higher as specified in the vendor advisory at https://aws.amazon.com/security/security-bulletins/2026-009-AWS/. Until patching is complete, users should avoid opening project directories from untrusted sources and verify the integrity of project files before opening them in the IDE. Organizations should review the Kiro IDE 0.8.0 changelog at https://kiro.dev/changelog/ide/0-8/ for complete remediation details and any additional security improvements included in the update.

Affected VersionsENISA

Kiro IDE 0.1.0 <0.8.0

Affected Packages

euvd kiro_ide fix: 0.8.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Kiro IDE is an integrated development environment published by AWS, as indicated by the CPE identifier cpe:2.3:a:aws:kiro_ide. The vulnerability stems from CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), where the application fails to properly validate and enforce trust boundaries when processing project directory files. This allows untrusted code or configuration files within a project directory to bypass the workspace trust mechanism that should prevent automatic execution of potentially dangerous operations when opening unfamiliar projects.

Know when Kiro Ide gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 7.8 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:21 EUVD-patch-fix

executive summary

Patch available

Apr 16, 2026 - 05:29 EUVD

0.8.0

CVE Published

Mar 17, 2026 - 19:11 nvd

HIGH 7.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Kiro IDE versions prior to 0.8.0 contain a trust boundary enforcement flaw that allows remote attackers to execute arbitrary code when users open malicious project directories, directly circumventing workspace protections intended to prevent unauthorized execution. This affects all supported platforms and creates significant risk for development teams whose members may unknowingly load compromised projects, potentially compromising source code, build systems, and downstream deployments.

Business Impact: High

Compensating Controls

Apply vendor patch. Until upgraded to 0.8.0 or later: restrict opening of project directories from untrusted or external sources; disable local user workspace opening of projects; require code review of externally-sourced projects before opening in Kiro IDE; monitor IDE process execution for anomalies.

Threat Intelligence Overview

EPSS Score

0.0%

Top 97% exploitable

Exploit

POC

Public exploit code exists

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

GitHub

VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC Yes

EPSS 0.0%

Patch available Yes

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.