Quick answers
- Is CVE-2026-21727 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-21727 being exploited in the wild.
- How severe is CVE-2026-21727?
- Low severity, with a CVSS score of 3.3, published 15 April 2026.
- Which products and versions are affected?
- github.com/grafana/grafana (Go) < 1.9.2-0.20260127141016-e702db6096e0, SEMVER:introduced=0, SEMVER:introduced=0,fixed=1.9.2-0.20260127141016-e702db6096e0; Grafana versions before 11.6.11, 12.0.9, 12.1.6, and 12.2.4.
- Is there a fix for CVE-2026-21727?
- Yes. github.com/grafana/grafana (Go): upgrade to 1.9.2-0.20260127141016-e702db6096e0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-21727 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-21727?
- Check whether you run github.com/grafana/grafana (Go) or Grafana at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- github.com/grafana/grafana (Go): upgrade to 1.9.2-0.20260127141016-e702db6096e0 or later
go get github.com/grafana/grafana@v1.9.2-0.20260127141016-e702db6096e0
Technical details
A cross-tenant isolation flaw in Grafana's Correlations feature allows org_id = 0 legacy correlation records created before Grafana 10.2 to be returned and modified across organizational boundaries. An authenticated attacker with datasource management privileges can exploit a backward compatibility condition to read and permanently delete correlation data from other tenants. The vulnerability requires high privilege level and involves network-based access.
Affected products
- Grafana Grafana versions before 11.6.11, 12.0.9, 12.1.6, and 12.2.4
Identifiers
- CVE-2026-21727
- BIT-GRAFANA-2026-21727
- GHSA-p5x9-j974-rpfp
- GO-2026-6664
Timeline
- 2026-01-29: disclosed
- 2026-04-15: advisory