Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2026-15157: undici vulnerable to CRLF Injection via blob-like body 'type' property

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: undici undici 6.28.0, 7.29.0, 8.9.0; azl3 nodejs 24.18.1-1 on Azure Linux 3.0 24.20.0-1.

Low priority for now. Upgrade to undici undici 6.28.0, 7.29.0, 8.9.0; azl3 nodejs 24.18.1-1 on Azure Linux 3.0 24.20.0-1 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

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.

MediumCVSS 5.4 · v3.1—No exploit Fix available
Published
Jul 29, 2026
Updated
Aug 4, 2026
EPSS
0.2% · 18th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.4 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.4
CNA · openjs
4.2
1.2 point gap

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

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
  • No public exploit code on record
  • A fix has been released

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

Follow CVE-2026-15157

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for nodejs records

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.

VendorProduct
nodejsundici

Affected versions

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

  • nodejs undicibefore 6.28.0
  • nodejs undici7.0.0 and later · before 7.29.0
  • nodejs undici8.0.0 and later · before 8.9.0

Versions reported by the vendor

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

  • undici undici

    • 6.28.0, 7.29.0, 8.9.0not affected
    • before 6.28.0affected · semver
    • 7.0.0 and later · before 7.29.0affected · semver
    • 8.0.0 and later · before 8.9.0affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12node-undicifrom 0—
Debian:14node-undicibefore 8.9.0+dfsg+~cs3.2.0-18.9.0+dfsg+~cs3.2.0-1
npmundicifrom 7.0.0 · before 7.29.07.29.0
npmundicifrom 8.0.0 · before 8.9.08.9.0
npmundicibefore 6.28.06.28.0
Red Hat:hummingbird:1nodejs24before 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-binbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-develbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-docsbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-full-i18nbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-libsbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs24-npmbefore 0:11.16.0-1.24.18.1.0.1.hum10:11.16.0-1.24.18.1.0.1.hum1
Red Hat:hummingbird:1nodejs24-npm-binbefore 0:24.18.1-0.1.hum10:24.18.1-0.1.hum1
Red Hat:hummingbird:1nodejs26before 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-binbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-develbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-docsbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-full-i18nbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-libsbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
Red Hat:hummingbird:1nodejs26-npmbefore 0:11.17.0-1.26.5.1.1.5.hum10:11.17.0-1.26.5.1.1.5.hum1
Red Hat:hummingbird:1nodejs26-npm-binbefore 0:26.5.1-1.5.hum10:26.5.1-1.5.hum1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSnodejs16before 16.20.2-150400.3.42.116.20.2-150400.3.42.1
SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSnodejs18before 18.20.8-150400.9.39.118.20.8-150400.9.39.1
SUSE:Linux Enterprise Server 12 SP5-LTSSnodejs18before 18.20.8-8.44.118.20.8-8.44.1

Same product

nodejs: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-35949`undici.request` vulnerable to SSRF using absolute URL on `pathname`
    40Plan
  • CVE-2026-1525undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
    39Monitor
  • CVE-2026-109829undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects
    36Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-16728Jul 29, 2026 · undici vulnerable to downstream response desynchronization via retry interceptor
    26Monitor
  • ← EarlierCVE-2026-14643Jul 29, 2026 · undici vulnerable to cross-user information disclosure via whitespace around equals in Cache-Control directives
    30Monitor
  • Later →CVE-2026-84933Sep 4, 2026 · undici vulnerable to cross-user cookie disclosure via Set-Cookie caching in shared caches
    32Monitor

Remediation

Which version to upgrade to

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

Product / packageFixed versionSource
undici undici6.28.0Vendor (CNA)
undici undici7.29.0Vendor (CNA)
undici undici8.9.0Vendor (CNA)
azl3 nodejs 24.18.1-1 on Azure Linux 3.024.20.0-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:node-undici8.9.0+dfsg+~cs3.2.0-1 · Debian:14Package registry (OSV)
npm:undici6.28.0Package registry (OSV)
npm:undici7.29.0Package registry (OSV)
npm:undici8.9.0Package registry (OSV)
red hat:nodejs240:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-devel0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-docs0:24.18.1-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs260:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-bin0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-devel0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-docs0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-full-i18n0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-libs0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm0:11.17.0-1.26.5.1.1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm-bin0:26.5.1-1.5.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:nodejs1616.20.2-150400.3.42.1 · SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOSPackage registry (OSV)
suse:nodejs1818.20.8-8.44.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

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.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

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

No commit or PR link among the references.

Credits

All researchers

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

Variant candidates

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

  • CVE-2026-967942 days apartundici vulnerable to HTTP header injection via Set-Cookie percent-decoding
    23Monitor
  • CVE-2026-1527139 days apartundici is vulnerable to CRLF Injection via upgrade option
    18Monitor

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

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
low · data can be read
Integrity
low · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records