node-undici: undici is an HTTP client library for Node.js
CVE-2026-109383 is fixed in 21 products on 1 platform, first by DEBIAN-CVE-2026-109383, released November 1, 2026. It is not reported as exploited. Patch Radar priority: Urgent.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| node-undici · Debian 14 | 8.12.2+dfsg+~cs3.2.3-1 | DEBIAN-CVE-2026-109383 | Nov 1, 2026 |
| nodejs22 · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-debuginfo · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-debugsource · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-devel · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-docs · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-full-i18n · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-libs · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-libs-debuginfo · amzn 2023 | 1:22.23.4-1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs22-npm · amzn 2023 | 1:10.9.9-1.22.23.4.1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| nodejs24 · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-debuginfo · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-debugsource · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-devel · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-docs · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-full-i18n · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-libs · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-libs-debuginfo · amzn 2023 | 1:24.22.1-1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| nodejs24-npm · amzn 2023 | 1:11.19.1-1.24.22.1.1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
| v8-12.4-devel · amzn 2023 | 3:12.4.254.21-1.22.23.4.1.amzn2023.0.1 | ALAS2023-2026-3328 | Nov 7, 2026 |
| v8-13.6-devel · amzn 2023 | 3:13.6.233.17-1.24.22.1.1.amzn2023.0.1 | ALAS2023-2026-3330 | Nov 7, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.