CVE-2026-100699 json
Nodemailer before 10.0.9 Malformed Envelope Recipient via RFC 5322 Comment
published 2026-09-26 43 d ago modified 2026-09-30 39 d ago also GHSA-g57g-f23g-4646 , EUVD-2026-87672
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm nodemailer 10.0.9
- nodemailer nodemailer 10.0.9
- node-nodemailer Debian 14 10.0.10+~8.0.1-1
debian advisories DEBIAN-CVE-2026-100699
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-100699 updated cvss 5.3
nodemailer: nodemailer: Malformed envelope recipient via crafted email address comments
-
Red Hat Developer Hub 1 rhdh/rhdh-hub-rhel9 Red Hat Enterprise Linux 10 grafana 12.4.3-2.el10not affected: vulnerable code not present
-
Red Hat Hardened Images grafana13.1 13.1.6-0.3.hum1, grafana13.2 13.2.1-0.6.hum1, grafana12.4 12.4.10-0.7.hum1not affected: component not present
-
Red Hat Self-service automation portal 2 ansible-automation-platform/bootc-automation-portal-rhel9not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 41 d ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/nodemailer/nodemailer/security/advisories/GHSA-g57g-f23g-4646 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| CNA | 4.0 | 6.9 | CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nodemailer | >=9.1.0, <10.0.9 |
10.0.9 |
Affected products
- nodemailer nodemailer
Classification
References
-
github.com
/nodemailer/nodemailer/commit/2f36eb1aa1dd33e312411dc9b888548e14db54ee
web
-
github.com
/nodemailer/nodemailer/security/advisories/GHSA-g57g-f23g-4646
vendor-advisory, exploit, web
-
vulncheck.com
/advisories/nodemailer-before-10.0.9-malformed-envelope-recipient-via-rfc-5322-comment
third-party-advisory
-
github.com
/nodemailer/nodemailer
package
-
github.com
/nodemailer/nodemailer/releases/tag/v10.0.9
web
Sources
- CVE List CVE-2026-100699
- GitHub Advisory GHSA-g57g-f23g-4646
- NVD CVE-2026-100699
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.