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.
Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion
Problem type
Affected products
nodemailer
< 10.0.2 - AFFECTED
10.0.2 - UNAFFECTED
References
https://github.com/nodemailer/nodemailer/security/advisories/GHSA-6vj9-mwq6-2f5v
https://www.vulncheck.com/advisories/nodemailer-5.0.0-through-10.0.1-tls-servername-cache-confusion
GitHub Security Advisories
GHSA-2mg4-38wg-2h6f
Nodemailer versions 5.0.0 through 10.0.1 use a process-global DNS cache that is keyed only by the...
https://github.com/advisories/GHSA-2mg4-38wg-2h6fNodemailer 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.
https://github.com/nodemailer/nodemailer/security/advisories/GHSA-6vj9-mwq6-2f5v
https://nvd.nist.gov/vuln/detail/CVE-2026-100701
https://www.vulncheck.com/advisories/nodemailer-5.0.0-through-10.0.1-tls-servername-cache-confusion
https://github.com/advisories/GHSA-2mg4-38wg-2h6f
JSON source
https://cveawg.mitre.org/api/cve/CVE-2026-100701Click to expand
{
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"cveMetadata": {
"cveId": "CVE-2026-100701",
"assignerOrgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"assignerShortName": "VulnCheck",
"dateUpdated": "2026-09-26T23:11:37.880Z",
"dateReserved": "2026-09-26T02:39:50.973Z",
"datePublished": "2026-09-26T13:23:57.215Z",
"state": "PUBLISHED"
},
"containers": {
"cna": {
"providerMetadata": {
"orgId": "83251b91-4cc7-4094-a5c7-464a1b83ea10",
"shortName": "VulnCheck",
"dateUpdated": "2026-09-26T13:23:57.215Z"
},
"datePublic": "2026-09-10T00:00:00.000Z",
"title": "Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion",
"descriptions": [
{
"lang": "en",
"value": "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": [
{
"vendor": "nodemailer",
"product": "nodemailer",
"defaultStatus": "unaffected",
"versions": [
{
"version": "5.0.0",
"status": "affected",
"versionType": "semver",
"lessThan": "10.0.2"
},
{
"version": "10.0.2",
"status": "unaffected",
"versionType": "semver"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"lang": "en",
"description": "Improper Certificate Validation",
"cweId": "CWE-295",
"type": "CWE"
}
]
}
],
"references": [
{
"url": "https://github.com/nodemailer/nodemailer/security/advisories/GHSA-6vj9-mwq6-2f5v",
"name": "GitHub Security Advisory (GHSA-6vj9-mwq6-2f5v)",
"tags": [
"vendor-advisory"
]
},
{
"url": "https://www.vulncheck.com/advisories/nodemailer-5.0.0-through-10.0.1-tls-servername-cache-confusion",
"name": "VulnCheck Advisory: Nodemailer 5.0.0 through 10.0.1 TLS servername Cache Confusion",
"tags": [
"third-party-advisory"
]
}
],
"metrics": [
{
"format": "CVSS"
},
{
"format": "CVSS",
"cvssV3_1": {
"version": "3.1",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:L/A:N",
"attackVector": "NETWORK",
"attackComplexity": "HIGH",
"privilegesRequired": "LOW",
"userInteraction": "NONE",
"scope": "UNCHANGED",
"confidentialityImpact": "HIGH",
"integrityImpact": "LOW",
"availabilityImpact": "NONE",
"baseScore": 5.9,
"baseSeverity": "MEDIUM"
}
}
],
"credits": [
{
"lang": "en",
"value": "ry2811",
"type": "reporter"
}
]
},
"adp": [
{
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-09-26T23:11:37.880Z"
},
"title": "CISA ADP Vulnrichment",
"metrics": [
{}
]
}
]
}
}