Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Unrated

undici ProxyAgent SOCKS5 requestTls certificate validation bypass

IdentifiersCVE-2026-9697CWE-295

CVE-2026-9697 affects undici's ProxyAgent and Socks5ProxyAgent when configured with a SOCKS5 proxy URI (socks5:// or socks://). In the vulnerable code path introduced in undici 7.23.0, the requestTls option is silently dropped for HTTPS connections established through a SOCKS5 tunnel. As a result, user-supplied TLS validation parameters such as ca, cert, key, rejectUnauthorized, and servername are not applied to the target connection, which instead falls back to Node.js default trust store behavior. This breaks intended TLS scope restriction or private CA pinning for proxied HTTPS requests and causes certificate validation to be performed against the default Mozilla CA bundle rather than the application-configured trust anchors.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

The primary impact is a TLS certificate validation bypass for applications that depend on requestTls to constrain trust when using undici over SOCKS5. If an application expects only certificates chaining to an internal or corporate CA to be accepted, the vulnerable behavior causes any certificate for the target hostname signed by a publicly trusted CA to be accepted instead. This defeats the intended pinning or trust restriction and enables a man-in-the-middle attacker positioned on the network or proxy path to intercept, read, and modify HTTPS traffic to the target service.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available within the SOCKS5 code path itself. If upgrading is not immediately possible and SOCKS5 proxying is not strictly required, route the traffic through an HTTP-proxy ProxyAgent instead, where requestTls is honored correctly. Also review whether affected applications rely on requestTls for private CA pinning or other TLS trust restrictions when traversing proxies.

Remediation

Patch, then assume compromise.

Upgrade undici to version 7.28.0 or 8.5.0, which contain the fix for the SOCKS5 ProxyAgent handling of requestTls. The vulnerable behavior was introduced in version 7.23.0, so deployments using affected versions in that range should be updated.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NodejsUndiciapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity5

Community discussion across Reddit, Mastodon, and other social sources.