Skip to main content
VulnerabilityPublished

CVE-2026-95985: AWS Kiro IDE · Untrusted Functionality Inclusion

Affects AWS Kiro IDESource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 1.0.242 soon.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.242
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade AWS Kiro IDE to 1.0.242.

Affected software

ProductAffectedFixed in
AmazonKiro IDEAffected
  • <1.0.242
Fixed in
  • 1.0.242

AI-suggested

Upgrade Amazon Kiro IDE to version 1.0.242 or later. Users who have run the agent in an untrusted workspace on earlier versions should review the global Kiro configuration directory (~/.kiro) for any unauthorized entries and remove them as necessary.

Description

The file write tool in Amazon Kiro IDE versions before 1.0.242 might allow remote unauthenticated actors to inject crafted instructions into the agent's context. When a user runs the agent in a crafted repository as an untrusted workspace, sending any message can cause agent modifications to auto-loaded global configuration paths. We recommend you upgrade to Kiro IDE version 1.0.242 or later. Users who ran the agent in an untrusted workspace on an earlier version should also review the global Kiro configuration directory (~/.kiro) for entries they did not create.

References

Community reviews

Loading reviews…