Quick answers
- Is CVE-2026-82662 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82662 being exploited in the wild.
- How severe is CVE-2026-82662?
- Medium severity, with a CVSS score of 6.5, published 31 August 2026.
- Which products and versions are affected?
- Nodemailer <= 8.0.7.
- Is there a fix for CVE-2026-82662?
- A patch was published on 2026-05-26: Fixed in version 8.0.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82662 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82662?
- Check whether you run Nodemailer at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in lib/fetch/index.js where Nodemailer sets rejectUnauthorized: false in its internal HTTPS client, disabling TLS peer certificate verification globally. This allows self-signed and invalid certificates to be accepted, hostname validation to be bypassed, and attacker-controlled HTTPS endpoints to be trusted. An attacker in a man-in-the-middle position can intercept OAuth2 token requests to capture OAuth client_secret, refresh_token, and access tokens. The vulnerability affects versions <= 8.0.7 and is patched in version 8.0.8. Attack vector is network with high attack complexity (requires MITM positioning).
Affected products
- Nodemailer Nodemailer <= 8.0.7
Identifiers
- CVE-2026-82662
- GHSA-r7g4-qg5f-qqm2
Timeline
- 2026-05-26: disclosed
- 2026-05-26: patched: Fixed in version 8.0.8