Intel

AIKIDO-2026-846025

undici is vulnerable to Improper Certificate Validation

CVE-2026-109383Published Oct 19, 2026
October 19, 2026

74

CVE Score

High

Improper Certificate Validation

Are you affected? Scan for Free

TL;DR

Agent deep-clones its constructor options with JSON before forwarding them to each per-origin Pool, which silently drops function-valued tls options such as a caller-supplied checkServerIdentity. A certificate the application was written to reject (e.g. for certificate or public-key pinning) is then accepted if it still passes Node's default hostname and chain checks. Agent is the default dispatcher behind request, fetch, and setGlobalDispatcher, and EnvHttpProxyAgent is also affected on its direct and NO_PROXY routes. Passing the same options through connect is not affected. The fix preserves the tls option outside the JSON clone so custom verification callbacks reach each origin.

How do I fix this?

Upgrade the undici library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you pass a function-valued tls option (such as a custom checkServerIdentity) to an Agent or EnvHttpProxyAgent.

Package

Versions

4.0.0 - 6.29.0

Fixed in 6.29.1

7.0.0 - 7.30.0

Fixed in 7.30.1

8.0.0 - 8.12.1

Fixed in 8.12.2

Background info

undici is vulnerable to Improper Certificate Validation in versions 4.0.0 - 6.29.0, 7.0.0 - 7.30.0 and 8.0.0 - 8.12.1.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea