dbcve.org
Incorrect Default PermissionsWeakness · CWE-276

CVE-2026-11931

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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). To remediate this issue, users should upgrade to Kiro IDE version 0.11.133 or later. After upgrading and restarting the application, the cache file permissions are automatically updated on the next token refresh. Users operating in a multi-user environment can invalidate existing tokens by reauthenticating.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Kiro IDE stored authentication tokens in a cache file with overly permissive world-readable permissions (0644) instead of owner-only access (0600). This allows any local user or process on the same system to read the cached authentication tokens, potentially gaining unauthorized access to user accounts.

MitigationUpgrade to Kiro IDE version 0.11.133 or later, which automatically corrects file permissions on the next token refresh. In shared multi-user environments, reauthenticate to invalidate any tokens that may have been exposed.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Kiro IDE is installed
    Run 'kiro --version' or look for Kiro IDE in your installed applications. Note the version number reported.
    Affected if If Kiro IDE is installed and the version is earlier than 0.11.133, the environment may be vulnerable.
  2. Locate the authentication token cache file
    Search for token cache files in common config directories such as ~/.config/kiro/, ~/.cache/kiro/, or similar paths under your home directory. Look for files named containing 'token', 'auth', or 'cache' in the filename.
    Affected if If a token cache file exists in a world-readable location, it may be accessible to other users.
  3. Verify file permissions on the token cache
    Run 'ls -la <path_to_token_file>' to check the permission bits. Look for the permission string (e.g., -rw-r--r-- indicates 0644).
    Affected if If the permissions show '-rw-r--r--' (0644) or any variant where the 'other' users have read access, the tokens are exposed to local users.
  4. Confirm version is within vulnerable range
    Compare the installed Kiro IDE version to the affected range: any version prior to 0.11.133.
    Affected if If the installed version is below 0.11.133 and a token cache file exists with permissive read access, the system is affected by this vulnerability.

A user is affected if Kiro IDE version is below 0.11.133 and an authentication token cache file exists with permissions allowing read access by other users (0644 or more permissive).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Kiro IDE version 0.11.133 or later, which automatically corrects file permissions on the next token refresh. In shared multi-user environments, reauthenticate to invalidate any tokens that may have been exposed.

Recommended fix High confidence

Kiro IDE version 0.11.133 or later

  1. Upgrade Kiro IDE to version 0.11.133 or later
  2. Restart the application
  3. The cache file permissions will be automatically updated to 0600 on the next token refresh
  4. For multi-user environments, re-authenticate to invalidate any tokens stored with the old insecure permissions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11931 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11931 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data