llamaCVEVulnerability Intelligence
/
Advisory · GitHub · npm · nodemailer

GHSA-85X2-Q946-CP5H

Nodemailer: A ">" inside a quoted local part ends an angle-addr early in addressparser, delivering to a domain the header does not name

Parche disponible
Descargar PNG JSON
CVSS
—
medium
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche1 versiónPrimer parche a -5 d de la divulgación
Exposición27 dDesde la divulgación, 23 oct 2026, 4:51 p. m.
Detección47 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Modificada
Explotación
Remediación
Parche 10.1.4
Monitoreo
Detectada
Verificada
18 oct 26
23 oct 26
4 nov 26
16 nov 26
20 nov 26
18 oct 26
26 oct 26
3 nov 26
11 nov 26
20 nov 26
FechaFaseEventoDetalle
Remediación Parche 10.1.4 nodemailer · -5 d desde divulgación
Divulgación Publicada GHSA-85X2-Q946-CP5H divulgada
Monitoreo Detectada Ingresó al índice
Divulgación Modificada Última actualización del registro
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Descripción del advisory
Texto original · GitHub · en inglés
Vulnerability summary

addressparser ends an angle-addr at the first `>` it sees, including one inside a quoted local part, a comment or a domain literal. The domain is then read off the text in front of that `>`. `<"a@evil.com>"@good.com>` is the mailbox `"a@evil.com>"@good.com` under RFC 5322, and Nodemailer read it as an address at `evil.com`. The unbracketed spelling of the same value was already read correctly. Affected: 3.0.0 through 10.1.3.

Attacker capabilities

The attacker controls the text of a recipient or sender address that an application passes to Nodemailer, for example a To value entered in a contact or invite form, 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 address that conformant parsers accept without defects.

Realistic exploitation scenario

An application lets users send invitations or notifications only to addresses at an allowed domain and validates the submitted value with a conformant parser or by checking its domain. The attacker submits `<"a@evil.com>"@good.com>`, which validates as a `good.com` mailbox. Nodemailer then parses the same value, issues `RCPT TO:<"\"a"@evil.com>` and the message, with whatever content the application puts into it, is delivered to the attacker's domain. The security boundary crossed is the application's recipient allow list. In the inbound direction, mailparser reports a different address than a conformant reader of the same header, so a display or policy layer built on the two disagrees.

Proof of concept
const addressparser = require('nodemailer/lib/addressparser');
console.log(addressparser("<\"a@evil.com>\"@good.com>"));
// [ { address: '"a@evil.com', name: '@good.com>' } ]

Python's `email._header_value_parser.get_address_list` reads the same value as `"a@evil.com>"@good.com`, with no defects reported.

The envelope a message gets is built from the same parse, so `sendMail({ to: "<\"a@evil.com>\"@good.com>" })` issues the RCPT TO shown above.

Security impact

Mail that an application intends for an allowed domain is delivered to a domain chosen by the attacker, which discloses its content. It is a security vulnerability rather than a parsing bug because the misreading only occurs for values that a conformant validator approves, so validation done the right way is bypassed. Affected are applications that pass user influenced addresses to Nodemailer and consumers of the standalone parser such as mailparser.

The fix tracks quoted strings, comments and domain literals inside an angle-addr 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.

Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.

Versiones

Rangos afectados

Afectada Corregida Última
nodemailer≥ 3.0.0 < 10.1.4
3.0.0
10.1.4
10.6.0
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
npmnodemailer
Corregida 10.1.4 -5 d 10.6.0 no afectada
Versiones corregidas10.1.4
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Otrahttps://github.com/nodemailer/nodemailer/security/advisories/GHSA-85x2-q946-cp5h
Otrahttps://github.com/nodemailer/nodemailer/commit/1cd57d2b8c49dff048c21cdbafdb54439a7f07e2
Otrahttps://github.com/nodemailer/nodemailer
Otrahttps://github.com/nodemailer/nodemailer/releases/tag/v10.1.4

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.