Quick answers
- Is CVE-2026-110872 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-110872 being exploited in the wild.
- How severe is CVE-2026-110872?
- Medium severity, with a CVSS score of 5.9, published 14 October 2026.
- Which products and versions are affected?
- Nodemailer 3.0.0 through 10.0.9; nodemailer (npm) SEMVER:introduced=3.0.0,fixed=10.0.10.
- Is there a fix for CVE-2026-110872?
- Yes. nodemailer (npm): upgrade to 10.0.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-110872 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-110872?
- 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.10 or later
npm install nodemailer@10.0.10
Technical details
The vulnerability is a quadratic (O(n²)) complexity flaw in the SMTP client reply parser (SMTPConnection._onData and isPartialResponse) that reassembles multiline server replies. When processing continuation lines without a completion line, the parser repeatedly performs string slice and test operations on an unbounded accumulated reply buffer, forcing full string flattens on each line. This stalls the single-threaded Node.js event loop during the greeting/EHLO phase, before authentication, with no size or line-count limit.
Affected products
- nodemailer nodemailer 3.0.0 through 10.0.9
Identifiers
- CVE-2026-110872
- GHSA-4g23-2xm8-66gc
Timeline
- 2026-09-30: disclosed
- 2026-10-14: advisory