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.0%, top 95% 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
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 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).

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
46.6%
KEV
Not listed

Published

April 24, 2026

Last Modified

July 10, 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 11× in last 7d / 43× 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 133 total refreshes for this CVE.

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

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).
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 July 10, 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 46.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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