CVE-2026-33381: Grafana improper access control in service account token minting

CVE-2026-33381 · Severity: medium · CVSS 5.9 · Published 2026-05-13

Grafana is an open-source platform for monitoring and observability. A security flaw was identified where users whose permissions to create service account tokens have been revoked can still generate new tokens for a short window of time. This could allow a recently restricted user to maintain unauthorized access to the system by creating long-lived credentials before the revocation fully takes effect.

Technologies: github.com/grafana/grafana (Go). Vendors: Go.

Quick answers

Is CVE-2026-33381 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33381 being exploited in the wild.
How severe is CVE-2026-33381?
Medium severity, with a CVSS score of 5.9, published 13 May 2026.
Which products and versions are affected?
github.com/grafana/grafana (Go) < 1.9.2-0.20260513165311-fb7336fc36c1, SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.9.2-0.20260513165311-fb7336fc36c1.
Is there a fix for CVE-2026-33381?
Yes. github.com/grafana/grafana (Go): upgrade to 1.9.2-0.20260513165311-fb7336fc36c1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33381 attacked?
It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-33381?
Check whether you run github.com/grafana/grafana (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • github.com/grafana/grafana (Go): upgrade to 1.9.2-0.20260513165311-fb7336fc36c1 or later
    go get github.com/grafana/grafana@v1.9.2-0.20260513165311-fb7336fc36c1

Technical details

A race condition or caching delay in Grafana's Role-Based Access Control (RBAC) system allows for improper access control (CWE-284). When a user's permission to 'mint' or generate tokens for a service account is revoked, the change is not immediately enforced across all sessions or nodes, leaving a window of several seconds where token generation is still possible. An attacker with high privileges (the initial permission to create tokens) can exploit this by automating token creation immediately after their access is revoked. This allows them to maintain persistent access via a new service account token despite the administrative action to restrict them. The fix involves improving RBAC cache invalidation on permission changes.

Affected products

  • Grafana Grafana OSS 9.2.0 <= 11.6.14; 12.0.0 <= 12.2.8; 12.3.0 <= 12.3.6; 12.4.0 <= 12.4.3; 13.0.0 <= 13.0.1

Identifiers

  • CVE-2026-33381
  • GHSA-wfhv-mj62-f5xh
  • GO-2026-5708

Timeline

  • 2026-05-13: disclosed
  • 2026-05-13: patched
  • 2026-05-13: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.