Skip to main content
VulnerabilityPublished

CVE-2026-125755: nodemailer · Interpretation Conflict

Affects nodemailerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.3 High : upgrade to 10.4.1 soon.

Data as of 10 Nov 2026, 15:34 UTC

CVSS 4.0 base score
8.3High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.3
CNA (VulnCheck)CVSS 3.16.5
Patch
Available – fixed in 10.4.1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Upgrade nodemailer to 10.4.1.

Affected software

ProductAffectedFixed in
nodemailernodemailerAffected
  • >=3.0.0 <10.4.1
Fixed in
  • 10.4.1
npmnodemailerpkg:npm/nodemailerOther threatsAffected
  • >=3.0.0 <10.4.1
Fixed in
  • 10.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should upgrade Nodemailer to version 10.4.1 or later, where this address parsing flaw has been fixed. No other mitigation steps are indicated by the vendor advisory or data provided.

Description

Nodemailer versions from 3.0.0 up to but not including 10.4.1 contain an address parsing flaw in the addressparser component. This flaw causes domains to be truncated at folding whitespace or comments before a dot, which can allow attackers to bypass recipient domain restrictions. By crafting to, cc, bcc, or replyTo addresses that appear valid under RFC 5322 domain checks, attackers can cause mail to be delivered to an attacker-controlled address while preserving the application's sender identity. This vulnerability has a high severity score of 8.3 and was fixed in version 10.4.1.

References

Community reviews

Loading reviews…