CVE-2026-9697Nodejs Undici
NVDCVSS scored by ce714d77-add3-4f53-aff5-83d477b104bb
Vulnerability Summary
Impact:
undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert, key, rejectUnauthorized, and servername settings.
Applications that pin to an internal or corporate CA via requestTls.ca will, when their proxy URI is SOCKS5, get the default Mozilla CA bundle as the trust anchor instead. Any cert signed by any publicly-trusted CA for the target hostname is accepted, breaking the intended pin and enabling MITM read and tamper of the HTTPS exchange.
Affected applications are those that use undici's ProxyAgent (or Socks5ProxyAgent directly) with SOCKS5 AND rely on requestTls for TLS scope restriction. The bug was introduced in undici 7.23.0 when SOCKS5 support was added.
Patches:
Upgrade to undici v7.28.0 or v8.5.0.
Workarounds:
No workaround is available within the SOCKS5 path. If a SOCKS5 proxy with TLS scope restriction is required and an upgrade is not yet possible, route the traffic through an HTTP-proxy ProxyAgent instead, where requestTls is honored correctly.
undici's ProxyAgent silently drops the requestTls option when configured with a SOCKS5 proxy URI (socks5:// or socks://). The target HTTPS connection through the SOCKS5 tunnel falls back to Node's default trust store, ignoring user-configured ca, cert, key, rejectUnauthorized, and servername settings.
Applications that pin to an internal or corporate CA via requestTls.ca will, when their proxy URI is SOCKS5, get the default Mozilla CA bundle as the trust anchor instead. Any cert signed by any publicly-trusted CA for the target hostname is accepted, breaking the intended pin and enabling MITM read and tamper of the HTTPS exchange.
Affected applications are those that use undici's ProxyAgent (or Socks5ProxyAgent directly) with SOCKS5 AND rely on requestTls for TLS scope restriction. The bug was introduced in undici 7.23.0 when SOCKS5 support was added.
Patches:
Upgrade to undici v7.28.0 or v8.5.0.
Workarounds:
No workaround is available within the SOCKS5 path. If a SOCKS5 proxy with TLS scope restriction is required and an upgrade is not yet possible, route the traffic through an HTTP-proxy ProxyAgent instead, where requestTls is honored correctly.
CVSS v3.1 Base Metrics — Score 7.4 (HIGH)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:NAttack VectorNetwork
Attack ComplexityHigh
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
Affected & Patched Versions
- Nodejs Undici >= 7.23.0 and < 7.28.0
- Nodejs Undici >= 8.0.0 and < 8.5.0
- Nodejs Undici 7.28.0
- Nodejs Undici 8.5.0
What to do
Plan remediation soon. No exploitation is confirmed yet, but the severity is high.
- Check whether you run Nodejs Undici and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Jun 17, 2026Published
- Sep 9, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Nodejs Undici CVEsYou are reading CVE-2026-9697. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Vendor Advisoryhttps://cna.openjsf.org/security-advisories.html
- Vendor Advisoryhttps://github.com/nodejs/undici/security/advisories/GHSA-vmh5-mc38-953g
- Referencehttps://access.redhat.com/errata/RHSA-2026:22380
- Referencehttps://access.redhat.com/errata/RHSA-2026:22934
- Referencehttps://access.redhat.com/errata/RHSA-2026:34342
- Referencehttps://access.redhat.com/errata/RHSA-2026:35841
- Referencehttps://access.redhat.com/errata/RHSA-2026:35891
- Referencehttps://access.redhat.com/errata/RHSA-2026:36621
- Referencehttps://access.redhat.com/errata/RHSA-2026:36754
- Referencehttps://access.redhat.com/errata/RHSA-2026:36820
- Referencehttps://access.redhat.com/errata/RHSA-2026:38236
- Referencehttps://access.redhat.com/errata/RHSA-2026:39868
- Referencehttps://access.redhat.com/errata/RHSA-2026:41929
- Referencehttps://access.redhat.com/errata/RHSA-2026:47728
- Referencehttps://access.redhat.com/errata/RHSA-2026:48124
- Referencehttps://access.redhat.com/errata/RHSA-2026:48151
- Referencehttps://access.redhat.com/errata/RHSA-2026:56366
- Referencehttps://access.redhat.com/errata/RHSA-2026:56431
- Referencehttps://access.redhat.com/errata/RHSA-2026:57013
- Referencehttps://access.redhat.com/errata/RHSA-2026:60520
- Referencehttps://access.redhat.com/errata/RHSA-2026:65126
- Referencehttps://access.redhat.com/errata/RHSA-2026:7378
- Vendor Advisoryhttps://access.redhat.com/security/cve/CVE-2026-9697
- Issue Trackinghttps://bugzilla.redhat.com/show_bug.cgi?id=2490018
- Referencehttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-9697.json
Data last checked: Nov 19, 2026 11:13 UTC