CVE-2026-90776

7.5

Nodemailer · addressparser

Nodemailer's addressparser component is vulnerable to a quadratic time complexity flaw when parsing RFC 5322 email comments, allowing attackers to trigger a denial of service via CPU exhaustion.

Executive summary

A quadratic time complexity vulnerability in the Nodemailer addressparser component allows unauthenticated attackers to cause a denial of service by blocking the Node.js event loop.

Vulnerability

The vulnerability exists within the address parsing logic, specifically when handling RFC 5322 comments. An unauthenticated attacker can supply specially crafted email headers containing comment-separated atoms to trigger excessive CPU consumption, effectively freezing the Node.js event loop.

Business impact

Successful exploitation results in a denial of service, which can render applications utilizing Nodemailer unresponsive. Because this vulnerability targets the Node.js event loop, it can impact the availability of the entire application process rather than just the email parsing function. With a CVSS score of 7.5, this represents a significant risk to service continuity and operational stability for any platform handling external email inputs.

Remediation

Immediate Action: Update the Nodemailer package to version 10.0.5 or later, which contains the necessary algorithmic improvements to address the quadratic complexity issue.

Proactive Monitoring: Monitor server CPU utilization and Node.js event loop latency for sudden spikes that correlate with incoming email processing requests.

Compensating Controls: Implement input validation or size limits on email header fields at the Web Application Firewall or proxy level to prevent excessively large or complex address strings from reaching the application.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

This high-severity vulnerability poses a direct threat to application availability. Administrators should prioritize updating the Nodemailer dependency to version 10.0.5 immediately to eliminate the risk of service disruption. If an immediate update is not feasible, ensure that rigorous input sanitization is applied to all email headers before they are processed by the addressparser component.

More Nodemailer CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by mmadersbacher, per the CVE Program record.