Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-m943-m63m-w62w

Nodemailer: A ";" inside a quoted string or comment ends an address group early in addressparser, turning display text into a recipient

CVSS 8.3 HighEPSS 0.0032 · 25th percentile

Published by the GitHub Advisory Database at 23 Oct 2026, 21:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
nodemailernpm>=3.0.0, <10.1.410.1.4
Identifiers
GHSA-m943-m63m-w62w · CVE-2026-121425
Weakness (CWE)
CWE-20 · CWE-436
Tags
Published
23 Oct 2026
Updated
4 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nodemailer versions 3.0.0 through 10.1.3 have an addressparser flaw: a semicolon inside a quoted display name or comment within an RFC 5322 group ends the group early, so the following text is read as a top level recipient. An attacker who can control an address field passed to Nodemailer, or a header parsed with mailparser, can make mail intended for an approved address go to an attacker-chosen address, bypassing recipient validation that uses a conformant parser. Upgrade to Nodemailer 10.1.4, which is listed as the fixed version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0032, the 25th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:33 UTC First seen by agentprime
  2. 31 Oct 2026, 13:33 UTC Confirmed by OSV
  3. 3 Nov 2026, 14:38 UTC Confirmed by the CVE List
  4. 3 Nov 2026, 15:25 UTC Confirmed by NVD

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.