CVE-2026-21725: Authorization Bypass via TOCTOU in Grafana Datasource Deletion by Name
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.
Security readout for executives and security teams
Plain-English summary
This is a narrow Grafana issue where a person who used to administer a datasource may be able to delete its replacement shortly after it is recreated. The attack window is about 30 seconds and depends on unlikely UID and pod conditions. The documented impact is availability only, not data theft or integrity compromise.
Executive priority
Treat this as low urgency unless Grafana v11.0.0 is present with delegated datasource administration. It does not indicate data exposure, but it could disrupt a datasource under a very specific race condition. Validate exposure during normal vulnerability management cycles.
Technical view
CVE-2026-21725 is a TOCTOU authorization bypass in Grafana datasource deletion by name. Under stringent conditions, stale authorization state can let a low-privileged user re-delete a datasource recreated with the same UID after initial deletion. CVSS is 2.6, with high attack complexity, required privileges, user interaction, and availability impact only.
Likely exposure
Exposure appears limited to Grafana v11.0.0 according to the source bundle. Practical exposure is highest where users can administer datasources, recreate datasources with fixed UIDs, and traffic can land on the same Grafana pod within the 30-second window.
Exploitation context
No active exploitation is indicated by KEV or the provided sources. The described scenario requires prior datasource admin rights, deletion and recreation within 30 seconds, same pod handling, same UID reuse, and loss of admin rights on the recreated datasource.
Researcher notes
The key research constraint is the narrow precondition chain: prior admin, first deletion, recreated datasource, same UID, same pod, and 30-second expiry. Evidence does not name a patch in the supplied bundle, so remediation should follow Grafana's advisory rather than assumed version guidance.
Mitigation direction
Check Grafana's advisory for vendor-supported remediation guidance.
Inventory Grafana deployments and identify any v11.0.0 instances.
Restrict datasource admin privileges to trusted operational users.
Avoid manually reusing datasource UIDs after deletion.
Monitor datasource deletion and recreation events for unusual timing.
Validation and detection
Confirm whether any Grafana instance is running v11.0.0.
Review datasource permission assignments for excessive admin rights.
Audit logs for delete-then-recreate events within 30 seconds.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-367 · source CWE mapping
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.