# CVE-2026-15157 — undici

> As of 2026-07-30, CVE-2026-15157 is a MEDIUM-severity vulnerability in undici, CVSS v3.1 4.2, EPSS 0.1% (3.9th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-15157 as of 2026-07-30; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-30

## What is CVE-2026-15157?

undici does not validate the type property of a duck-typed blob-like request body before using it as the Content-Type header on the HTTP/1.1 dispatcher. In undici before 6.28.0, from 7.0.0 up to before 7.29.0, and from 8.0.0 up to before 8.9.0, an application that passes a hand-rolled blob-like body (via request, stream, pipeline, or dispatch) whose type is derived from untrusted input allows an attacker to inject CRLF sequences and append arbitrary HTTP headers, potentially smuggling a second request past the upstream. Native Blob objects are safe because their constructor strips CRLF from the type, and fetch is unaffected because it validates headers, but ecosystem libraries that build duck-typed blob shapes from user input can reach the vulnerable path. This is the same defect class as CVE-2022-35948 and CVE-2026-1527, on a header sink that the earlier fixes did not cover. The issue is fixed in undici 6.28.0, 7.29.0, and 8.9.0.

The record classifies CVE-2026-15157 under weakness class [CWE-93](https://intel.threadlinqs.com/cwe/CWE-93). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 68 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 4.2 — MEDIUM (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 3.9% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 2.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-29, last modified 2026-07-30

## Is CVE-2026-15157 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **undici**: undici

## How to fix CVE-2026-15157

No vendor patch reference has been recorded for CVE-2026-15157 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-15157

No threat campaign in the Threadlinqs corpus currently references CVE-2026-15157, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on 2026-07-31. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [github.com](https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5)
- [cna.openjsf.org](https://cna.openjsf.org/security-advisories.html)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-15157
Full detection coverage and IOCs for threats exploiting CVE-2026-15157 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp