Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injection

CVE-2026-82661GHSA-268h-hp4c-crq3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (nodemailer 8.0.9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2026-82661: 0.26% estimated exploitation activity in the next 30 days; percentile 17.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Nodemailer constructs List- headers from the caller-provided list message option using internally prepared header values. The list..comment field is inserted into those prepared values without removing CR (\r) or LF (\n) characters. Because prepared headers bypass the normal header-value sanitizer and are passed to mimeFuncs.foldLines(), a CRLF sequence in a list comment is emitted as an actual header boundary in the generated RFC822 message. An application that lets a lower-privileged or unauthenticated user influence list.help.comment, list.unsubscribe.comment, list.subscribe.comment, list.post.comment, list.owner.comment, list.archive.comment, or list.id.comment can therefore be made to generate messages containing attacker-chosen additional headers. Details Source-to-sink evidence: - lib/mailer/mail-message.js:241-249 calls getListHeaders(this.data.list) and adds each returned value with this.message.addHeader(listHeader.key, value). - lib/mailer/mail-message.js:253-296…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-268h-hp4c-crq3

  2. Revision 1 · created ·

    Published from osv record GHSA-268h-hp4c-crq3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-82661

Advisory: Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injection
IDs: CVE-2026-82661, GHSA-268h-hp4c-crq3
Record: https://patchnext.com/advisories/cve-2026-82661 (revision 2, source checked 26 Oct 2026, 12:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: nodemailer 8.0.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm nodemailer: affected <= 8.0.8; fixed in 8.0.9

## Suggested inspection (read-only)
- `npm ls nodemailer --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on nodemailer.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-268h-hp4c-crq3 (OSV record GHSA-268h-hp4c-crq3 lists affected ranges: npm nodemailer >=0 <8.0.9 (fixed))
- Verified: https://github.com/advisories/GHSA-268h-hp4c-crq3 (GitHub-reviewed advisory GHSA-268h-hp4c-crq3 lists affected ranges: npm nodemailer >=0 <=8.0.8)

Commands are suggestions: review each one before running it.

Loading voting…