undici vulnerable to Denial of Service via unbounded memory in the EventSource parser (CVE-2026-109924)
Published Last modified Sources: Red Hat, OSV, Hersteller, CVE.org
What is affected, what to do
A flaw was found in undici. A malicious server can trigger a Denial of Service (DoS) by exhausting application memory.
Update Undici to version 6.29.1, Undici to version 7.30.1, Undici to version 8.12.2.
- Affected
- Undici
lt 6.5.0..6.29.1 - Undici
lt 7.0.0..7.30.1 - Undici
lt 8.0.0..8.12.2
- Undici
- Fixed in
- Undici
6.29.1 - Undici
7.30.1 - Undici
8.12.2
- Undici
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
5.9
CVSS v3
Severity Medium on the scale from 0 to 10.
Source: Red Hat, OSV, Hersteller, CVE.org
0.3 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 25.1
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 64.52 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 5.9
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.3 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 25.1
- Elevated — this CVE ranks above at least 10% of all CVEs scored today.
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 16 October 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-770
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in undici. A malicious server can trigger a Denial of Service (DoS) by exhausting application memory. When an application connects to an untrusted Server-Sent Events (SSE) feed, the EventSource parser does not properly limit retained internal state when processing fragmented lines or repeated message fields. This allows an attacker to send crafted or compressed responses that consume excessive memory and terminate the application process.
Source: redhat_csaf, OSV (Open Source Vulnerabilities), GitHub Security Advisories, NVD (NIST), cvelistv5
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| undici | undici |
|
|
| nodejs | undici |
|
|
| npm | undici |
|
|
Vendors and products
Weakness classes (CWE)
CWE-770Allocation of Resources Without Limits or Throttling
Base
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Entry at MITRE CWE-770
References & sources
- github.comnodejs/undici/security/advisories/GHSA-4qv8-2p9j-2685Vendor advisory, web
- cna.openjsf.orgsecurity-advisories.htmlVendor advisory, web
- NVD (NIST)vuln/detail/CVE-2026-109924advisory
- github.comnodejs/undici/commit/299162740d5f39120092277e70efacb4d151c1c6web
- github.comnodejs/undici/commit/789ef26461c648480433846607154f52d74ec9abweb
- github.comnodejs/undici/commit/c43b23fdc6b37e1283d4347408bb16800f867d9eweb
- github.comnodejs/undicipackage
- github.comnodejs/undici/releases/tag/v6.29.1web
- github.comnodejs/undici/releases/tag/v7.30.1web
- github.comnodejs/undici/releases/tag/v8.12.2web
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Initial analysis by NVDNVD
Newly listed as affected:- Nodejs undici (7.0.0 – before 7.30.1; 8.0.0 – before 8.12.2; 6.5.0 – before 6.29.1)
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HProduct configuration added —OR *cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:* versions from (including) 7.0.0 up to (excluding) 7.30.1 *cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:* versions from (including) 8.0.0 up to (excluding) 8.12.2 *cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:* versions from (including) 6.5.0 up to (excluding) 6.29.1Reference type added —openjs: https://cna.openjsf.org/security-advisories.html Types: Vendor AdvisoryReference type added —openjs: https://github.com/nodejs/undici/security/advisories/GHSA-4qv8-2p9j-2685 Types: Vendor AdvisorySource identifier: nvd@nist.gov
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: no
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-109924","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-10-16T20:05:08.940657Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedOpenJS Foundation
CVSS V3.1: AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness type: CWE-770
Description added or changed
Show 6 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —undici is an HTTP client library for Node.js. In versions 6.5.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its EventSource client can be driven to exhaust process memory by a malicious or compromised Server-Sent Events peer. By sending millions of tiny completed data fields with no blank event separator, or a single unfinished line split across many chunks, the parser retains a growing amount of per-field and per-chunk state that the byte-based maxEventSize and maxResponseSize limits do not bound, and because maxResponseSize is enforced on the compressed body before decompression, a small compressed response can expand into enough retained memory to terminate the process. An application only needs to maintain an EventSource connection to an untrusted peer, which controls only the response, and availability is the only impact. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which bound the retained parser state independently of the byte limits, and users should upgrade to one of those versions or later. There is no workaround.CVSS added —AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HWeakness type (CWE) added —CWE-770Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/109xxx/CVE-2026-109924.json">CVE-2026-109924</a>Reference added —https://cna.openjsf.org/security-advisories.htmlReference added —https://github.com/nodejs/undici/security/advisories/GHSA-4qv8-2p9j-2685Source identifier: ce714d77-add3-4f53-aff5-83d477b104bb
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-109924"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-109924.svg?lang=en" alt="CVE-2026-109924 – NEOSEC Intel" height="20"></a>