NVD / CVE Program· CNA GitHub_M

CVE-2026-42154: Prometheus: remote read endpoint allows denial of service via crafted snappy payload

Noroxi assessment

Priority: Monitor (action score 30/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.81% (FIRST EPSS); higher than 57.1% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: azl3 telegraf 1.31.0-19 on Azure Linux 3.0 1.31.0-20.

Low priority for now. Upgrade to azl3 telegraf 1.31.0-19 on Azure Linux 3.0 1.31.0-20 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.5 · v3.1—Proof of concept Fix available

Published: May 4, 2026
Updated: Sep 10, 2026
EPSS: 0.8% · 57th percentile
CWE: CWE-400

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.8%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · GitHub_M: 7.5; NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
prometheus	prometheus	cpe:2.3:a:prometheus:prometheus

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

prometheus prometheusbefore 3.5.3
prometheus prometheus3.6.0 and later · before 3.11.3

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

prometheus prometheus
- < 3.5.3, >= 3.6.0, < 3.11.3affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
AlmaLinux:10	opentelemetry-collector	before 0.152.1-1.el10_2	0.152.1-1.el10_2
AlmaLinux:9	opentelemetry-collector	before 0.152.1-1.el9_8	0.152.1-1.el9_8
Alpine:v3.23	prometheus	from 3.6.0 · before 3.5.3-r0	3.5.3-r0
Debian:12	prometheus	from 0	—
Debian:14	prometheus	before 3.5.3+ds1-1	3.5.3+ds1-1
Go	github.com/prometheus/prometheus	from 0.306.0 · before 0.311.3	0.311.3
Go	github.com/prometheus/prometheus	from 1.0.0-rc.0 · up to and including 2.5.0	—
Go	github.com/prometheus/prometheus	from 1.0.0-rc.0	—
Go	github.com/prometheus/prometheus	before 0.305.2	0.305.2
Go	github.com/prometheus/prometheus/v2	from 0	—
openSUSE:Tumbleweed	golang-github-prometheus-prometheus	before 3.11.3-1.1	3.11.3-1.1
Red Hat:edge_manager:1.1::el10	flightctl	before 0:1.1.3-1.el10em	0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el10	flightctl-agent	before 0:1.1.3-1.el10em	0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el10	flightctl-cli	before 0:1.1.3-1.el10em	0:1.1.3-1.el10em
Red Hat:edge_manager:1.1::el9	flightctl	before 0:1.1.3-1.el9em	0:1.1.3-1.el9em
Red Hat:edge_manager:1.1::el9	flightctl-agent	before 0:1.1.3-1.el9em	0:1.1.3-1.el9em
Red Hat:edge_manager:1.1::el9	flightctl-cli	before 0:1.1.3-1.el9em	0:1.1.3-1.el9em
Red Hat:enterprise_linux_eus:10.0	opentelemetry-collector	before 0:0.152.1-1.el10_0	0:0.152.1-1.el10_0
Red Hat:enterprise_linux:10.2	opentelemetry-collector	before 0:0.152.1-1.el10_2	0:0.152.1-1.el10_2
Red Hat:enterprise_linux:9::appstream	opentelemetry-collector	before 0:0.152.1-1.el9_8	0:0.152.1-1.el9_8
Red Hat:hummingbird:1	jaeger	before 0:2.19.0-1.hum1	0:2.19.0-1.hum1
Red Hat:hummingbird:1	opentelemetry-collector	before 0:0.153.0-1.hum1	0:0.153.0-1.hum1
Red Hat:hummingbird:1	opentelemetry-collector-contrib	before 0:0.155.0-0.1.hum1	0:0.155.0-0.1.hum1
Red Hat:rhel_e4s:9.4::appstream	opentelemetry-collector	before 0:0.152.1-1.el9_4	0:0.152.1-1.el9_4

+67

Same product

prometheus: all records

Other highest-scoring records for the same primary product.

CVE-2026-42151Prometheus Azure AD remote write OAuth client secret exposed via config API
30Monitor
CVE-2021-29622Arbitrary redirects under /new endpoint
30Monitor
CVE-2026-119566Prometheus through 3.15.1 Credential Leak via remote_write Cross-Host Redirects
25Monitor

Published before and after this one in the same product

← EarlierCVE-2019-3826Mar 26, 2019 · A stored, DOM based, cross-site scripting (XSS) flaw was found in Prometheus before version 2.7.1.
25Monitor
← EarlierCVE-2026-40179Apr 15, 2026 · Prometheus: Stored XSS via metric names and label values in web UI tooltips and metrics explorer
21Monitor
Later →CVE-2026-44903May 26, 2026 · Prometheus: Stored XSS via crafted histogram bucket label values in the heatmap display of the old Prometheus web UI
20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
azl3 telegraf 1.31.0-19 on Azure Linux 3.0	1.31.0-20 · CBL-Mariner Releases	Microsoft (MSRC)
almalinux:opentelemetry-collector	0.152.1-1.el10_2 · AlmaLinux:10	Package registry (OSV)
alpine:prometheus	3.5.3-r0 · Alpine:v3.23	Package registry (OSV)
debian:prometheus	3.5.3+ds1-1 · Debian:14	Package registry (OSV)
Go:github.com/prometheus/prometheus	0.305.2	Package registry (OSV)
Go:github.com/prometheus/prometheus	0.311.3	Package registry (OSV)
opensuse:golang-github-prometheus-prometheus	3.11.3-1.1 · openSUSE:Tumbleweed	Package registry (OSV)
red hat:flightctl	0:1.1.3-1.el10em · Red Hat:edge_manager:1.1::el10	Package registry (OSV)
red hat:flightctl-agent	0:1.1.3-1.el10em · Red Hat:edge_manager:1.1::el10	Package registry (OSV)
red hat:flightctl-cli	0:1.1.3-1.el10em · Red Hat:edge_manager:1.1::el10	Package registry (OSV)
red hat:jaeger	0:2.19.0-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:opentelemetry-collector	0:0.153.0-1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
red hat:opentelemetry-collector-contrib	0:0.155.0-0.1.hum1 · Red Hat:hummingbird:1	Package registry (OSV)
rocky linux:opentelemetry-collector	0:0.152.1-1.el10_2 · Rocky Linux:10	Package registry (OSV)
suse:dracut-saltboot	1.2.1-150002.3.9.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-boynux-squid_exporter	1.13.0-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-lusitaniae-apache_exporter	1.0.10-150002.3.9.2 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-prometheus-alertmanager	0.28.1-150002.4.11.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-prometheus-node_exporter	1.10.2-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-prometheus-prometheus	3.5.3-150002.3.13.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:golang-github-QubitProducts-exporter_exporter	0.4.0-150002.3.6.2 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:grafana	11.6.14+security04-150002.4.21.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:mgr-push	5.2.4-150002.3.9.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:prometheus-blackbox_exporter	0.26.0-150002.3.11.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:prometheus-postgres_exporter	0.10.1-150002.3.3.2 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)
suse:python-defusedxml-sle15	0.7.1-150002.1.3.1 · SUSE:Multi Linux Manager Tools SLE-15	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-05-15

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMay 4, 2026
First PoCMay 15, 2026+10 d
TodayNov 7, 2026+187 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-secondary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}