CVE-2026-21727: Grafana Correlations: Cross-Tenant Data Disclosure and Permanent Deletion via Legacy org_id=0 Record
---
title: Cross-Tenant Legacy Correlation Disclosure and Deletion
draft: false
hero:
image: /static/img/heros/hero-legal2.svg
content: "# Cross-Tenant Legacy Correlation Disclosure and Deletion"
date: 2026-01-29
product: Grafana
severity: Low
cve: CVE-2026-21727
cvss_score: "3.3"
cvss_vector: "CVSS:3.3/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N"
fixed_versions:
- ">=11.6.11 >=12.0.9 >=12.1.6 >=12.2.4"
---
A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records. Due to a backward compatibility condition allowing org_id = 0 records to be returned across organizations, a user with datasource management privileges could read and permanently delete legacy correlation data belonging to another organization. This issue affects correlations created prior to Grafana 10.2 and is fixed in >=11.6.11, >=12.0.9, >=12.1.6, and >=12.2.4.
Thanks to Gyu-hyeok Lee (g2h) for reporting this vulnerability.
Security readout for executives and security teams
Plain-English summary
This is a low-severity Grafana Correlations issue where certain old correlation records could cross organization boundaries. A highly privileged datasource manager could read or permanently delete legacy correlation data from another organization. The issue is narrow, but deletion risk makes cleanup worthwhile for multi-tenant Grafana environments.
Executive priority
Treat this as a targeted maintenance item, not an emergency. Patch during the next appropriate Grafana maintenance window, with higher priority for multi-tenant environments that use Correlations.
Technical view
Grafana’s Correlations feature allowed backward-compatible org_id=0 legacy records to be returned across organizations. The advisory says users with datasource management privileges could read and permanently delete legacy correlations belonging to another organization. Fixed versions are >=11.6.11, >=12.0.9, >=12.1.6, and >=12.2.4.
Likely exposure
Exposure is most likely in Grafana deployments using Correlations with legacy correlation records created before Grafana 10.2, especially multi-organization instances with users holding datasource management privileges.
Exploitation context
No active exploitation is cited, and KEV is false. The CVSS vector requires network access, high attack complexity, and high privileges, with low confidentiality and integrity impact and no availability impact.
Researcher notes
Evidence is limited to the CVE data and Grafana advisory. The key condition is legacy org_id=0 correlation handling. Validate exposure by confirming version, Correlations usage, legacy record presence, and datasource-management privilege assignments.
Mitigation direction
Upgrade Grafana to a fixed version for your branch.
Review Grafana’s advisory for branch-specific upgrade guidance.
Limit datasource management privileges to trusted administrators.
Identify whether legacy pre-10.2 correlation records exist.
Prioritize multi-organization instances where correlations are used.
Validation and detection
Check current Grafana version against the fixed version list.
Inventory Correlations usage and legacy records created before Grafana 10.2.
Review users and roles with datasource management privileges.
Check for unexpected missing or cross-organization correlation data.
Document affected organizations and remediation status.
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 · medium confidence lookup
CWE-732: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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.
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.