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% (8th percentile of EPSS-scored CVEs). 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.2%CVSS: 5.4Exploit: None knownExposed services: Not assessed

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.4MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

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%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

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(4)

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 / EcosystemFix (by version range) / 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 rangeFix by version rangeDependents
node-undici5.15.0+dfsg1+~cs20.10.9.3-1 ... 8.9.0+dfsg+~cs3.2.0-1 (40 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.9.0+dfsg+~cs3.2.0-1 (16 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-undici7.15.0+dfsg+~cs3.2.0-1 ... 8.5.0+dfsg+~cs3.2.0-3 (14 versions)
  • every version up to 8.9.0+dfsg+~cs3.2.0-1: fixed in 8.9.0+dfsg+~cs3.2.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
undici—
  • every version up to 6.28.0: fixed in 6.28.0
  • 7.0.0 up to 7.29.0: fixed in 7.29.0
  • 8.0.0 up to 8.9.0: fixed in 8.9.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× 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.

Showing the most recent 100 of 148 total refreshes for this CVE.

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

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

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 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.2% probability of exploitation in the next 30 days (8th percentile of EPSS-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?
A fix for CVE-2026-15157 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-15157 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-15157

Explore →

Is Your Infrastructure Affected by CVE-2026-15157?

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

Book a Demo →Browse All CVEs