Skip to main content
VulnerabilityPublished Updated

CVE-2026-10591: AWS Kiro IDE · Incorrect Permissions

Affects AWS Kiro IDESource CVE Database V5

0
Compare

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

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.11
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 2 Jun 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 30 Oct 2026.

What to do

Upgrade AWS Kiro IDE to 0.11.

Affected software

ProductAffectedFixed in
AWSKiro IDEAffected
  • <0.11
Fixed in
  • 0.11

AI-suggested

A patch is available. Users should upgrade AWS Kiro IDE to version 0.11 or later to remediate this vulnerability. Since this is a cloud service, AWS manages remediation for the hosted service; users should verify their environment is updated accordingly by consulting the AWS security advisory at https://aws.amazon.com/security/security-bulletins/2026-037-aws/.

Description

CVE-2026-10591 is a high-severity vulnerability in AWS Kiro IDE versions before 0.11. It involves incorrect permission assignment in the file write tool, allowing remote unauthenticated actors to execute arbitrary commands by writing to execution-sensitive paths such as .vscode/tasks.json. This can lead to automatic execution of malicious instructions when a folder is opened. The issue is fixed in version 0.11 and later.

References

Community reviews

Loading reviews…