CVE-2026-11931 - Insecure Permissions on Authentication Token Cache File in Kiro IDE
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.
AI Analysis
Technical 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.
Potential 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.
Mitigation Recommendations
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.
CVE-2026-11931 - Insecure Permissions on Authentication Token Cache File in Kiro IDE
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.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
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.
Potential 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.
Mitigation Recommendations
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.
Technical Details
- Article Source
- {"url":"https://aws.amazon.com/security/security-bulletins/rss/2026-045-aws/","fetched":true,"fetchedAt":"2026-06-15T18:48:00.910Z","wordCount":169}
Threat ID: 6a3048e00b89be688875eef3
Added to database: 06/15/2026, 18:48:00 UTC
Last enriched: 06/15/2026, 18:48:05 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 141
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.