CVE-2026-100701

published 26 Sep 2026 · updated 26 Sep 2026

Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion

5.9MediumCVSS 5.9EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 10.0.2.

Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the DNS host, while each cache entry also stores the caller-specific TLS servername. When two direct TLS/SMTPS transports (secure: true) resolve the same non-IP host with different tls.servername values, the first transport's servername is returned on the cache hit and overwrites the second transport's explicitly configured value, so Nodemailer sends the wrong SNI value and validates the peer certificate against the wrong identity. In multi-tenant services or SNI-routed SMTP gateways, an attacker who can prime the cache can cause a victim transport to connect to the attacker's TLS virtual host and accept the attacker's certificate even with rejectUnauthorized: true, disclosing the victim's SMTP credentials. Fixed in 10.0.2.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
nodemailer>=5.0.0 <10.0.210.0.2

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-100701 severity on Zeptric[![CVE-2026-100701](https://zeptric.io/badge/cve/CVE-2026-100701.svg)](https://zeptric.io/cve/CVE-2026-100701)