dbcve.org
GrafanaApplication

CVE-2026-33381

HIGH · 8.1 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to 11.6.14 / 12.2.8 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
When a user's access to mint tokens for a service account is revoked, it is sometimes still possible to do so for a few seconds after the event. The user will eventually lose access to do this.

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 · moderate confidence

This is a time-of-check to time-of-use (TOCTOU) or authorization cache propagation vulnerability in the token minting system for service accounts. When an administrator revokes a user's permission to mint tokens, the revocation does not take effect immediately due to caching or asynchronous propagation, creating a window of several seconds where the user can still mint tokens despite the revocation.

MitigationImplement synchronous, immediate invalidation of cached permissions upon revocation rather than relying on eventual consistency. Alternatively, add a secondary authorization check immediately before the mint operation that queries the current revocation state.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GrafanaApplication
Affected:>= 11.6.0, < 11.6.14>= 12.2.0, < 12.2.8>= 12.3.0, < 12.3.6>= 12.4.0, < 12.4.3>= 13.0.0, < 13.0.1

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Identify installed Grafana version
    Run 'grafana-server -v' or check the version through the admin UI at /api/health or from package manager. Compare the version number to the affected ranges: 11.6.0-11.6.13, 12.2.0-12.2.7, 12.3.0-12.3.5, 12.4.0-12.4.2, and 13.0.0.
    Affected if The installed version falls within any of these ranges and the token minting service is in use.
  2. Confirm service account token minting is enabled
    Check the Grafana configuration file (grafana.ini or environment variables) for [serviceAccounts] enabled setting or examine if any service accounts exist in the system via the API at /api/serviceaccounts.
    Affected if Service accounts are enabled and tokens can be minted by users with appropriate permissions.
  3. Review authorization configuration for caching settings
    Examine the Grafana configuration file for any authz.* settings or authorization-related caching parameters that control how long permission changes take effect.
    Affected if Authorization caching or delayed revocation propagation is configured, extending the revocation window.
  4. Inspect token minting audit logs
    Query the Grafana audit logs or unified telemetry for events related to service account token creation (action: create-token) occurring after permission revocation events.
    Affected if Tokens were minted within several seconds after a revoke-permission event for the same user/service account.
  5. Check for recent permission revocation events
    Review Grafana logs, audit trails, or API access logs for user permission modifications to service accounts, particularly revoke or remove-permission operations.
    Affected if Permission revocations have occurred and the system uses token minting with the affected Grafana versions.

A user is affected if they run a Grafana version within the listed ranges and use the service account token minting feature, with authorization caching that delays revocation propagation.

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
Upgrade available Upgrade to 11.6.14 / 12.2.8 / 12.3.6 or later
Fixed in 11.6.1412.2.812.3.6
Interim mitigation

Implement synchronous, immediate invalidation of cached permissions upon revocation rather than relying on eventual consistency. Alternatively, add a secondary authorization check immediately before the mint operation that queries the current revocation state.

Recommended fix High confidence

Grafana 11.6.14+, 12.2.8+, 12.3.6+, or 12.4.3+ (depending on your version branch)

  1. 1. Identify the currently installed Grafana version by checking the grafana-server version or configuration
  2. 2. Determine which version branch you are running (11.6.x, 12.2.x, 12.3.x, or 12.4.x)
  3. 3. For Grafana 11.6.x: upgrade to version 11.6.14 or later
  4. 4. For Grafana 12.2.x: upgrade to version 12.2.8 or later
  5. 5. For Grafana 12.3.x: upgrade to version 12.3.6 or later
  6. 6. For Grafana 12.4.x: upgrade to version 12.4.3 or later
  7. 7. After upgrading, verify that service account token minting permissions are properly and immediately revoked when access is removed
  8. 8. Review audit logs to confirm the fix is working as expected
Caveat Minor version upgrades within the same major version typically have minimal breaking changes; review Grafana release notes for any deprecation notices

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

Fix this in Grafana Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33381 — 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-33381 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