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

Published Mar 17, 2026
·
Updated

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.

Affected Software

1 affected component
Kiro Kiro IDE<0.8.0

Event History

Mar 17, 2026
CVE Published
via MITRE·07:11 PM
Data Sourced
via MITRE·07:11 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Jul 30, 58194
Event
via FIRST·02:41 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4295?

CVE-2026-4295 has a high severity rating as it allows for arbitrary code execution.

2

How do I fix CVE-2026-4295?

To fix CVE-2026-4295, update Kiro IDE to version 0.8.0 or later.

3

What types of systems are affected by CVE-2026-4295?

CVE-2026-4295 affects all supported platforms running Kiro IDE versions prior to 0.8.0.

4

Who can exploit CVE-2026-4295?

CVE-2026-4295 can be exploited by remote unauthenticated threat actors using malicious project directory files.

5

What is the main risk associated with CVE-2026-4295?

The main risk associated with CVE-2026-4295 is potentially allowing arbitrary code execution on vulnerable systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203