CVE-2026-1528 — undici is vulnerable to Malicious WebSocket 64-bit length overflows undici parser and crashes the client
ImpactA server can reply with a WebSocket frame using the 64-bit length form and an extremely large length. undici's ByteParser overflows internal math, ends up in an invalid state, and throws a fatal TypeError that terminates the process. Patches Patched in the undici version v7.24.0 and v6.24.0. Users should upgrade to this version or later.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.5% (30-day exploitation probability)+6
- Technical severity (high)+6
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Nodejs Undici, Undici Undici).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | ce714d77-add3-4f53-aff5-83d477b104bb via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | 3.9 | 3.6 | 0b0ca135-0b70-47e7-9f44-1890c2a1c46c via NIST National Vulnerability Database |
| 7.5 | CVSS 3.1 | High | — | — | openjs via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H (score shown at the top: ce714d77-add3-4f53-aff5-83d477b104bb) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.50%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · undici/undici
- SSVC assessment updated
- Record published
- CVSS changed · 7.5
- Source status changed · → Modified
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
21 on the record
- cna.openjsf.org/security-advisories.html
- github.com/nodejs/undici/security/advisories/GHSA-f269-vfmq-vjvj
- access.redhat.com/errata/RHSA-2026:21772
- hackerone.com/reports/3537648
- bugzilla.redhat.com/show_bug.cgi
- access.redhat.com/errata/RHSA-2026:7302
- access.redhat.com/errata/RHSA-2026:5807
- access.redhat.com/errata/RHSA-2026:17789
- access.redhat.com/errata/RHSA-2026:21931
- access.redhat.com/errata/RHSA-2026:7350
- access.redhat.com/errata/RHSA-2026:13826
- access.redhat.com/errata/RHSA-2026:7670
- access.redhat.com/errata/RHSA-2026:7080
- access.redhat.com/errata/RHSA-2026:7983
- access.redhat.com/security/cve/CVE-2026-1528
- access.redhat.com/errata/RHSA-2026:34342
- access.redhat.com/errata/RHSA-2026:9742
- access.redhat.com/errata/RHSA-2026:7123
- access.redhat.com/errata/RHSA-2026:7675
- access.redhat.com/errata/RHSA-2026:7310
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-1528.json
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-87029 undici vulnerable to Denial of Service via unhandled exception in the decompress interceptor 7h
- High CVE-2026-87018 undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation 7h
- Medium CVE-2026-109932 undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering 7h
- Medium CVE-2026-109924 undici vulnerable to Denial of Service via unbounded memory in the EventSource parser 7h
- High CVE-2026-109869 undici vulnerable to Denial of Service via unhandled error on excessive content-encodings 7h
- High CVE-2026-109829 undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects 7h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-1528 is "undici is vulnerable to Malicious WebSocket 64-bit length overflows undici parser and crashes the client", rated High. It affects Undici (Nodejs); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.50% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.