Is CVE-2025-13033 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-13033 being exploited in the wild.

How severe is CVE-2025-13033?

High severity, with a CVSS score of 7.5, published 14 November 2025.

Which products and versions are affected?

Nodemailer Fixed in commit 1150d99fba77280df2cfb1885c43df23109a8626; nodemailer (npm) SEMVER:introduced=0,fixed=7.0.7.

Is there a fix for CVE-2025-13033?

Yes. nodemailer (npm): upgrade to 7.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2025-13033 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2025-13033?

Check whether you run Nodemailer or nodemailer (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2025-13033: Nodemailer improper email parsing in addressparser

CVE-2025-13033 · Severity: high · CVSS 7.5 · Published 2025-11-14

A vulnerability was found in Nodemailer, a popular library used by Node.js applications to send emails. Due to a flaw in how the library handles specially formatted email addresses, an attacker can trick the system into sending emails to an external address instead of the intended internal recipient. This could result in the leakage of sensitive information and allow attackers to bypass security filters or access controls.

Technologies: Nodemailer, nodemailer (npm). Vendors: Nodemailer, npm.

Quick answers

Is CVE-2025-13033 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-13033 being exploited in the wild.
How severe is CVE-2025-13033?: High severity, with a CVSS score of 7.5, published 14 November 2025.
Which products and versions are affected?: Nodemailer Fixed in commit 1150d99fba77280df2cfb1885c43df23109a8626; nodemailer (npm) SEMVER:introduced=0,fixed=7.0.7.
Is there a fix for CVE-2025-13033?: Yes. nodemailer (npm): upgrade to 7.0.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2025-13033 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2025-13033?: Check whether you run Nodemailer or nodemailer (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

nodemailer (npm): upgrade to 7.0.7 or later
```
npm install nodemailer@7.0.7
```

Technical details

An interpretation conflict exists in Nodemailer's address parser due to improper handling of quoted local-parts containing the '@' symbol. When a recipient address is crafted with an external address embedded within quotes (e.g., "\"user@external.com\"@internal.domain"), the parser may misroute the email to the external domain instead of the RFC-compliant internal domain. This vulnerability allows for data exfiltration, bypass of domain-based access controls, and evasion of anti-spam filters. The issue was addressed in the Nodemailer repository by fixing how the addressparser handles quoted nested email strings.

Affected products

Nodemailer Nodemailer Fixed in commit 1150d99fba77280df2cfb1885c43df23109a8626

Identifiers

CVE-2025-13033
GHSA-mm7p-fcc7-pg87

Timeline

2025-10-07: other: Bug reported to Red Hat Bugzilla
2025-11-14: disclosed: CVE published to NVD
2026-03-04: patched: Red Hat Developer Hub update released
2026-05-11: patched: Red Hat Ceph Storage update released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.