Nodemailer before 8.0.4 SMTP Command Injection via envelope.size
Impact
Nodemailer before 8.0.4 is vulnerable to SMTP command injection via the envelope.size parameter, allowing injection of arbitrary SMTP commands if an application exposes the envelope size to attacker-controlled input. The weakness is due to improper neutralization of CRLF sequences. Exploitation requires attacker-controlled input.
Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.Exploitation requires the application to expose the envelope size to attacker-controlled input, as Nodemailer does not include size in the default auto-constructed envelope.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
nodemailer · VulnCheck
nodemailer
2 ranges
nodemailer · VulnCheck
nodemailer
Package identity
pkg:npm/nodemailerExplore nodemailer →Identity supplied by VulnCheck. Version matching requires compatible range evidence.
Compare with this publisher’s ranges. This does not inspect your installation.
affected
0 → before 8.0.4
semver versions
unaffected
8.0.4
semver versions
Other versions: unaffected
Original source description
Nodemailer before 8.0.4 is vulnerable to SMTP command injection through the unsanitized envelope.size parameter. When an application passes a custom envelope object with a size property containing CRLF characters to sendMail(), the value is concatenated into the SMTP MAIL FROM command (as SIZE=...) without sanitization, allowing injection of arbitrary SMTP commands such as RCPT TO to silently add attacker-controlled recipients. Exploitation requires the application to expose the envelope size to attacker-controlled input, as Nodemailer does not include size in the default auto-constructed envelope.
Inside the record
Evidence available
Describes the evidence in this view, not whether the product is safe.
Original records
CVE-2026-82854View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.
cve.new JSON →Underlying weaknesses
The source’s classification of what caused the vulnerability.
Environment requirements
These conditions apply together as specified by the publisher. A matching product name alone does not establish exposure.
VulnCheck · platform conditions
Any condition may hold
Vulnerable product
cpe:2.3:a:nodemailer:nodemailer:*:*:*:*:*:*:*:*Before: 8.0.4
Original applicability statements
[
{
"nodes": [
{
"operator": "OR",
"negate": false,
"cpeMatch": [
{
"vulnerable": true,
"criteria": "cpe:2.3:a:nodemailer:nodemailer:*:*:*:*:*:*:*:*",
"versionEndExcluding": "8.0.4"
}
]
}
]
}
]Contributing organizations · 2
Assigning organization
Additional data publisher
What changed
Follow changesLarge field values are marked as truncated previews. Original source snapshots remain retained.