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 Address Parsing Bypass via Nested Comments

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-121424

Published

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit addresses whose nested comment hides an attacker address, bypassing conformant validators and recipient allow lists to receive mail or spoof senders in mailparser.

Read the publisher's advisory

euvd · EUVD-2026-115956

Published

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit addresses whose nested comment hides an attacker address, bypassing conformant validators and recipient allow lists to receive mail or spoof senders in mailparser.

Read the publisher's advisory

nvd · CVE-2026-121424

Published

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit addresses whose nested comment hides an attacker address, bypassing conformant validators and recipient allow lists to receive mail or spoof senders in mailparser.

Read the publisher's advisory

osv · GHSA-8c8m-p3m8-cjg8

Published

### Vulnerability summary RFC 5322 comments nest. addressparser ended a comment at the first `)`, including the one that closes a nested comment, and parsed the rest of the outer comment as header text. `Victim (x(y) <[email protected]>) <[email protected]>` names `[email protected]` with `x(y) <[email protected]>` as a comment, and Nodemailer read it as the address `[email protected]`. This is the same shape as the escaped parenthesis fixed in 10.1.2, reached through nesting instead of a quoted-pair. Affected: 3.0.0 through 10.1.3. ### Attacker capabilities The attacker controls the text of an address that an application passes to Nodemailer, or the From or To 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 address that conformant parsers accept without defects. ### Realistic exploitation scenario An application validates a submitted address with a conformant parser and allows only its own domain. The attacker submits `Victim (x(y) <[email protected]>) <[email protected]>`, which validates as `[email protected]`. Nodemailer delivers to `[email protected]`. In the inbound direction, a DMARC or display layer built on a conformant parser and a mail client built on mailparser disagree on the author of the same message, which is the setting for sender spoofing. The boundary crossed is the application's recipient allow list, or the author check of the receiving side. ### Proof of concept ```js const addressparser = require('nodemailer/lib/addressparser'); console.log(addressparser("Victim (x(y) <[email protected]>) <[email protected]>")); // [ { address: '[email protected]', name: 'Victim) [email protected]' } ] ``` Python's `email._header_value_parser.get_address_list` reads the same value as `[email protected]` with the display name `Victim`, with no defects reported. The envelope a message gets is built from the same parse, so `sendMail({ to: "Victim (x(y) <[email protected]>) <[email protected]>" })` issues the RCPT TO shown above. ### Security impact Mail intended for an approved recipient is delivered to an attacker chosen domain, disclosing its content, and parsers built on this module report a different author than conformant ones. The misreading only occurs on values a conformant validator approves, so correct validation is bypassed. Affected are applications that pass user influenced addresses to Nodemailer and consumers of the standalone parser such as mailparser. The fix counts comment depth and ends a comment only at the `)` that closes the outermost one. 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

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

Risk history

Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.

When does an EPSS score appear as a change?

A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).

Advisory history

15 saved versions

See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.

How advisory history works

Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.

22 Nov 2026 09:30:13 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

20 Nov 2026 09:22:00 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

18 Nov 2026 08:27:26 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

16 Nov 2026 07:34:15 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

14 Nov 2026 07:01:57 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

12 Nov 2026 06:54:37 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

10 Nov 2026 06:05:03 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

8 Nov 2026 05:08:11 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

6 Nov 2026 04:38:31 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

4 Nov 2026 03:59:45 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

euvd · EUVD-2026-115956 · Published

4 Nov 2026 03:59:20 UTC

Nodemailer from 3.0.0 before 10.1.4 contains an address parsing vulnerability in addressparser that allows remote attackers to redirect recipients by ending nested RFC 5322 comments at the first closing parenthesis. Attackers can submit add…

nvd · CVE-2026-121424 · Published

4 Nov 2026 03:57:35 UTC

Nodemailer: A nested comment ends early in addressparser, releasing the rest of the comment as a recipient

osv · GHSA-8c8m-p3m8-cjg8 · Published

3 Nov 2026 19:57:16 UTC

Nodemailer 3.0.0 before 10.1.4 Address Parsing Bypass via Nested Comments

cve-program · CVE-2026-121424 · Published

3 Nov 2026 15:57:17 UTC

Nodemailer 3.0.0 before 10.1.4 Address Parsing Bypass via Nested Comments

cve-program · CVE-2026-121424 · Published

24 Oct 2026 13:17:17 UTC

Nodemailer: A nested comment ends early in addressparser, releasing the rest of the comment as a recipient

osv · GHSA-8c8m-p3m8-cjg8 · Published

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 22 Nov 13:22 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current