# CVE-2026-21725: Authorization Bypass via TOCTOU in Grafana Datasource Deletion by Name

> An attacker with prior admin access can delete a recreated datasource without permission due to a race condition, requiring strict timing and UID reuse.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Feb 2026
- **Updated:** 27 Aug 2026
- **Also known as:** BIT-grafana-2026-21725, GHSA-w36g-f98m-wm99, MINI-26hr-w278-wh82, MINI-2m4r-wh6v-jrv9, MINI-2wp4-2fv9-5v2j, MINI-3gv6-8c75-j4r6, MINI-3jp7-jhvp-hq8j, MINI-4gcm-wmw8-4f28, MINI-87wf-59qh-85v9, MINI-8f8g-4qfq-4r3w, MINI-9xch-gpcw-c8mf, MINI-f9vq-2gfr-hcv7, MINI-p7rq-3p85-vcfv, MINI-pr52-m586-68xr, MINI-qfxc-p552-3677, MINI-qx34-gcvx-68rg, MINI-rg3r-76v5-hg9x, MINI-rrvx-4hr2-2wj6, UBUNTU-CVE-2026-21725

## What is CVE-2026-21725?

CVE-2026-21725 is a low-severity vulnerability in Grafana Grafana, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A time-of-create-to-time-of-use (TOCTOU) vulnerability lets recently deleted-then-recreated data sources be re-deleted without permission to do so.

This requires several very stringent conditions to be met:

- The attacker must have admin access to the specific datasource prior to its first deletion.
- Upon deletion, all steps within the attack must happen within the next 30 seconds and on the same pod of Grafana.
- The attacker must delete the datasource, then someone must recreate it.
- The new datasource must not have the attacker as an admin.
- The new datasource must have the same UID as the prior datasource. These are randomised by default.
- The datasource can now be re-deleted by the attacker.
- Once 30 seconds are up, the attack is spent and cannot be repeated.
- No datasource with any other UID can be attacked.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

1 open source package ship an affected version, including grafana. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `grafana` | Bitnami | From 11.0.0 | 12.4.1 |

Products: Grafana Grafana.

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

Upgrade grafana to 12.4.1 or later.

## Is CVE-2026-21725 being exploited?

There is no known exploitation of CVE-2026-21725 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-21725 and fix it if it is affected.

What it is: CVE-2026-21725 is a low-severity vulnerability in Grafana Grafana, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-21725 in the wild and no public exploit code.

Affected packages and fixed versions:
- grafana (Bitnami): affected from 11.0.0; fixed in 12.4.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-21725/ (Markdown: https://insights.sbomify.com/CVE-2026-21725/index.md)
```

## Sources

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

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