Nodemailer before 8.0.9 fails to sanitize carriage return and line feed characters in list comment fields, allowing attackers to inject arbitrary message headers. An attacker with control over list.*.comment parameters can inject CRLF sequences to create additional headers in generated RFC822 messages, altering mail client behavior and message semantics.
CVE-2026-82661
Score 5.4 from GitHub Security Advisory published 2026-08-31. a secondary CVSS source baseline 5.4; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 9%
- KEV
- Not listed
Published
August 31, 2026
Last Modified
September 10, 2026
Advisory Details (2)
Auto-updated Aug 31, 2026Nodemailer CRLF Injection via List-* Header Comments | Advisories | VulnCheck
https://www.vulncheck.com/advisories/nodemailer-crlf-injection-via-list-header-commentsCRLF injection in Nodemailer List-* header comments allows arbitrary message header injection · Advisory · nodemailer/nodemailer · GitHub
https://github.com/nodemailer/nodemailer/security/advisories/GHSA-268h-hp4c-crq3Vendor Advisories for CVE-2026-82661(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(4 across 4 ecosystems)
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-nodemailer | 6.10.0+~6.4.17-1 ... 9.0.6+~8.0.1-1 (24 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-nodemailer | 6.10.0+~6.4.17-1 ... 9.0.6+~8.0.1-1 (17 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| node-nodemailer | 6.10.0+~6.4.17-1 ... 8.0.4+~7.0.11-2 (11 versions) | 8.0.11+~8.0.1-1 | — |
npm(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nodemailer | — | 8.0.9 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 21× in last 7d / 60× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-19 02:47 UTCEG score recompute
- 2026-09-19 02:47 UTCGHSA enrichment
- 2026-09-18 19:28 UTCEPSS rescore
- 2026-09-18 04:16 UTCEG score recompute
- 2026-09-18 04:16 UTCGHSA enrichment
- 2026-09-17 05:45 UTCEG score recompute
- 2026-09-17 05:44 UTCGHSA enrichment
- 2026-09-16 14:08 UTCEPSS rescore
- 2026-09-16 07:09 UTCEG score recompute
- 2026-09-16 07:09 UTCGHSA enrichment
- 2026-09-16 05:15 UTCEPSS rescore
- 2026-09-15 08:38 UTCEG score recompute
- 2026-09-15 08:38 UTCGHSA enrichment
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-15 03:12 UTCEPSS rescore
- 2026-09-14 10:07 UTCEG score recompute
- 2026-09-14 10:07 UTCGHSA enrichment
- 2026-09-13 11:36 UTCEG score recompute
- 2026-09-13 11:36 UTCGHSA enrichment
- 2026-09-12 13:05 UTCEG score recompute
- 2026-09-12 13:05 UTCGHSA enrichment
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:53 UTCEPSS rescore
- 2026-09-11 14:33 UTCEG score recompute
- 2026-09-11 14:33 UTCGHSA enrichment
Show 35 moreShow fewer
- 2026-09-10 16:02 UTCEG score recompute
- 2026-09-10 16:02 UTCGHSA enrichment
- 2026-09-10 07:08 UTCGHSA enrichment
- 2026-09-09 08:37 UTCEG score recompute
- 2026-09-09 08:37 UTCGHSA enrichment
- 2026-09-08 22:01 UTCEPSS rescore
- 2026-09-08 10:06 UTCEG score recompute
- 2026-09-08 10:05 UTCGHSA enrichment
- 2026-09-07 11:23 UTCEG score recompute
- 2026-09-07 11:23 UTCGHSA enrichment
- 2026-09-06 13:48 UTCEPSS rescore
- 2026-09-06 12:46 UTCEG score recompute
- 2026-09-06 12:46 UTCGHSA enrichment
- 2026-09-05 15:31 UTCEPSS rescore
- 2026-09-05 14:14 UTCGHSA enrichment
- 2026-09-04 15:43 UTCEG score recompute
- 2026-09-04 15:43 UTCGHSA enrichment
- 2026-09-04 05:07 UTCEPSS rescore
- 2026-09-03 17:10 UTCGHSA enrichment
- 2026-09-02 18:38 UTCEG score recompute
- 2026-09-02 18:37 UTCGHSA enrichment
- 2026-09-02 18:06 UTCEG score recompute
- 2026-09-02 18:06 UTCGHSA enrichment
- 2026-09-02 14:12 UTCEPSS rescore
- 2026-09-02 06:45 UTCEG score recompute
- 2026-09-02 06:45 UTCGHSA enrichment
- 2026-09-01 13:54 UTCEPSS rescore
- 2026-09-01 08:13 UTCEG score recompute
- 2026-09-01 08:12 UTCGHSA enrichment
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-09-01 04:40 UTCEPSS rescore
- 2026-08-31 09:37 UTCEG score recompute
- 2026-08-31 09:37 UTCGHSA enrichment
- 2026-08-31 08:55 UTCEG score recompute
- 2026-08-31 08:52 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-82661?
When was CVE-2026-82661 disclosed?
Is CVE-2026-82661 actively exploited?
What is the CVSS score of CVE-2026-82661?
How do I remediate CVE-2026-82661?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82661
Is Your Infrastructure Affected by CVE-2026-82661?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.