CVE-2026-15157

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% 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, nvd
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 4, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Patch available. Sources: github.
generic

Security Advisories | OpenJS Foundation CVE Numbering Authority

https://cna.openjsf.org/security-advisories.html
github Patch Available

undici vulnerable to CRLF Injection via blob-like body 'type' property · Advisory · nodejs/undici · GitHub

Affected: 6.24.0 / 7.24.0), both closed by adding

https://github.com/nodejs/undici/security/advisories/GHSA-m8rv-5g2x-5cg5

Vendor Advisories for CVE-2026-15157(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatnodejs24-main-24.18.1-0.1.hum12026-07-30redhat
redhatnodejs26-main-26.5.1-1.5.hum12026-07-29redhat

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

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (39 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (15 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.5.0+dfsg+~cs3.2.0-3 (14 versions)8.9.0+dfsg+~cs3.2.0-1—
npm(1)
PackageVulnerable rangeFixed inDependents
undici—8.9.0—

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 20× in last 7d / 60× 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.

  1. 2026-08-21 05:11 UTCEG score recompute
  2. 2026-08-21 05:11 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 04:22 UTCEG score recompute
  5. 2026-08-20 04:22 UTCVendor advisory
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 03:33 UTCEG score recompute
  8. 2026-08-19 03:33 UTCVendor advisory
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-18 02:37 UTCEG score recompute
  11. 2026-08-18 02:37 UTCVendor advisory
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-17 01:47 UTCEG score recompute
  14. 2026-08-17 01:47 UTCVendor advisory
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-16 00:58 UTCEG score recompute
  18. 2026-08-16 00:58 UTCVendor advisory
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-15 00:08 UTCVendor advisory
  21. 2026-08-13 23:18 UTCEG score recompute
  22. 2026-08-13 23:18 UTCVendor advisory
  23. 2026-08-13 22:00 UTCEPSS rescore
  24. 2026-08-12 22:29 UTCEG score recompute
  25. 2026-08-12 22:29 UTCVendor advisory
Show 35 more
  1. 2026-08-12 13:50 UTCEPSS rescore
  2. 2026-08-11 21:39 UTCEG score recompute
  3. 2026-08-11 21:39 UTCVendor advisory
  4. 2026-08-11 13:42 UTCEPSS rescore
  5. 2026-08-11 00:00 UTCEPSS rescore
  6. 2026-08-10 20:50 UTCVendor advisory
  7. 2026-08-09 20:00 UTCEG score recompute
  8. 2026-08-09 20:00 UTCVendor advisory
  9. 2026-08-09 13:46 UTCEPSS rescore
  10. 2026-08-08 19:11 UTCEG score recompute
  11. 2026-08-08 19:11 UTCVendor advisory
  12. 2026-08-08 16:37 UTCEPSS rescore
  13. 2026-08-07 18:21 UTCEG score recompute
  14. 2026-08-07 18:21 UTCVendor advisory
  15. 2026-08-06 17:32 UTCEG score recompute
  16. 2026-08-06 17:32 UTCVendor advisory
  17. 2026-08-06 13:46 UTCEPSS rescore
  18. 2026-08-05 19:17 UTCEPSS rescore
  19. 2026-08-05 16:42 UTCVendor advisory
  20. 2026-08-04 15:53 UTCEG score recompute▲ 1.20
  21. 2026-08-04 15:52 UTCNVD updateCVSS v3 → 5.4
  22. 2026-08-04 15:09 UTCEPSS rescore
  23. 2026-08-04 10:38 UTCEPSS rescore
  24. 2026-08-03 20:17 UTCEG score recompute
  25. 2026-08-03 10:35 UTCEPSS rescore
  26. 2026-08-02 19:27 UTCEG score recompute
  27. 2026-08-02 02:26 UTCEPSS rescore
  28. 2026-08-01 18:38 UTCEG score recompute
  29. 2026-08-01 04:15 UTCEPSS rescore
  30. 2026-07-30 16:33 UTCEG score recompute
  31. 2026-07-30 16:27 UTCEPSS rescore
  32. 2026-07-30 15:40 UTCEG score recompute
  33. 2026-07-29 22:26 UTCEG score recompute
  34. 2026-07-29 21:27 UTCEG score recompute
  35. 2026-07-29 21:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-15157?
CVE-2026-15157 is a medium vulnerability published on July 29, 2026. 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…
When was CVE-2026-15157 disclosed?
CVE-2026-15157 was first published in the National Vulnerability Database on July 29, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-15157 actively exploited?
CVE-2026-15157 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 94.9% of all scored CVEs.
What is the CVSS score of CVE-2026-15157?
CVE-2026-15157 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-15157?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-15157, 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-15157

Explore →

Is Your Infrastructure Affected by CVE-2026-15157?

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

Start Free Scan →Browse All CVEs