nodemailer

10.2.1 · 22 Oct 2026MIT-023.7M / weekRepository Homepage npm Atom feed

Same major only

11 releases in betweennotes for 4

Other targets from 2.4.0Clears its 15 advisories10.0.6 Latest10.2.1

?
changes to make: 0
advisories fixed: 1+
new: 2+
fixes

Counted from 4 of 11 release notes. Advisories are counted from the advisory database, in full.

Security

15 advisories still affect 2.7.2

Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injectionmoderate · GHSA-268h-hp4c-crq3
Command injection in nodemailercritical · GHSA-48ww-j4fc-435p
Nodemailer: resolveContent() on a MailMessage bypasses disableFileAccess/disableUrlAccess when called with the legacy signaturemoderate · GHSA-8m3c-c648-2xjj

Upgrading to 10.0.6 clears them.

Release by release

2.6.1 – 2.7.27 releases, nothing new or fixed; 6 without a note
2.6.0
5 Sep 20161 new · 1 fix
- new
  Added new options disableFileAccess and disableUrlAccess
- fixed
  Fixed envelope handling where cc/bcc fields were ignored in the envelope object
2.4.2 – 2.5.02 releases, nothing new or fixed; 1 without a note
2.4.1
12 May 20161 fix
- fixed
  Fixed outdated shrinkwrap file

2 other lines we could not sort, mostly version bumps

Bumped mailcomposer that generates encoded-words differently which might break some tests
2.7.0
Removed shrinkwrap file. Seemed to cause more trouble than help
2.4.2

Upgrade to 2.7.2

npm install nodemailer@2.7.2

What 2.7.2 needs

Reading 2.7.2's manifest…

Check against your package.json

Which of your other dependencies stand in the way of 2.7.2. Read once, not stored.

After upgrading

Run the type checker, the linter and the tests.
Build, and look for new deprecation warnings.
Update peer dependencies the new version asks for.
15 advisories still affect 2.7.2.