Quick answers
- Is CVE-2026-90776 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-90776 being exploited in the wild.
- How severe is CVE-2026-90776?
- High severity, with a CVSS score of 7.5, published 13 September 2026.
- Which products and versions are affected?
- Nodemailer 9.1.0 through 10.0.4; nodemailer (npm) SEMVER:introduced=9.1.0,fixed=10.0.5.
- Is there a fix for CVE-2026-90776?
- Yes. nodemailer (npm): upgrade to 10.0.5 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-90776 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-90776?
- 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 10.0.5 or later
npm install nodemailer@10.0.5
Technical details
The vulnerability is a quadratic time complexity (ReDoS-like) flaw in the addressparser component when processing RFC 5322 comments in email addresses. An attacker can craft malicious email headers with nested or repeated comment-separated atoms that trigger the quadratic parsing behavior, consuming excessive CPU and blocking the Node.js event loop for several seconds. This is a network-accessible vulnerability triggered during email address parsing. The vulnerability affects Nodemailer versions 9.1.0 through 10.0.4; users should upgrade to a patched version when available.
Affected products
- Nodemailer Nodemailer 9.1.0 through 10.0.4
Identifiers
- CVE-2026-90776
- GHSA-prgh-xp8r-p3m5
Timeline
- 2026-09-13: disclosed