CVE-2026-100702

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreHIGH confidence

Score 5.9 from GitHub Security Advisory (severity: HIGH) published 2026-09-26. A secondary CVSS source baseline 5.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Nodemailer before 10.0.2 fails to properly flatten deeply nested arrays in recipient fields such as to, cc, and bcc, allowing attackers to cause stack exhaustion. Attackers can supply a deeply nested JSON recipient array that triggers recursive Array.toString() conversion, exhausting the call stack and terminating the Node.js process.

CVSS v3
5.9
EG Score
5.9MEDIUMhigh confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
14th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

Nodemailer before 10.0.2 Stack Exhaustion via Nested Recipient Arrays | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nodemailer-before-10.0.2-stack-exhaustion-via-nested-recipient-arrays
github Patch Available🟡 PoC Available

Nested structured recipient arrays bypass the parser depth limit and cause stack exhaustion DoS · Advisory · nodemailer/nodemailer · GitHub

https://github.com/nodemailer/nodemailer/security/advisories/GHSA-8vvx-rff5-p5rq

Vendor Advisories for CVE-2026-100702(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-nodemailer10.0.0+~8.0.1-1 ... 9.0.6+~8.0.1-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-nodemailer10.0.0+~8.0.1-1 ... 9.0.6+~8.0.1-1 (20 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-nodemailer10.0.0+~8.0.1-1 ... 9.0.6+~8.0.1-1 (17 versions)
  • every version up to 10.0.10+~8.0.1-1: fixed in 10.0.10+~8.0.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
nodemailer—
  • every version up to 10.0.2: fixed in 10.0.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 18× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:21 UTCEPSS rescore
  2. 2026-10-04 18:09 UTCGHSA enrichment
  3. 2026-10-03 17:48 UTCEG score recompute
  4. 2026-10-03 17:48 UTCGHSA enrichment
  5. 2026-10-03 14:25 UTCEPSS rescore
  6. 2026-10-02 17:27 UTCEG score recompute
  7. 2026-10-02 17:27 UTCGHSA enrichment
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 17:04 UTCGHSA enrichment
  10. 2026-09-30 16:43 UTCEG score recompute
  11. 2026-09-30 16:43 UTCGHSA enrichment
  12. 2026-09-30 15:02 UTCEPSS rescore
  13. 2026-09-30 01:29 UTCEG score recompute
  14. 2026-09-30 01:29 UTCGHSA enrichment
  15. 2026-09-29 15:20 UTCEPSS rescore
  16. 2026-09-29 01:08 UTCEG score recompute
  17. 2026-09-29 01:08 UTCGHSA enrichment
  18. 2026-09-28 13:50 UTCEPSS rescore
  19. 2026-09-28 00:45 UTCEG score recompute
  20. 2026-09-28 00:45 UTCGHSA enrichment
  21. 2026-09-27 00:23 UTCEG score recompute
  22. 2026-09-27 00:23 UTCGHSA enrichment
  23. 2026-09-26 23:27 UTCEG score recompute
  24. 2026-09-26 23:27 UTCGHSA enrichment
  25. 2026-09-26 14:29 UTCEG score recompute
Show 2 more
  1. 2026-09-26 13:34 UTCEG score recompute
  2. 2026-09-26 13:30 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-100702?
CVE-2026-100702 is a medium vulnerability published on September 26, 2026. Nodemailer before 10.0.2 fails to properly flatten deeply nested arrays in recipient fields such as to, cc, and bcc, allowing attackers to cause stack exhaustion. Attackers can supply a deeply nested JSON recipient array that triggers recursive Array.toString() conversion, exhausting the call stack…
When was CVE-2026-100702 disclosed?
CVE-2026-100702 was first published on September 26, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100702 actively exploited?
CVE-2026-100702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100702?
CVE-2026-100702 has a CVSS base score of 5.9 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100702?
A fix for CVE-2026-100702 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100702 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-100702

Explore →

Is Your Infrastructure Affected by CVE-2026-100702?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs