# CVE-2026-33381: Users can generate Service Account tokens after permissions removal

> Attackers can generate service account tokens briefly after permission revocation due to a race condition, potentially bypassing access controls.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2026-33381, GHSA-wfhv-mj62-f5xh, GO-2026-5708, MINI-329f-xq8m-9f8r, MINI-5w6x-94pg-6rg5, MINI-68cf-4rcp-cjp7, MINI-79qf-h7x3-vfvq, MINI-8j23-3523-24c3, MINI-8v9v-57p9-rx26, MINI-9p8h-5rvx-2cq9, MINI-g3r4-9vxg-3373, MINI-grx7-99wr-xxv6, MINI-gv2r-cp55-rjj6, MINI-h49r-x2vc-84jw, MINI-hw95-ccvj-9mj7, MINI-q856-8p9j-qv5c, MINI-w5w2-86mc-7hpx, MINI-x37x-jx52-8c87, MINI-xpx8-9xhc-x244, UBUNTU-CVE-2026-33381

## What is CVE-2026-33381?

CVE-2026-33381 is a medium-severity vulnerability in Grafana Grafana, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-33381?

4 open source packages ship an affected version, including github.com/grafana/grafana and grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/grafana/grafana` | Go | All versions | None |
| `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260513165311-fb7336fc36c1 |
| `github.com/grafana/grafana` | Go | All versions | 1.9.2-0.20260513165311-fb7336fc36c1 |
| `grafana` | Bitnami | From 9.2.0 | 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.1 |

Products: Grafana Grafana.

## How do I fix CVE-2026-33381?

Upgrade github.com/grafana/grafana to 1.9.2-0.20260513165311-fb7336fc36c1 or later.

## Is CVE-2026-33381 being exploited?

There is no known exploitation of CVE-2026-33381 in the wild and no public exploit code.

## Other vulnerabilities in Grafana Grafana

- [CVE-2021-43798](https://insights.sbomify.com/CVE-2021-43798/): Grafana Path Traversal (high 7.5, exploited in the wild)
- [CVE-2025-41115](https://insights.sbomify.com/CVE-2025-41115/): Incorrect privilege assignment (critical 10.0)
- [CVE-2022-39328](https://insights.sbomify.com/CVE-2022-39328/): Grafana vulnerable to race condition allowing privilege escalation (critical 9.8)
- [CVE-2022-28660](https://insights.sbomify.com/CVE-2022-28660/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-26148](https://insights.sbomify.com/CVE-2022-26148/): Information disclosure in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33381 and fix it if it is affected.

What it is: CVE-2026-33381 is a medium-severity vulnerability in Grafana Grafana, published on 13 May 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33381 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/grafana/grafana (Go): affected all versions; no fix listed
- github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260513165311-fb7336fc36c1
- github.com/grafana/grafana (Go): affected all versions; fixed in 1.9.2-0.20260513165311-fb7336fc36c1
- grafana (Bitnami): affected from 9.2.0; fixed in 11.6.14, 12.2.8, 12.3.6, 12.4.3, 13.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33381/ (Markdown: https://insights.sbomify.com/CVE-2026-33381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33381
- OSV: https://osv.dev/vulnerability/CVE-2026-33381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33381/
Summaries are generated and may contain mistakes; the official description above is the record.