VulnerabilityPublished 19 Oct 2026

CVE-2026-11931: Kiro IDE · Insecure Permissions on Authentication Token Cache File

Source AWS Security Bulletins

Compare

Not known to be exploited · fixed in 0.11.133 : update affected systems when convenient.

Data as of 30 Oct 2026, 11:52 UTC

Severity

Medium

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.11.133

Exploitation evidence

Disclosed: evidence found.
Public on cve.org; its publication date is not in this record
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

This issue has been officially fixed in Kiro IDE version 0.11.133. Users should upgrade to version 0.11.133 or later to ensure the authentication token cache file permissions are properly restricted. No additional mitigation steps are required beyond applying the official fix.

Description

Bulletin ID: 2026-045-AWS Scope: AWS Content Type: Important (requires attention) Publication Date: 06/15/2026 11:45 AM PDT Description: Kiro IDE is an agentic development environment that makes it easy for developers to ship real engineering work with the help of AI agents. We identified CVE-2026-11931, where incorrect default permissions in Kiro IDE on macOS and Linux before version 0.11.133 could expose the authentication token cache file to other local users or processes via world-readable permissions (0644) instead of owner-restricted permissions (0600). Impacted versions: < 0.11.133 Please refer to the article below for the most up-to-date and complete information related to this AWS Security Bulletin.

Impact

The vulnerability exposes authentication tokens stored in the cache file to other local users or processes on the same system due to overly permissive file permissions. This could lead to unauthorized access to user sessions or credentials if an attacker has local access. However, the impact is limited to local privilege scenarios and does not affect remote exploitation. The severity is considered low.

Summary

Kiro IDE versions prior to 0.11.133 on macOS and Linux platforms set the authentication token cache file permissions to world-readable (0644) instead of owner-restricted (0600). This incorrect default permission setting could allow unauthorized local users or processes to access authentication tokens stored in the cache file. The vulnerability was identified and addressed in version 0.11.133, which enforces stricter file permissions to protect the token cache file from unauthorized access.

References

aws.amazon.com/security/security-bulletins/rss/2026-045-aws/ (opens in a new tab)

Community reviews

Loading reviews…