Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Nodemailer 3.0.0 before 10.1.4 Recipient Injection via addressparser Group Parsing

CVSS 4.0 8.3 HIGHCVSS 3.1 6.5 MEDIUMEUVD CVSS 4.0 8.3 CVSS 4.0 · [email protected] · Secondary 8.3 HIGHCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by nodemailer 10.1.4KEV status unknown

cve-program · CVE-2026-121425

Published

Nodemailer from 3.0.0 before 10.1.4 contains a parsing flaw in addressparser that ends an RFC 5322 group at a semicolon inside quoted display names or comments. Attackers can submit crafted group addresses that conformant validators approve, redirecting mail to attacker-chosen recipients and bypassing recipient allow lists.

Read the publisher's advisory

euvd · EUVD-2026-115957

Published

Nodemailer from 3.0.0 before 10.1.4 contains a parsing flaw in addressparser that ends an RFC 5322 group at a semicolon inside quoted display names or comments. Attackers can submit crafted group addresses that conformant validators approve, redirecting mail to attacker-chosen recipients and bypassing recipient allow lists.

Read the publisher's advisory

nvd · CVE-2026-121425

Published

Nodemailer from 3.0.0 before 10.1.4 contains a parsing flaw in addressparser that ends an RFC 5322 group at a semicolon inside quoted display names or comments. Attackers can submit crafted group addresses that conformant validators approve, redirecting mail to attacker-chosen recipients and bypassing recipient allow lists.

Read the publisher's advisory

osv · GHSA-m943-m63m-w62w

Published

### Vulnerability summary addressparser ends an RFC 5322 group at the first `;`, including one inside a quoted display name or a comment. The text after it is parsed again as top level recipients with the quoting flipped, so text that every conformant parser reads as a display name or comment becomes a live address. `G: (a; <[email protected]>) <[email protected]>;` names only `[email protected]`, and Nodemailer read it as the single recipient `[email protected]`. Affected: 3.0.0 through 10.1.3. ### Attacker capabilities The attacker controls the text of an address field that an application passes to Nodemailer, or the header of an inbound message parsed with mailparser. No access to the application, its configuration or its credentials is needed. The value is a syntactically valid RFC 5322 group that conformant parsers accept without defects. ### Realistic exploitation scenario An application validates the recipients of a submitted address list with a conformant parser and only allows addresses at its own domain. The attacker submits `G: (a; <[email protected]>) <[email protected]>;`. The validator sees one mailbox, `[email protected]`, and approves it. Nodemailer delivers to `[email protected]` only. The same works through a quoted display name, `G: "a;" "<[email protected]>" <[email protected]>;`. The boundary crossed is the application's recipient allow list. ### Proof of concept ```js const addressparser = require('nodemailer/lib/addressparser'); console.log(addressparser("G: (a; <[email protected]>) <[email protected]>;")); // [ { name: 'G', group: [ [Object] ] }, { address: '[email protected]', name: ') [email protected]' } ] ``` Python's `email._header_value_parser.get_address_list` reads the same value as the single mailbox `[email protected]`, with no defects reported. The envelope a message gets is built from the same parse, so `sendMail({ to: "G: (a; <[email protected]>) <[email protected]>;" })` issues the RCPT TO shown above. ### Security impact Mail that an application intends for an approved recipient goes to a recipient chosen by the attacker, which discloses its content, and the intended recipient never receives it. The misreading only occurs on values a conformant validator approves, so correct validation is bypassed, which makes it a security issue rather than a parsing bug. Affected are applications that pass user influenced address lists to Nodemailer and consumers of the standalone parser such as mailparser. The fix tracks quoted strings and comments inside a group and reads only a `;` outside them. Found in an internal review of addressparser on 2026-10-18. Verified on 3.0.0, 6.9.16 and 10.1.3.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-121425

Published

nodemailer

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "nodemailer",
                    "product": "nodemailer",
                    "defaultStatus": "unaffected",
                    "packageURL": "pkg:npm/nodemailer",
                    "versions": [
                        {
                            "version": "3.0.0",
                            "status": "affected",
                            "versionType": "semver",
                            "lessThan": "10.1.4"
                        },
                        {
                            "version": "10.1.4",
                            "status": "unaffected",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-115957

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 3, 2026, 2:28:20 PM

dateUpdated: Nov 3, 2026, 4:55:34 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-121425

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-20

Original publisher date fields

published: 2026-11-03T15:17:33.057

lastModified: 2026-11-03T17:18:09.250

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-m943-m63m-w62w

Published

nodemailer

npm

SEMVER · introduced 3.0.0 → fixed 10.1.4

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 06:51 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current