Skip to content
Noroxi
NVD / CVE Program· CNA openjs

CVE-2026-9675: undici WebSocket client vulnerable to denial of service via cumulative fragment bypass

Noroxi assessment

Priority: Monitor (action score 30/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.48% (FIRST EPSS).
  • 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: undici undici 8.5.0; azl3 nodejs 24.14.1-3 on Azure Linux 3.0 24.17.0-1.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to undici undici 8.5.0; azl3 nodejs 24.14.1-3 on Azure Linux 3.0 24.17.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

Impact: The undici WebSocket client enforces maxPayloadSize per-frame but does not enforce the cumulative size of fragmented uncompressed messages. A malicious WebSocket server can stream many small fragments that each pass per-frame validation but collectively exceed the configured limit, causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. This is a regression specific to undici 8.1.0. The 6.25.0 line shipped the equivalent cumulative check from the start and is unaffected. The 7.x line never had the maxPayloadSize feature and is also unaffected. Patches: Upgrade to undici >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Jun 17, 2026
Updated
Jun 25, 2026
EPSS
0.4% · 41th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

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

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · openjs
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
  • 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-9675

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.

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 undici8.0.0 and later · before 8.5.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

    • 8.5.0not affected
    • 8.0.0 and later · before 8.5.0affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
npmundicifrom 8.0.0 · before 8.5.08.5.0
Red Hat:hummingbird:1cargobefore 0:1.96.0-1.hum10:1.96.0-1.hum1
Red Hat:hummingbird:1clippybefore 0:1.96.0-1.hum10:1.96.0-1.hum1
Red Hat:hummingbird:1nodejs24before 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-binbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-develbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-docsbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-full-i18nbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-libsbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs24-npmbefore 0:11.13.0-1.24.16.0.1.hum10:11.13.0-1.24.16.0.1.hum1
Red Hat:hummingbird:1nodejs24-npm-binbefore 0:24.16.0-1.hum10:24.16.0-1.hum1
Red Hat:hummingbird:1nodejs25before 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-binbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-develbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-docsbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-full-i18nbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-libsbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs25-npmbefore 0:11.12.1-1.25.9.0.1.1.hum10:11.12.1-1.25.9.0.1.1.hum1
Red Hat:hummingbird:1nodejs25-npm-binbefore 0:25.9.0-1.1.hum10:25.9.0-1.1.hum1
Red Hat:hummingbird:1nodejs26before 0:26.3.0-1.2.hum10:26.3.0-1.2.hum1
Red Hat:hummingbird:1nodejs26-binbefore 0:26.3.0-1.2.hum10:26.3.0-1.2.hum1
Red Hat:hummingbird:1nodejs26-develbefore 0:26.3.0-1.2.hum10:26.3.0-1.2.hum1
Red Hat:hummingbird:1nodejs26-docsbefore 0:26.3.0-1.2.hum10:26.3.0-1.2.hum1
Red Hat:hummingbird:1nodejs26-full-i18nbefore 0:26.3.0-1.2.hum10:26.3.0-1.2.hum1

+20

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-2581Mar 12, 2026 · undici is vulnerable to Unbounded Memory Consumption in in Undici's DeduplicationHandler via Response Buffering leads to DoS
    23Monitor
  • ← EarlierCVE-2026-12151Jun 17, 2026 · undici WebSocket client vulnerable to denial of service via fragment count bypass
    30Monitor
  • Later →CVE-2026-11525Jun 17, 2026 · undici vulnerable to Set-Cookie SameSite attribute downgrade via permissive substring matching
    14Monitor

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 undici8.5.0Vendor (CNA)
azl3 nodejs 24.14.1-3 on Azure Linux 3.024.17.0-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
npm:undici8.5.0Package registry (OSV)
red hat:cargo0:1.96.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:clippy0:1.96.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs240:24.16.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.16.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs250:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs25-bin0:25.9.0-1.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs260:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-bin0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-devel0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-docs0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-full-i18n0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-libs0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm0:11.16.0-1.26.3.0.1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm-bin0:26.3.0-1.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:rust0:1.96.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:rust-analyzer0:1.96.0-1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:rust-debugger-common0:1.96.0-1.hum1 · Red Hat:hummingbird:1Package 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.

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-121510 days apartundici WebSocket client vulnerable to denial of service via fragment count bypass
    30Monitor
  • CVE-2026-109932120 days apartundici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering
    30Monitor

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.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

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.

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

Vulnerable

ts
function expand(node) {  return node.children.map(expand);}

Fixed

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

Attack context

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

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