CVE-2026-21721

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-01-27. the CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:grafana, epss, ghsa
Elevated
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is an organization‑internal privilege escalation.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
52(Track)
EG Risk 52/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

January 27, 2026

Last Modified

August 27, 2026

Advisory Details (1)

Auto-updated Jun 23, 2026
No patch confirmed yet.
generic

Cross-dashboard privilege escalation via permission management | Grafana Labs

https://grafana.com/security/security-advisories/cve-2026-21721

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17835788472026-07-16redhat
redhatrhacm2/acm-grafana-rhel9:17749506542026-04-15redhat
redhatrhacm2/acm-grafana-rhel9:17740021662026-03-24redhat
redhatgrafana-0:10.2.6-17.el9_62026-03-02redhat
redhatgrafana-0:10.2.6-20.el10_02026-02-23redhat
redhatgrafana-0:10.2.6-18.el9_72026-02-18redhat
redhatgrafana-0:10.2.6-22.el10_12026-02-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 218 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-16 14:07 UTCEPSS rescore
  3. 2026-09-16 05:15 UTCEPSS rescore
  4. 2026-09-15 18:54 UTCOSV refresh
  5. 2026-09-13 16:47 UTCEPSS rescore
  6. 2026-09-12 15:01 UTCEPSS rescore
  7. 2026-09-11 14:52 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-07 16:01 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-04 05:06 UTCEPSS rescore
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:41 UTCEPSS rescore
  20. 2026-08-27 18:04 UTCEG score recompute
  21. 2026-08-27 18:04 UTCVendor advisory
  22. 2026-08-27 18:04 UTCGHSA enrichment
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-26 09:17 UTCEG score recompute
Show 75 more
  1. 2026-08-26 09:17 UTCVendor advisory
  2. 2026-08-26 09:17 UTCGHSA enrichment
  3. 2026-08-25 13:48 UTCEPSS rescore
  4. 2026-08-24 14:04 UTCEG score recompute
  5. 2026-08-24 14:04 UTCVendor advisory
  6. 2026-08-24 14:04 UTCGHSA enrichment
  7. 2026-08-23 00:19 UTCEPSS rescore
  8. 2026-08-21 23:49 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-19 19:15 UTCVendor advisory
  11. 2026-08-19 19:15 UTCGHSA enrichment
  12. 2026-08-19 18:59 UTCVendor advisory
  13. 2026-08-19 18:59 UTCGHSA enrichment
  14. 2026-08-19 17:55 UTCEG score recompute
  15. 2026-08-19 17:55 UTCVendor advisory
  16. 2026-08-19 17:55 UTCGHSA enrichment
  17. 2026-08-19 17:03 UTCEPSS rescore
  18. 2026-08-18 13:48 UTCEPSS rescore
  19. 2026-08-17 21:45 UTCEG score recompute
  20. 2026-08-17 21:45 UTCVendor advisory
  21. 2026-08-17 21:45 UTCGHSA enrichment
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 02:14 UTCEPSS rescore
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-15 01:21 UTCVendor advisory
  27. 2026-08-15 01:21 UTCGHSA enrichment
  28. 2026-08-14 12:14 UTCEG score recompute
  29. 2026-08-14 12:14 UTCVendor advisory
  30. 2026-08-14 12:14 UTCGHSA enrichment
  31. 2026-08-13 22:00 UTCEPSS rescore
  32. 2026-08-13 04:26 UTCEG score recompute
  33. 2026-08-13 04:26 UTCVendor advisory
  34. 2026-08-13 04:26 UTCGHSA enrichment
  35. 2026-08-12 13:50 UTCEPSS rescore
  36. 2026-08-12 13:27 UTCEG score recompute
  37. 2026-08-12 13:27 UTCVendor advisory
  38. 2026-08-12 13:27 UTCGHSA enrichment
  39. 2026-08-11 13:42 UTCEPSS rescore
  40. 2026-08-11 05:35 UTCEG score recompute
  41. 2026-08-11 05:35 UTCVendor advisory
  42. 2026-08-11 05:35 UTCGHSA enrichment
  43. 2026-08-11 00:00 UTCEPSS rescore
  44. 2026-08-10 10:27 UTCVendor advisory
  45. 2026-08-10 10:27 UTCGHSA enrichment
  46. 2026-08-09 18:13 UTCEG score recompute
  47. 2026-08-09 18:13 UTCVendor advisory
  48. 2026-08-09 18:13 UTCGHSA enrichment
  49. 2026-08-09 13:46 UTCEPSS rescore
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-07 23:28 UTCEG score recompute
  52. 2026-08-07 23:28 UTCVendor advisory
  53. 2026-08-07 23:28 UTCGHSA enrichment
  54. 2026-08-06 13:46 UTCEPSS rescore
  55. 2026-08-06 04:55 UTCEG score recompute
  56. 2026-08-06 04:55 UTCVendor advisory
  57. 2026-08-06 04:55 UTCGHSA enrichment
  58. 2026-08-05 19:17 UTCEPSS rescore
  59. 2026-08-04 15:10 UTCEPSS rescore
  60. 2026-08-04 10:38 UTCEPSS rescore
  61. 2026-08-03 10:35 UTCEPSS rescore
  62. 2026-08-02 22:05 UTCEG score recompute
  63. 2026-08-02 22:05 UTCVendor advisory
  64. 2026-08-02 22:05 UTCGHSA enrichment
  65. 2026-08-02 02:26 UTCEPSS rescore
  66. 2026-08-01 04:15 UTCEPSS rescore
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-29 14:51 UTCEG score recompute
  69. 2026-07-29 14:51 UTCVendor advisory
  70. 2026-07-29 14:51 UTCGHSA enrichment
  71. 2026-07-27 14:13 UTCEPSS rescore
  72. 2026-07-26 14:54 UTCEPSS rescore
  73. 2026-07-26 14:54 UTCEPSS rescore
  74. 2026-07-26 09:39 UTCEG score recompute
  75. 2026-07-26 09:39 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCLeonideath/Exploit-LPE-CVE-2026-21721
    First seen Feb 3, 2026

    Эксплоит на CVE-2026-21721

    Open source ↗

Frequently asked(5)

What is CVE-2026-21721?
CVE-2026-21721 is a high vulnerability published on January 27, 2026. The dashboard permissions API does not verify the target dashboard scope and only checks the dashboards.permissions:* action. As a result, a user who has permission management rights on one dashboard can read and modify permissions on other dashboards. This is an organization‑internal privilege…
When was CVE-2026-21721 disclosed?
CVE-2026-21721 was first published in the National Vulnerability Database on January 27, 2026, with the most recent update on August 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21721 actively exploited?
CVE-2026-21721 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.7% of all scored CVEs.
What is the CVSS score of CVE-2026-21721?
CVE-2026-21721 has a CVSS v4.0 base score of 8.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-21721?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21721, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-21721

Explore →

Is Your Infrastructure Affected by CVE-2026-21721?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.