Skip to main content
EPSS 0.3%top 83%

Nodemailer before 8.0.9 fails to sanitize carriage return and line feed characters in list comment fields, allowing attackers to inject arbitrary… (CVE-2026-82661)

0
Medium
Published: 08/31/2026 (08/31/2026, 09:30:29 UTC)
Source: GCVE Database

Description

Nodemailer versions before 8.0.9 do not properly sanitize carriage return and line feed characters in list comment fields. This vulnerability allows attackers who can control list.*.comment parameters to inject arbitrary message headers by inserting CRLF sequences. Such header injection can alter mail client behavior and message semantics.

CVSS v3.1

Score 5.4medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected software

Affected versions
<8.0.9

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 09/09/2026, 11:23:11 UTC

Technical Analysis

The vulnerability in Nodemailer prior to version 8.0.9 involves improper sanitization of carriage return (CR) and line feed (LF) characters in list comment fields. An attacker with control over these parameters can inject CRLF sequences, enabling the creation of additional headers in generated RFC822 email messages. This can lead to altered mail client behavior and changes in message semantics, potentially impacting the integrity of email communications.

Potential Impact

The vulnerability allows an attacker with limited privileges (PR:L) and no user interaction (UI:N) to inject arbitrary headers into email messages generated by Nodemailer. This can lead to altered message semantics and mail client behavior, potentially causing confusion or misinterpretation of emails. The confidentiality and integrity impacts are low, and there is no impact on availability.

Mitigation Recommendations

A fix is available in Nodemailer version 8.0.9 that properly sanitizes carriage return and line feed characters in list comment fields. Users should upgrade to version 8.0.9 or later to remediate this vulnerability. Patch status is not explicitly confirmed in the provided data, but the version boundary indicates the fix is in 8.0.9. No vendor advisory content was provided to contradict this.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
GHSA-2jv2-wqrj-g6x7
Osv Schema Version
1.4.0
Aliases
["CVE-2026-82661"]
Database Specific Severity
MODERATE
Cvss Version
3.1

Threat ID: 6a95a0f4acd9273b4947e2a3

Added to database: 08/31/2026, 15:42:44 UTC

Last enriched: 09/09/2026, 11:23:11 UTC

Last updated: 10/14/2026, 06:48:21 UTC

Views: 25

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses