Security readout for executives and security teams
Plain-English summary
A highly privileged Grafana user could cross organization boundaries to view or permanently delete certain legacy Correlations records. Exposure is limited to correlations created before Grafana 10.2, but affected multi-tenant deployments could experience confidentiality and integrity loss.
Executive priority
Schedule remediation through normal vulnerability management, prioritizing multi-tenant systems with legacy correlations and broadly assigned datasource privileges. Escalate if sensitive correlation content is present, unexplained deletions appear, or privileged-account misuse is suspected.
Technical view
Grafana’s backward-compatibility handling returned legacy Correlations records with org_id=0 across organizations. A user holding datasource management privileges could read or delete another organization’s affected records. The issue is CWE-732 with CVSS 3.3 and is fixed in 11.6.11, 12.0.9, 12.1.6, and 12.2.4 or later.
Likely exposure
Most relevant to multi-organization Grafana deployments containing Correlations created before version 10.2. Exploitation requires datasource management privileges. Single-organization environments, deployments without legacy correlations, and versions confirmed at an applicable fixed release have lower or no stated exposure.
Exploitation context
The CVSS vector indicates network access, high attack complexity, high privileges, no user interaction, and limited confidentiality and integrity impact. The supplied record is not in KEV, and the sources provide no evidence of active exploitation. Absence from KEV does not prove exploitation has never occurred.
Researcher notes
The vulnerable condition is narrowly tied to legacy org_id=0 records and backward compatibility. The supplied affected-version metadata is incomplete for deriving exact vulnerable ranges; use Grafana’s fixed-release guidance instead. Validate tenant boundaries and record ownership defensively without modifying or deleting production data.
Mitigation direction
- Upgrade to 11.6.11, 12.0.9, 12.1.6, 12.2.4, or a later applicable release.
- Follow Grafana’s advisory when selecting the correct fixed branch for your deployment.
- Restrict datasource management privileges to personnel who require them.
- Preserve relevant records and logs before investigation because affected correlations can be permanently deleted.
Validation and detection
- Confirm every Grafana instance version against the vendor’s listed fixed releases.
- Determine whether the deployment uses multiple organizations and Correlations created before Grafana 10.2.
- Review which users and service accounts possess datasource management privileges.
- Identify legacy correlation records using org_id=0 through approved administrative review.
- Review available audit evidence for unexpected cross-organization correlation access or deletion.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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.
Open ATT&CK lookupCVE-2026-21727 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N0.72.5GRAFANAVulnerability scoring details
Base CVSS 3.1 score
3.3LowVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://grafana.com/security/security-advisories/cve-2026-21727CVE reference, GRAFANA · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Permission Assignment for Critical Resource
Incorrect Permission Assignment for Critical Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.