Quick answers
- Is CVE-2026-82853 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82853 being exploited in the wild.
- How severe is CVE-2026-82853?
- Medium severity, with a CVSS score of 4.9, published 31 August 2026.
- Which products and versions are affected?
- Nodemailer up to and including 8.0.4.
- Is there a fix for CVE-2026-82853?
- A patch was published on 2026-04-08: Fix released in version 8.0.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82853 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82853?
- Check whether you run Nodemailer 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.
Technical details
The vulnerability is a CRLF injection in the SMTP connection initialization code (lib/smtp-connection/index.js). The transport name option is concatenated directly into the EHLO/HELO/LHLO SMTP commands without sanitization for \r\n sequences. When the SMTP server processes these injected newlines, each becomes a separate command; an attacker can inject MAIL FROM, RCPT TO, DATA, and email content to send fraudulent messages. The attack occurs before authentication and requires only the ability to control the name configuration parameter—for example, in multi-tenant SaaS platforms, admin panels with database-driven SMTP settings, or applications accepting external configuration. A fix is available in version 8.0.5, which strips CRLF characters from the name parameter.
Affected products
- Nodemailer Nodemailer up to and including 8.0.4
Identifiers
- CVE-2026-82853
- GHSA-vvjj-xcjg-gr5g
Timeline
- 2026-04-08: disclosed: GHSA-vvjj-xcjg-gr5g published
- 2026-04-08: patched: Fix released in version 8.0.5