CVE-2026-42154

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 46% 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: epss, secondary
Trending — Patch released 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.

Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the remote read endpoint (/api/v1/read) does not validate the declared decoded length in a snappy-compressed request body before allocating memory. An unauthenticated attacker can send a small payload that causes a huge heap allocation per request. Under concurrent load this can exhaust available memory and crash the Prometheus process. This issue has been patched in versions 3.5.3 and 3.11.3.

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
54%
KEV
Not listed

Published

May 4, 2026

Last Modified

August 19, 2026

Advisory Details (5)

Auto-updated May 4, 2026
Patch available. Sources: github.
github Patch Available

Remote read endpoint allows denial of service via crafted snappy payload · Advisory · prometheus/prometheus · GitHub

Affected: 3.11.3 and 3.5.3 LTS. Users should upgrade to these versions or later.

https://github.com/prometheus/prometheus/security/advisories/GHSA-8rm2-7qqf-34qm
generic

Release 3.5.3 / 2026-04-27 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/releases/tag/v3.5.3
generic

Release 3.11.3 / 2026-04-27 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/releases/tag/v3.11.3
generic

remote: validate snappy decoded length before allocation in read enpoint by roidelapluie · Pull Request #18585 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/pull/18585
generic

remote: validate snappy decoded length before allocation in read endpoint by roidelapluie · Pull Request #18584 · prometheus/prometheus · GitHub

https://github.com/prometheus/prometheus/pull/18584

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatopenshift-logging/opa-openshift-rhel9:17866451092026-08-18redhat
redhatcompliance/openshift-file-integrity-rhel8-operator:17864394492026-08-12redhat
redhatopenshift4/ose-prometheus-rhel9:17855825592026-08-12redhat
redhatopentelemetry-collector-0:0.152.1-1.el10_02026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_62026-08-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17854428722026-08-11redhat
redhatopentelemetry-collector-0:0.152.1-1.el9_42026-08-11redhat
redhatopenshift4/ose-prometheus-rhel9:17848288712026-08-06redhat
redhatopenshift-logging/opa-openshift-rhel9:17854188522026-08-05redhat
redhatopenshift4/ose-prometheus-rhel9:17853600672026-08-05redhat
redhatopenshift4/ose-prometheus-rhel9:17845838362026-07-29redhat
redhatopenshift-logging/opa-openshift-rhel9:17847478152026-07-29redhat
redhatopenshift4/ose-prometheus-rhel9:17843497132026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17849066282026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatopenshift4/ose-prometheus-rhel9:17840535552026-07-21redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhtas/trillian-logsigner-rhel9:17839688612026-07-16redhat
redhatrhem/flightctl-worker-rhel10:17841949712026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17840606812026-07-16redhat
redhatquay/quay-rhel8:17837504472026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhtas/createtree-rhel9:17839688612026-07-16redhat
redhatrhtas/updatetree-rhel9:17839688612026-07-16redhat
redhatrhem/flightctl-worker-rhel9:17841277752026-07-15redhat
redhatquay/quay-rhel8:17841258382026-07-15redhat

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

(6 across 5 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/prometheus/prometheus0.311.3
github.com/prometheus/prometheus/v2
Debian:11(1)
PackageVulnerable rangeFixed inDependents
prometheus2.24.1+ds-1 ... 3.5.3+ds1-3 (75 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
prometheus2.42.0+ds-5 ... 3.5.3+ds1-3 (40 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
prometheus2.53.3+ds1-2 ... 3.5.3+ds1-3 (10 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
prometheus2.53.3+ds1-2 ... 2.53.5+ds1-5 (7 versions)3.5.3+ds1-1

Weakness Classification(3)

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

Additional Vendor Advisories

(21)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 25× in last 7d / 121× 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 231 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-42154?
CVE-2026-42154 is a high vulnerability published on May 4, 2026. Prometheus is an open-source monitoring system and time series database. Prior to versions 3.5.3 and 3.11.3, the remote read endpoint (/api/v1/read) does not validate the declared decoded length in a snappy-compressed request body before allocating memory. An unauthenticated attacker can send a…
When was CVE-2026-42154 disclosed?
CVE-2026-42154 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42154 actively exploited?
CVE-2026-42154 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 45.8% of all scored CVEs.
What is the CVSS score of CVE-2026-42154?
CVE-2026-42154 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-42154?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42154, 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-42154

Explore →

Is Your Infrastructure Affected by CVE-2026-42154?

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