Node.js undici Flaw CVE-2026-109383: Update Now
Published October 28, 2026 · Last updated October 28, 2026
The short version: CVE-2026-109383 is a critical-severity security flaw in Node.js undici. The National Vulnerability Database (NVD) published it on October 15, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on October 28, 2026, CISA had not added CVE-2026-109383 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.
What the official record says about CVE-2026-109383
The record was filed by ce714d77-add3-4f53-aff5-83d477b104bb. In its own words: "undici is an HTTP client library for Node.js. In versions 4.0.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its Agent dispatcher passes its constructor options through a JSON-based deep clone before forwarding them to each per-origin pool, and because JSON cannot represent functions, a caller-supplied tls option containing a checkServerIdentity callback is silently dropped before it reaches the TLS layer. As a result, a TLS peer whose certificate a custom checkServerIdentity was written to reject, but which passes Node's default hostname and chain checks, is silently accepted. Because Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, this affects the path most applications use, and EnvHttpProxyAgent is affected on its direct and no-proxy routes as well, while only applications that pass a function-valued tls option such as a custom checkServerIdentity for certificate or public-key pinning are at risk. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which preserve the tls option outside the JSON clone so custom verification callbacks are forwarded unchanged, and users should upgrade to one of those versions or later. As a workaround, pass the TLS options through connect instead of tls, or for proxied destinations use requestTls and proxyTls."
Why undici admins should care
Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on nist.gov rated CVE-2026-109383 9.1 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping undici running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.
Scores can differ between the vendor and NVD because each judges the worst realistic case differently. For this flaw, ce714d77-add3-4f53-aff5-83d477b104bb gives it 7.4 (High, CVSS 3.1).
Affected undici releases
According to the record, these releases are vulnerable:
- 4.0.0 up to, but not including, 6.29.1
- 7.0.0 up to, but not including, 7.30.1
- 8.0.0 up to, but not including, 8.12.2
The type of bug behind CVE-2026-109383
NVD classifies it using MITRE's Common Weakness Enumeration:
- CWE-295, Improper Certificate Validation. MITRE describes this class of bug as follows: "The product does not validate, or incorrectly validates, a certificate."
Vendor remediation for CVE-2026-109383
The vendor advisory remediation for operators of undici, quoted for this page, is: "Upgrade undici past the affected ranges listed in GitHub advisory GHSA-2m5v-pch6-74hx (newer than 6.29.0, 7.30.0, or 8.12.1, depending on your release line). Node.js's built-in fetch is built on undici, so also check that your Node.js release includes a fixed undici."
What to do about it
- Update now: Upgrade undici past the affected ranges listed in GitHub advisory GHSA-2m5v-pch6-74hx (newer than 6.29.0, 7.30.0, or 8.12.1, depending on your release line). Node.js's built-in fetch is built on undici, so also check that your Node.js release includes a fixed undici.
- Who should act: IT teams, managed service providers, and developers who run or ship undici. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
- Read the official advisory from Node.js (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
- After patching, confirm the new version is actually running and review logs from October 15, 2026 onward for anything unusual.
- Home users: you do not need to buy or download anything because of CVE-2026-109383. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.
CVE-2026-109383 record details from CISA and NVD
- Attack complexity for CVE-2026-109383: low
- CVE-2026-109383 CVSS scope: unchanged
- NVD sub-scores for CVE-2026-109383: exploitability 3.9, impact 5.2.
- Who mapped the weakness type: ce714d77-add3-4f53-aff5-83d477b104bb (Secondary)
- NVD product identifiers (CPE):
cpe:2.3:a:nodejs:undici:*:*:*:*:*:node.js:*:* - References in the NVD record: 2 (2 tagged Vendor Advisory, 1 tagged Mitigation).
- CISA SSVC decision points for CVE-2026-109383 (from NVD): exploitation=none; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).
Dates to know
- October 15, 2026: NVD publishes CVE-2026-109383.
- October 28, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-109383 is not listed.
- October 19, 2026: most recent NVD update (record status: Analyzed).
Official references
Links listed in the NVD record (labels in brackets come from NVD):
- cna.openjsf.org/security-advisories.html (Vendor Advisory)
- github.com/nodejs/undici/security/advisories/GHSA-2m5v-pch6-74hx (Mitigation, Vendor Advisory)
Sources
General education only, not security advice. Facts checked against the sources above on the date shown.