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 45% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 7.5Exploit: None knownExposed services: Not assessed

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.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

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%
EPSS PROB
0.9%
EPSS %ILE
58th
KEV
Not listed

Published

May 4, 2026

Last Modified

September 10, 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

Vendor Advisories for CVE-2026-42154(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatopenshift4/ose-prometheus:17873438382026-09-03redhat
redhatopenshift4/ose-prometheus:17869998212026-08-26redhat
redhatopenshift4/ose-prometheus:17869982742026-08-26redhat
redhatrhacm2/prometheus-rhel9:17872302872026-08-26redhat
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.el9_42026-08-11redhat
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
redhatopenshift4/ose-prometheus-rhel9:17848288712026-08-06redhat
redhatopenshift-logging/opa-openshift-rhel9:17854188522026-08-05redhat
redhatopenshift4/ose-prometheus-rhel9:17853600672026-08-05redhat
redhatopenshift-logging/opa-openshift-rhel9:17847478152026-07-29redhat
redhatopenshift4/ose-prometheus-rhel9:17845838362026-07-29redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17849066282026-07-28redhat
redhatopenshift4/ose-prometheus-rhel9:17843497132026-07-28redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845613762026-07-23redhat
redhatquay/quay-rhel8:17843539042026-07-21redhat
redhatopenshift4/ose-prometheus-rhel9:17840535552026-07-21redhat
redhatquay/quay-rhel8:17843519662026-07-21redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17845620602026-07-21redhat
redhatquay/quay-rhel8:17837518652026-07-20redhat
redhatrhtas/updatetree-rhel9:17839688612026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatquay/quay-rhel9:17839558462026-07-16redhat
redhatrhem/flightctl-worker-rhel10:17841949712026-07-16redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17840606812026-07-16redhat
redhatrhtas/createtree-rhel9:17839688612026-07-16redhat

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 rangeFix by version rangeDependents
github.com/prometheus/prometheus—
  • 0.306.0 up to 0.311.3: fixed in 0.311.3
  • every version up to 0.305.2: fixed in 0.305.2
  • 1.0.0-rc.0 through 2.5.0: no fix on record
  • 1.0.0-rc.0 on: no fix on record
—
github.com/prometheus/prometheus/v2—
  • every version on: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.24.1+ds-1 ... 3.5.3+ds1-3 (75 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.42.0+ds-5 ... 3.5.3+ds1-6~exp1 (43 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.53.3+ds1-2 ... 3.5.3+ds1-6~exp1 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
prometheus2.53.3+ds1-2 ... 2.53.5+ds1-5 (7 versions)
  • every version up to 3.5.3+ds1-1: fixed in 3.5.3+ds1-1
—

Weakness Classification(3)

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

All Vendor Advisories

(25)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 5× in last 7d / 33× 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 305 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Same product

5 shown

Debian:11:prometheus · Debian:13:prometheus · Go:github.com/prometheus/prometheus

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 on May 4, 2026, with the most recent update on September 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-42154 actively exploited?
CVE-2026-42154 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (58th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-42154?
CVE-2026-42154 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-42154?
A fix for CVE-2026-42154 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-42154 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs