Advisory record · GHSA-8rm2-7qqf-34qm

Prometheus: Remote read endpoint allows denial of service via crafted snappy payload

CVSS 7.5 HighEPSS 0.0081 · 57th percentile

Published by the GitHub Advisory Database at 5 May 2026, 19:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/prometheus/prometheusGo>=0.306.0, <0.311.3 || <0.305.2 || >=1.0.0-rc.0, <=2.5.00.311.3, 0.305.2
Identifiers
GHSA-8rm2-7qqf-34qm · BIT-prometheus-2026-42154 · CVE-2026-42154 · GO-2026-5264
Weakness (CWE)
CWE-400 · CWE-770 · CWE-789
Published
5 May 2026
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Prometheus (Go module github.com/prometheus/prometheus) versions before 0.305.2, from 0.306.0 before 0.311.3, from 1.0.0-rc.0 through 2.5.0 are affected. An unauthenticated attacker can send a small snappy-compressed request to the remote read endpoint (/api/v1/read) that triggers a very large memory allocation, which under concurrent load can exhaust memory and crash the process. Upgrade to 0.305.2, 0.311.3, or a later fixed release. Users who cannot upgrade can place the endpoint behind a reverse proxy or firewall that requires authentication.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0081, the 57th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 4 May 2026, 19:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:14 UTC First seen by agentprime
  3. 31 Oct 2026, 14:14 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.