LiveActive security incident?Get immediate response
CVE Record

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.

LowCVSS 2.6Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

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.
  • Check whether recreated datasources reuse previous UIDs.
  • Review multi-pod routing behavior relevant to same-pod requests.
Prepared
Confidence
high
Sources
3

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.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-21725 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
2.6CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L1.21.4GRAFANA

Vulnerability scoring details

Base CVSS 3.1 score

2.6Low
CVSS 3.1 vector shape for CVE-2026-21725Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GrafanaGrafanav11.0.0unaffected
Weakness

CWE details

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.