Grafana legacy correlations allow cross-tenant disclosure and deletion

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-21727: 0.20% estimated exploitation activity in the next 30 days; percentile 10.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

--- hero: image: /static/img/heros/hero-legal2.svg content: "

Cross-Tenant Legacy Correlation Disclosure and Deletion" date: 2026-01-29 product: Grafana fixedversions: - "=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 orgid = 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.

Published by the source

7 Oct 2026, 14:10 UTC

Last modified by the source

7 Oct 2026, 17:55 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p5x9-j974-rpfp

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-6664

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-21727

Advisory: Grafana legacy correlations allow cross-tenant disclosure and deletion
IDs: CVE-2026-21727, GHSA-p5x9-j974-rpfp
Record: https://patchnext.com/advisories/cve-2026-21727 (revision 2, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/grafana/grafana 1.9.2-0.20260127141016-e702db6096e0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/grafana/grafana: affected < 1.9.2-0.20260127141016-e702db6096e0; fixed in 1.9.2-0.20260127141016-e702db6096e0

## Suggested inspection (read-only)
- Go github.com/grafana/grafana: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/grafana/grafana.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6664 (OSV record GO-2026-6664 lists affected ranges: Go github.com/grafana/grafana >=0)
- Verified: https://github.com/advisories/GHSA-p5x9-j974-rpfp (GitHub-reviewed advisory GHSA-p5x9-j974-rpfp lists affected ranges: Go github.com/grafana/grafana >=0 <1.9.2-0.20260127141016-e702db6096e0)

Commands are suggestions: review each one before running it.