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

Grafana v11.0.0 can allow a former datasource administrator to delete a newly recreated datasource without permission. The opportunity lasts only 30 seconds and requires the replacement to use the same UID on the same Grafana pod. The impact is limited to datasource availability; the supplied sources report no confidentiality or integrity impact.

Executive priority

Treat as a low-priority but valid maintenance issue. Prioritize environments running v11.0.0 where datasource administration is broadly delegated or datasource loss could disrupt important monitoring. Escalate if logs show rapid same-UID recreation and deletion. Follow Grafana’s advisory because the supplied sources do not name a fixed release.

Technical view

This CWE-367 TOCTOU authorization bypass affects datasource deletion by name. Exploitation requires prior administrative access, deletion and same-UID recreation within 30 seconds, execution on the same pod, and removal of the attacker’s new administrative rights. A successful attempt permits only re-deletion of that replacement datasource.

Likely exposure

Exposure is narrow. The supplied affected-product data identifies Grafana v11.0.0. Practical risk requires a user with prior datasource administration rights, coordinated recreation using an identical UID, and same-pod requests within 30 seconds. Randomized UIDs normally make this sequence less likely.

Exploitation context

The supplied bundle does not identify active exploitation, and the CVE is not listed as KEV there. Exploitation has high complexity, requires prior privileges and another person recreating the datasource, and causes limited availability loss. No exploit procedure or public weaponization evidence is provided.

Researcher notes

The constraints substantially limit reproducibility: prior datasource administration, a second actor, identical UID, same pod, and a 30-second window are all required. The authorization failure applies only to the recreated datasource with that UID. Available evidence supports availability impact only, with CVSS 3.1 score 2.6 and vector AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:N/A:L.

Mitigation direction

  • Review Grafana’s advisory and apply its supported remediation; the supplied sources name no fixed version.
  • Restrict datasource administration to trusted users and revoke unnecessary privileges.
  • Avoid recreating deleted datasources with the same UID during the 30-second window.
  • Monitor rapid delete-recreate-delete sequences and investigate unexpected datasource loss.

Validation and detection

  • Identify whether any deployed Grafana instance runs v11.0.0.
  • Review datasource permissions for users who previously held administrative access.
  • Inspect logs for same-UID deletion, recreation, and re-deletion within 30 seconds on one pod.
  • Confirm recreated datasources receive new randomized UIDs.
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.