CVE-2026-21727

CVE-2026-21727 is a low-severity incorrect permission assignment for critical resource vulnerability in github.com/grafana/grafana (go), affecting versions < 1.9.2-0.20260127141016-e702db6096e0. It is fixed in 1.9.2-0.20260127141016-e702db6096e0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Grafana legacy correlations allow cross-tenant disclosure and deletion

hero:
image: /static/img/heros/hero-legal2.svg
content: "# Cross-Tenant Legacy Correlation Disclosure and Deletion"
date: 2026-01-29
product: Grafana
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.

Impact

A file, directory, or other resource is assigned permissions that allow broader access than intended. Typical impact: unauthorized read, modification, or execution of the resource.

CVE-2026-21727 has a CVSS score of 3.3 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.9.2-0.20260127141016-e702db6096e0); upgrading removes the vulnerable code path.

Affected versions

github.com/grafana/grafana (< 1.9.2-0.20260127141016-e702db6096e0)

Security releases

github.com/grafana/grafana → 1.9.2-0.20260127141016-e702db6096e0 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade github.com/grafana/grafana to 1.9.2-0.20260127141016-e702db6096e0 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2026-21727? CVE-2026-21727 is a low-severity incorrect permission assignment for critical resource vulnerability in github.com/grafana/grafana (go), affecting versions < 1.9.2-0.20260127141016-e702db6096e0. It is fixed in 1.9.2-0.20260127141016-e702db6096e0. A file, directory, or other resource is assigned permissions that allow broader access than intended.
  2. How severe is CVE-2026-21727? CVE-2026-21727 has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of github.com/grafana/grafana are affected by CVE-2026-21727? github.com/grafana/grafana (go) versions < 1.9.2-0.20260127141016-e702db6096e0 is affected.
  4. Is there a fix for CVE-2026-21727? Yes. CVE-2026-21727 is fixed in 1.9.2-0.20260127141016-e702db6096e0. Upgrade to this version or later.
  5. Is CVE-2026-21727 exploitable, and should I be worried? Whether CVE-2026-21727 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2026-21727 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2026-21727? Upgrade github.com/grafana/grafana to 1.9.2-0.20260127141016-e702db6096e0 or later.

Other vulnerabilities in github.com/grafana/grafana

Stop the waste.
Protect your environment with Kodem.