CVE-2026-82662
TLS verification bypass in Nodemailer allows interception of OAuth2 tokens.
Is CVE-2026-82662 being exploited?
Not confirmed. CVE-2026-82662 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-82662?
CVE-2026-82662 is rated High with a CVSS score of 8.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82662?
Yes. A fix has been recorded for CVE-2026-82662. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82662 affect?
CVE-2026-82662 affects Nodemailer < 8.0.8, Node.js applications using Nodemailer lib/fetch, Services using OAuth2 via Nodemailer. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82662?
Upgrade to Nodemailer >=8.0.8 and rotate OAuth2 client secrets/tokens if used.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
MITM attackers can capture OAuth2 client secrets, refresh and access tokens, enabling account takeover and unauthorized email/API access.
Immediate action required
- affected< 8.0.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.