Nodemailer vulnerabilities and security advisories
The newest reviewed advisories for nodemailer on npm. Each one shows which versions are affected, which version fixes it, and a prompt that has your AI agent check your project and upgrade only if it needs to.
Get an email when Nodemailer has a new one
Email alerts are coming soon. This page updates every hour.
$ latest 27 · 7 critical, high or exploited
- mediumOct 27, 2026
Nodemailer: Quadratic backtracking in SMTP AUTH mechanism detection regexes allows pre-auth remote denial of service
- nodemailer >= 3.0.0, <= 10.0.12 · fixed in 10.0.13
GHSA-4ffr-jq9g-5ffxprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-4ffr-jq9g-5ffx, severity medium What it is: Nodemailer: Quadratic backtracking in SMTP AUTH mechanism detection regexes allows pre-auth remote denial of service Affected packages: - nodemailer: affected versions >= 3.0.0, <= 10.0.12. Fixed in 10.0.13. Details: https://github.com/advisories/GHSA-4ffr-jq9g-5ffx Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 27, 2026
Nodemailer: RFC 5322 comment inside an angle-bracket address is never stripped
- nodemailer >= 3.0.0, <= 10.0.12 · fixed in 10.0.13
GHSA-g73g-hqqh-jr95prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-g73g-hqqh-jr95, severity medium What it is: Nodemailer: RFC 5322 comment inside an angle-bracket address is never stripped Affected packages: - nodemailer: affected versions >= 3.0.0, <= 10.0.12. Fixed in 10.0.13. Details: https://github.com/advisories/GHSA-g73g-hqqh-jr95 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 27, 2026
Nodemailer: Quadratic (O(n^2)) SMTP client reply parsing lets a malicious server or MITM cause a pre-auth remote denial of service
- nodemailer >= 3.0.0, <= 10.0.9 · fixed in 10.0.10
GHSA-4g23-2xm8-66gcprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-4g23-2xm8-66gc, severity medium What it is: Nodemailer: Quadratic (O(n^2)) SMTP client reply parsing lets a malicious server or MITM cause a pre-auth remote denial of service Affected packages: - nodemailer: affected versions >= 3.0.0, <= 10.0.9. Fixed in 10.0.10. Details: https://github.com/advisories/GHSA-4g23-2xm8-66gc Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 23, 2026
Nodemailer: A nested comment ends early in addressparser, releasing the rest of the comment as a recipient
- nodemailer >= 3.0.0, < 10.1.4 · fixed in 10.1.4
GHSA-8c8m-p3m8-cjg8prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-8c8m-p3m8-cjg8, severity medium What it is: Nodemailer: A nested comment ends early in addressparser, releasing the rest of the comment as a recipient Affected packages: - nodemailer: affected versions >= 3.0.0, < 10.1.4. Fixed in 10.1.4. Details: https://github.com/advisories/GHSA-8c8m-p3m8-cjg8 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 23, 2026
Nodemailer: A ";" inside a quoted string or comment ends an address group early in addressparser, turning display text into a recipient
- nodemailer >= 3.0.0, < 10.1.4 · fixed in 10.1.4
GHSA-m943-m63m-w62wprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-m943-m63m-w62w, severity medium What it is: Nodemailer: A ";" inside a quoted string or comment ends an address group early in addressparser, turning display text into a recipient Affected packages: - nodemailer: affected versions >= 3.0.0, < 10.1.4. Fixed in 10.1.4. Details: https://github.com/advisories/GHSA-m943-m63m-w62w Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 23, 2026
Nodemailer: A ">" inside a quoted local part ends an angle-addr early in addressparser, delivering to a domain the header does not name
- nodemailer >= 3.0.0, < 10.1.4 · fixed in 10.1.4
GHSA-85x2-q946-cp5hprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-85x2-q946-cp5h, severity medium What it is: Nodemailer: A ">" inside a quoted local part ends an angle-addr early in addressparser, delivering to a domain the header does not name Affected packages: - nodemailer: affected versions >= 3.0.0, < 10.1.4. Fixed in 10.1.4. Details: https://github.com/advisories/GHSA-85x2-q946-cp5h Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 22, 2026
Nodemailer: Quadratic (O(n^2)) DKIM header unfolding lets a large folded header cause remote denial of service during signing
- nodemailer >= 3.0.0, <= 10.0.9 · fixed in 10.0.10
GHSA-39m8-27wv-hr27CVE-2026-110871prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-39m8-27wv-hr27 (CVE-2026-110871), severity medium What it is: Nodemailer: Quadratic (O(n^2)) DKIM header unfolding lets a large folded header cause remote denial of service during signing Affected packages: - nodemailer: affected versions >= 3.0.0, <= 10.0.9. Fixed in 10.0.10. Details: https://github.com/advisories/GHSA-39m8-27wv-hr27 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highSep 30, 2026
Nodemailer addressparser: O(n^2) on comment-joined addresses enables a remote DoS (reachable via mailparser)
- nodemailer >= 9.1.0, <= 10.0.4 · fixed in 10.0.5
GHSA-prgh-xp8r-p3m5CVE-2026-90776prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-prgh-xp8r-p3m5 (CVE-2026-90776), severity high What it is: Nodemailer addressparser: O(n^2) on comment-joined addresses enables a remote DoS (reachable via mailparser) Affected packages: - nodemailer: affected versions >= 9.1.0, <= 10.0.4. Fixed in 10.0.5. Details: https://github.com/advisories/GHSA-prgh-xp8r-p3m5 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 29, 2026
Nodemailer: Quoted local-part can produce malformed envelope recipient through RFC 5322 comment parsing
- nodemailer >= 9.1.0, < 10.0.9 · fixed in 10.0.9
GHSA-g57g-f23g-4646prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-g57g-f23g-4646, severity medium What it is: Nodemailer: Quoted local-part can produce malformed envelope recipient through RFC 5322 comment parsing Affected packages: - nodemailer: affected versions >= 9.1.0, < 10.0.9. Fixed in 10.0.9. Details: https://github.com/advisories/GHSA-g57g-f23g-4646 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highSep 29, 2026
Nodemailer: Quadratic backtracking in the addressparser free-text fallback allows remote denial of service
- nodemailer <= 10.0.5 · fixed in 10.0.6
GHSA-v53p-9fqp-m79jprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-v53p-9fqp-m79j, severity high What it is: Nodemailer: Quadratic backtracking in the addressparser free-text fallback allows remote denial of service Affected packages: - nodemailer: affected versions <= 10.0.5. Fixed in 10.0.6. Details: https://github.com/advisories/GHSA-v53p-9fqp-m79j Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 29, 2026
Nodemailer: Nested structured recipient arrays bypass the parser depth limit and cause stack exhaustion DoS
- nodemailer < 10.0.2 · fixed in 10.0.2
GHSA-8vvx-rff5-p5rqprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-8vvx-rff5-p5rq, severity medium What it is: Nodemailer: Nested structured recipient arrays bypass the parser depth limit and cause stack exhaustion DoS Affected packages: - nodemailer: affected versions < 10.0.2. Fixed in 10.0.2. Details: https://github.com/advisories/GHSA-8vvx-rff5-p5rq Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 28, 2026
Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure
- nodemailer >= 5.0.0, < 10.0.2 · fixed in 10.0.2
GHSA-6vj9-mwq6-2f5vprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-6vj9-mwq6-2f5v, severity medium What it is: Nodemailer: Process-global DNS cache reuses TLS `servername` across transports, enabling cross-tenant SMTP credential disclosure Affected packages: - nodemailer: affected versions >= 5.0.0, < 10.0.2. Fixed in 10.0.2. Details: https://github.com/advisories/GHSA-6vj9-mwq6-2f5v Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 8, 2026
Nodemailer: IDN/Punycode domain allow-list bypass leads to email delivery to an attacker-controlled domain
- nodemailer < 9.1.0 · fixed in 9.1.0
GHSA-wmmp-3585-3rmpprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-wmmp-3585-3rmp, severity medium What it is: Nodemailer: IDN/Punycode domain allow-list bypass leads to email delivery to an attacker-controlled domain Affected packages: - nodemailer: affected versions < 9.1.0. Fixed in 9.1.0. Details: https://github.com/advisories/GHSA-wmmp-3585-3rmp Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highSep 8, 2026
Nodemailer: Quadratic (O(n²)) time complexity in addressparser allows remote denial of service via a crafted address list
- nodemailer < 9.1.0 · fixed in 9.1.0
GHSA-2x7j-588g-ccc2prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-2x7j-588g-ccc2, severity high What it is: Nodemailer: Quadratic (O(n²)) time complexity in addressparser allows remote denial of service via a crafted address list Affected packages: - nodemailer: affected versions < 9.1.0. Fixed in 9.1.0. Details: https://github.com/advisories/GHSA-2x7j-588g-ccc2 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 8, 2026
Nodemailer: Recipient-domain validation bypass via RFC 5322 comment mis-parsing leads to email delivery to an attacker-controlled domain
- nodemailer >= 6.9.16, < 9.1.0 · fixed in 9.1.0
GHSA-cc9r-2j5m-2m83prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-cc9r-2j5m-2m83, severity medium What it is: Nodemailer: Recipient-domain validation bypass via RFC 5322 comment mis-parsing leads to email delivery to an attacker-controlled domain Affected packages: - nodemailer: affected versions >= 6.9.16, < 9.1.0. Fixed in 9.1.0. Details: https://github.com/advisories/GHSA-cc9r-2j5m-2m83 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumSep 8, 2026
Nodemailer: resolveContent() on a MailMessage bypasses disableFileAccess/disableUrlAccess when called with the legacy signature
- nodemailer <= 9.1.0 · fixed in 9.1.1
GHSA-8m3c-c648-2xjjprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-8m3c-c648-2xjj, severity medium What it is: Nodemailer: resolveContent() on a MailMessage bypasses disableFileAccess/disableUrlAccess when called with the legacy signature Affected packages: - nodemailer: affected versions <= 9.1.0. Fixed in 9.1.1. Details: https://github.com/advisories/GHSA-8m3c-c648-2xjj Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highJun 18, 2026
Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message
- nodemailer <= 9.0.0 · fixed in 9.0.1
GHSA-p6gq-j5cr-w38fCVE-2026-82659prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-p6gq-j5cr-w38f (CVE-2026-82659), severity high What it is: Nodemailer: Message-level raw option bypasses disableFileAccess/disableUrlAccess, enabling arbitrary file read and full-response SSRF in the delivered message Affected packages: - nodemailer: affected versions <= 9.0.0. Fixed in 9.0.1. Details: https://github.com/advisories/GHSA-p6gq-j5cr-w38f Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumJun 15, 2026
Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injection
- nodemailer <= 8.0.8 · fixed in 8.0.9
GHSA-268h-hp4c-crq3prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-268h-hp4c-crq3, severity medium What it is: Nodemailer: CRLF injection in Nodemailer List-* header comments allows arbitrary message header injection Affected packages: - nodemailer: affected versions <= 8.0.8. Fixed in 8.0.9. Details: https://github.com/advisories/GHSA-268h-hp4c-crq3 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumJun 15, 2026
Nodemailer jsonTransport bypasses disableFileAccess and disableUrlAccess during message normalization
- nodemailer <= 8.0.8 · fixed in 8.0.9
GHSA-wqvq-jvpq-h66fprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-wqvq-jvpq-h66f, severity medium What it is: Nodemailer jsonTransport bypasses disableFileAccess and disableUrlAccess during message normalization Affected packages: - nodemailer: affected versions <= 8.0.8. Fixed in 8.0.9. Details: https://github.com/advisories/GHSA-wqvq-jvpq-h66f Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highJun 15, 2026
Nodemailer: Improper TLS Certificate Validation in OAuth2 Token Fetch Enables Credential Interception
- nodemailer <= 8.0.7 · fixed in 8.0.8
GHSA-r7g4-qg5f-qqm2CVE-2026-82662prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-r7g4-qg5f-qqm2 (CVE-2026-82662), severity high What it is: Nodemailer: Improper TLS Certificate Validation in OAuth2 Token Fetch Enables Credential Interception Affected packages: - nodemailer: affected versions <= 8.0.7. Fixed in 8.0.8. Details: https://github.com/advisories/GHSA-r7g4-qg5f-qqm2 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumApr 8, 2026
Nodemailer Vulnerable to SMTP Command Injection via CRLF in Transport name Option (EHLO/HELO)
- nodemailer <= 8.0.4 · fixed in 8.0.5
GHSA-vvjj-xcjg-gr5gprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-vvjj-xcjg-gr5g, severity medium What it is: Nodemailer Vulnerable to SMTP Command Injection via CRLF in Transport name Option (EHLO/HELO) Affected packages: - nodemailer: affected versions <= 8.0.4. Fixed in 8.0.5. Details: https://github.com/advisories/GHSA-vvjj-xcjg-gr5g Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - lowMar 26, 2026
Nodemailer has SMTP command injection due to unsanitized `envelope.size` parameter
- nodemailer < 8.0.4 · fixed in 8.0.4
GHSA-c7w3-x93f-qmm8prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-c7w3-x93f-qmm8, severity low What it is: Nodemailer has SMTP command injection due to unsanitized `envelope.size` parameter Affected packages: - nodemailer: affected versions < 8.0.4. Fixed in 8.0.4. Details: https://github.com/advisories/GHSA-c7w3-x93f-qmm8 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - highDec 1, 2025
Nodemailer’s addressparser is vulnerable to DoS caused by recursive calls
- nodemailer >= 3.0.0, <= 7.0.10 · fixed in 7.0.11
GHSA-rcmh-qjqh-p98vCVE-2025-14874prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-rcmh-qjqh-p98v (CVE-2025-14874), severity high What it is: Nodemailer’s addressparser is vulnerable to DoS caused by recursive calls Affected packages: - nodemailer: affected versions >= 3.0.0, <= 7.0.10. Fixed in 7.0.11. Details: https://github.com/advisories/GHSA-rcmh-qjqh-p98v Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumOct 7, 2025
Nodemailer: Email to an unintended domain can occur due to Interpretation Conflict
- nodemailer < 7.0.7 · fixed in 7.0.7
GHSA-mm7p-fcc7-pg87CVE-2025-13033prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-mm7p-fcc7-pg87 (CVE-2025-13033), severity medium What it is: Nodemailer: Email to an unintended domain can occur due to Interpretation Conflict Affected packages: - nodemailer: affected versions < 7.0.7. Fixed in 7.0.7. Details: https://github.com/advisories/GHSA-mm7p-fcc7-pg87 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumJan 31, 2024
nodemailer ReDoS when trying to send a specially crafted email
- nodemailer <= 6.9.8 · fixed in 6.9.9
GHSA-9h6g-pr28-7cqpprompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-9h6g-pr28-7cqp, severity medium What it is: nodemailer ReDoS when trying to send a specially crafted email Affected packages: - nodemailer: affected versions <= 6.9.8. Fixed in 6.9.9. Details: https://github.com/advisories/GHSA-9h6g-pr28-7cqp Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - mediumDec 10, 2021
Header injection in nodemailer
- nodemailer < 6.6.1 · fixed in 6.6.1
GHSA-hwqf-gcqm-7353CVE-2021-23400prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-hwqf-gcqm-7353 (CVE-2021-23400), severity medium What it is: Header injection in nodemailer Affected packages: - nodemailer: affected versions < 6.6.1. Fixed in 6.6.1. Details: https://github.com/advisories/GHSA-hwqf-gcqm-7353 Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now. - criticalMay 10, 2021
Command injection in nodemailer
- nodemailer < 6.4.16 · fixed in 6.4.16
GHSA-48ww-j4fc-435pCVE-2020-7769prompt for your AI agent
paste into your agentA security advisory covers a package this project may use. Advisory: GHSA-48ww-j4fc-435p (CVE-2020-7769), severity critical What it is: Command injection in nodemailer Affected packages: - nodemailer: affected versions < 6.4.16. Fixed in 6.4.16. Details: https://github.com/advisories/GHSA-48ww-j4fc-435p Please: 1. Check package.json and the lockfile (package-lock.json, pnpm-lock.yaml, yarn.lock or bun.lock) for these packages, including copies pulled in by other dependencies, and tell me which versions are installed. 2. If none of them are installed, or every installed version is outside the affected ranges, say so and change nothing. 3. If an installed version is affected, upgrade it to the fixed version for its release line or later. When the package only comes in through another dependency, upgrade that dependency, or add an override or resolution if it has no fixed release yet. 4. If there is no fixed version, read the advisory and apply its workaround, or tell me the options. 5. Reinstall, run the build and the tests, and fix anything the upgrade breaks. 6. Tell me what you changed and which versions are installed now.
From the GitHub Advisory Database, refreshed hourly. Full history on GitHub.
Keeping Nodemailer patched
npm audit(orpnpm audit) lists known vulnerable packages in your lockfile, including ones pulled in by other packages.- Turn on Dependabot for your GitHub repo and it opens the upgrade for you when an advisory lands.
- A patched framework doesn't cover your own setup: headers, cookies and HTTPS. The free check looks at those.