CVE-2026-21728

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 52% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:grafana, epss
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy.

Mitigation can be done by setting max_result_limit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

April 24, 2026

Last Modified

August 26, 2026

References (1)

Vendor Advisories for CVE-2026-21728(5)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17801671182026-06-04redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17792122592026-06-02redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17795794392026-06-01redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17788677532026-05-28redhat

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.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/grafana/tempo—2.10.2—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 98× 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 243 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-21728?
CVE-2026-21728 is a high vulnerability published on April 24, 2026. Tempo queries with large limits can cause large memory allocations which can impact the availability of the service, depending on its deployment strategy. Mitigation can be done by setting maxresultlimit in the search config, e.g. to 262144 (2^18). Alternatively, automatically restart the service.
When was CVE-2026-21728 disclosed?
CVE-2026-21728 was first published in the National Vulnerability Database on April 24, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21728 actively exploited?
CVE-2026-21728 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 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-21728?
CVE-2026-21728 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-21728?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21728, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-21728

Explore →

Is Your Infrastructure Affected by CVE-2026-21728?

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

Start Free Scan →Browse All CVEs