Advisory record · GHSA-r7g4-qg5f-qqm2

Nodemailer: Improper TLS Certificate Validation in OAuth2 Token Fetch Enables Credential Interception

CVSS 8.3 HighEPSS 0.0019 · 8th percentile

Published by the GitHub Advisory Database at 15 Jun 2026, 17:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
nodemailernpm<8.0.88.0.8
Identifiers
GHSA-r7g4-qg5f-qqm2 · CVE-2026-82662
Weakness (CWE)
CWE-295
Published
15 Jun 2026
Updated
5 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nodemailer versions before 8.0.8 disable TLS certificate verification in their internal HTTPS fetch client used for OAuth2 token requests, so those requests accept invalid or self-signed certificates. An attacker in a man-in-the-middle position between the application and the OAuth endpoint could intercept OAuth2 credentials such as the client secret, refresh token, and access tokens, and could then access mail or send mail. Upgrade to Nodemailer 8.0.8, which is the fixed version listed.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.3 High 4.0 CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N CNA (VulnCheck)
  • CISA KEV Not listed.
  • EPSS 0.0019, the 8th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 13:34 UTC First seen by agentprime
  2. 31 Oct 2026, 13:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.