What’s Vulnerable › Vulnerabilities
CVE-2026-100699: Nodemailer before 10.0.9 Malformed Envelope Recipient via RFC 5322 Comment
- Severity: medium (CVSS 5.3 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.2% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-09-26 · updated 2026-09-30
- Weakness: CWE-20
Description
Nodemailer is a Node.js email-sending library. In versions >= 9.1.0 and < 10.0.9, the address parser (src/addressparser) mishandles addresses whose local-part is a quoted string and that are followed by RFC 5322 comments, allowing trailing comment-separated domain atoms to be retained in the normalized address. For example, the input "user"@example.com(x)evil.com is parsed to the address value 'user@example.com evil.com', which contains additional attacker-controlled domain text separated by a literal space. This parsed value is used without further strict recipient validation when the message envelope is built (envelope.to in src/mime-node), so a malformed/ambiguous recipient address can be accepted and placed in the SMTP envelope. Whether this results in delivery to an unintended recipient on real SMTP servers has not been confirmed. The issue is a variant of the RFC 5322 comment parsing problem addressed in GHSA-cc9r-2j5m-2m83, affecting the separate quoted-local-part code path. Version 10.0.9 contains a fix.
Affected products
- nodemailer: from 9.1.0 before 10.0.9 — fixed in 10.0.9
How to fix
Upgrade to a fixed version: nodemailer 10.0.9. Check the vendor advisory for mitigations.
References
- https://github.com/nodemailer/nodemailer/security/advisories/GHSA-g57g-f23g-4646
- https://www.vulncheck.com/advisories/nodemailer-before-10.0.9-malformed-envelope-recipient-via-rfc-5322-comment
- https://github.com/nodemailer/nodemailer/security/advisories/GHSA-g57g-f23g-4646
Get alerted when CVE-2026-100699 or the next vulnerability affects your stack