CVE-2026-82853

Nodemailer before 8.0.5 SMTP Command Injection via CRLF

Published Aug 31, 2026 CVSS 4.0 · 6.9 Medium EPSS 1.0% KEV · Not listed
Description
Nodemailer versions before 8.0.5 contain an SMTP command injection vulnerability in the transport name option used in EHLO/HELO commands. The name parameter is concatenated directly into SMTP commands without sanitizing carriage return and line feed characters, allowing attackers to inject arbitrary SMTP commands for email spoofing and phishing attacks.

Analysis

AI-generated

Technical impact

The vulnerability is a classic SMTP command injection where an attacker can insert carriage return and line feed characters into the HELO/EHLO name parameter. When the name is concatenated directly into the SMTP command, an attacker can append additional SMTP commands, enabling manipulation of email headers and potentially forging sender addresses. This increases the risk of phishing campaigns that appear to originate from trusted domains, undermining the integrity and authenticity of email communications. The weakness is classified as CWE-93, which indicates a lack of sanitization for input that is sent to a command processor.

Affected Systems

Any application using Nodemailer versions earlier than 8.0.5 is affected. The library must be replaced or updated to the version 8.0.5 or later; no other environments or components are listed as impacted beyond the Nodemailer package itself.

Risk and Exploitability

The CVSS score of 6.9 indicates a medium severity, reflecting the potential for widespread phishing. The EPSS score is not available, so exact exploitation frequency is unknown. The vulnerability is not yet in the CISA KEV catalog, indicating that there are no confirmed large‑scale attacks, but the attack vector is inferred to be the network, as malicious SMTP commands can be sent during a normal SMTP session. An attacker would need network access to the target SMTP server or to an application that uses Nodemailer to send mail on their behalf. Successful exploitation would grant the attacker the ability to send emails that appear to come from their chosen address, thereby compromising the integrity and authenticity of the mail system.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Nodemailer to 8.0.5 or later to remove the injection flaw.
  • If an upgrade cannot be performed immediately, restrict or validate the HELO/EHLO name parameter to reject any CRLF characters before it is sent to the SMTP server.
  • Deploy outbound email filtering rules that flag or block messages with forged sender addresses or suspicious header patterns as a mitigating posture against possible spoof attempts.

Generated by OpenCVE AI on August 31, 2026 at 10:52 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Nodemailer versions before 8.0.5 contain an SMTP command injection vulnerability in the transport name option used in EHLO/HELO commands. The name parameter is concatenated directly into SMTP commands without sanitizing carriage return and line feed characters, allowing attackers to inject arbitrary SMTP commands for email spoofing and phishing attacks.
Title Nodemailer before 8.0.5 SMTP Command Injection via CRLF
First Time appeared Nodemailer
Nodemailer nodemailer
Weaknesses CWE-93
CPEs cpe:2.3:a:nodemailer:nodemailer:*:*:*:*:*:*:*:*
Vendors & Products Nodemailer
Nodemailer nodemailer
References
Metrics cvssV3_1

{'score': 4.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N'}

cvssV4_0

{'score': 6.9, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-93

    Improper Neutralization of CRLF Sequences ('CRLF Injection')

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Aug 31, 2026, 11:00 AM
Reserved
Aug 31, 2026, 8:37 AM
Status
Awaiting Analysis
Published
Aug 31, 2026, 9:17 AM
Modified
Sep 10, 2026, 3:48 PM
Severity
Moderate
Public date
Aug 31, 2026, 8:46 AM