CVE-2026-100699

Nodemailer before 10.0.9 Malformed Envelope Recipient via RFC 5322 Comment

Published Sep 26, 2026 CVSS 4.0 · 6.9 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An address parsing flaw in Nodemailer causes quoted local‑part addresses followed by RFC 5322 comments to be normalized into a value that includes attacker‑controlled domain text separated by a literal space. The resulting address is stored in the SMTP envelope without further validation, so an application that accepts user input could send a message to an unintended recipient or a domain that the application otherwise forbids. This may enable malicious payloads to be delivered or cause mail loss due to deceptive address resolution.

Affected Systems

The flaw resides in Nodemailer versions from 9.1.0 through 10.0.8 inclusive. Users running any of those releases on Node.js should check the installed package and verify the version. The problem is triggered only when the local part of the address is quoted and immediately followed by a comment containing domain atoms. Authentication or envelope construction code that relies on Nodemailer without additional input checks is vulnerable.

Risk and Exploitability

With a CVSS score of 6.9 the vulnerability presents moderate risk. The EPSS score is currently unavailable, and the issue is not listed in the CISA KEV catalog. Exploitation requires an attacker who can supply a crafted recipient address to an application that passes it unvalidated to Nodemailer. If such an input is accepted, the library builds an SMTP envelope containing the malformed address, which may allow the sending of messages to unintended recipients or misuse of the mail system. Based on the description, the likely attack vector is via user‑controlled input such as form fields or API payloads that supply email recipients. No confirmation exists that mail would be routed to the attacker’s domain on live SMTP servers, but the lack of strict validation creates a potential for abuse.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Nodemailer to version 10.0.9 or later, which includes the address‑parsing fix.
  • If an upgrade cannot be performed immediately, add explicit validation of recipient addresses before they reach Nodemailer, rejecting any address that contains comments or unexpected domain text.
  • Route outgoing mail through a validated relay that inspects the envelope and rejects suspicious addresses, adding an extra layer of control.

Generated by OpenCVE AI on September 27, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Nodemailer before 10.0.9 Malformed Envelope Recipient via RFC 5322 Comment
First Time appeared Nodemailer
Nodemailer nodemailer
Weaknesses CWE-20
CPEs cpe:2.3:a:nodemailer:nodemailer:*:*:*:*:*:*:*:*
Vendors & Products Nodemailer
Nodemailer nodemailer
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

cvssV4_0

{'score': 6.9, 'vector': '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'}

Weaknesses
  • CWE-1286

    Improper Validation of Syntactic Correctness of Input

  • CWE-20

    Improper Input Validation

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 28, 2026, 5:43 PM
Reserved
Sep 26, 2026, 2:39 AM
Status
Awaiting Analysis
Published
Sep 26, 2026, 2:16 PM
Modified
Sep 30, 2026, 4:32 PM
Severity
Moderate
Public date
Sep 26, 2026, 1:23 PM