CVE-2026-100700

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-87673 (ENISA EUVD) · GHSA-c7vw-frhj-6h9j (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

nodemailer before 10.0.6 contains a denial of service vulnerability in the addressparser free-text fallback regex pattern that exhibits quadratic backtracking behavior. Attackers can supply crafted email header values with long whitespace-free runs to block the Node.js event loop for tens of seconds, causing service unavailability.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
27th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-09). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 26, 2026

Last Modified

September 30, 2026

Advisory Details (2)

Auto-updated Sep 26, 2026
Patch available. Sources: github.
Web page

nodemailer before 10.0.6 Denial of Service via addressparser | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nodemailer-before-10.0.6-denial-of-service-via-addressparser
GitHub advisoryMentions a patch (unverified)

Quadratic backtracking in the addressparser free-text fallback allows remote denial of service · Advisory · nodemailer/nodemailer · GitHub

https://github.com/nodemailer/nodemailer/security/advisories/GHSA-v53p-9fqp-m79j

Vendor Advisories for CVE-2026-100700(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.6: fixed in 10.0.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 35× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 115 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  2. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  3. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  4. 2026-11-10 07:18 UTCEchelonGraph re-scored
  5. 2026-11-10 07:18 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-11-07 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-03 16:45 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-11-02 23:20 UTCEchelonGraph re-scored
  14. 2026-11-02 23:20 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  15. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  18. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  19. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  20. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-10-26 15:32 UTCEchelonGraph re-scored
  24. 2026-10-26 15:32 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 75 more
  1. 2026-10-25 15:58 UTCEchelonGraph re-scored
  2. 2026-10-25 03:58 UTCEchelonGraph re-scored
  3. 2026-10-25 03:58 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  5. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  6. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  7. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  8. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  9. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  10. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-10-18 05:11 UTCEchelonGraph re-scored
  12. 2026-10-17 20:11 UTCEchelonGraph re-scored
  13. 2026-10-17 20:10 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  16. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  19. 2026-10-12 16:41 UTCEchelonGraph re-scored
  20. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-10-11 20:16 UTCEchelonGraph re-scored
  22. 2026-10-11 19:08 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  23. 2026-10-11 18:29 UTCEchelonGraph re-scored
  24. 2026-10-11 15:02 UTCEchelonGraph re-scored
  25. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  26. 2026-10-11 07:34 UTCEchelonGraph re-scored
  27. 2026-10-11 07:34 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  28. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  29. 2026-10-10 19:53 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  30. 2026-10-10 08:11 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  31. 2026-10-09 20:37 UTCEchelonGraph re-scored
  32. 2026-10-09 20:37 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  33. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  34. 2026-10-09 09:03 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  35. 2026-10-08 21:29 UTCEchelonGraph re-scored
  36. 2026-10-08 21:28 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  37. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  38. 2026-10-08 09:53 UTCEchelonGraph re-scored
  39. 2026-10-08 09:53 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  40. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  41. 2026-10-07 22:19 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  42. 2026-10-07 10:45 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  43. 2026-10-06 23:10 UTCEchelonGraph re-scored
  44. 2026-10-06 23:10 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  45. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  46. 2026-10-06 11:36 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  47. 2026-10-06 00:02 UTCEchelonGraph re-scored
  48. 2026-10-06 00:01 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  49. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  50. 2026-10-05 12:28 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  51. 2026-10-05 00:53 UTCEchelonGraph re-scored
  52. 2026-10-05 00:53 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  53. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  54. 2026-10-04 13:17 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  55. 2026-10-04 01:43 UTCEchelonGraph re-scored
  56. 2026-10-04 01:43 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  57. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  58. 2026-10-03 14:09 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  59. 2026-10-03 02:35 UTCEchelonGraph re-scored
  60. 2026-10-03 02:35 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  61. 2026-10-02 15:00 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  62. 2026-10-02 03:26 UTCEchelonGraph re-scored
  63. 2026-10-02 03:26 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  64. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  65. 2026-10-01 15:52 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  66. 2026-10-01 04:18 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  67. 2026-09-30 16:44 UTCEchelonGraph re-scored
  68. 2026-09-30 16:44 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  69. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  70. 2026-09-30 14:50 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  71. 2026-09-30 03:17 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  72. 2026-09-29 15:42 UTCEchelonGraph re-scored
  73. 2026-09-29 15:42 UTCGHSA enrichmentGHSA-c7vw-frhj-6h9j · GitHub severity HIGH · GitHub CVSS 7.5
  74. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  75. 2026-09-29 04:07 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-100700?
CVE-2026-100700 is a high-severity vulnerability; its CVE record was published on September 26, 2026. nodemailer before 10.0.6 contains a denial of service vulnerability in the addressparser free-text fallback regex pattern that exhibits quadratic backtracking behavior. Attackers can supply crafted email header values with long whitespace-free runs to block the Node.js event loop for tens of…
When was CVE-2026-100700 made public?
CVE-2026-100700 was made public on September 11, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 26, 2026. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-100700 actively exploited?
CVE-2026-100700 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100700?
CVE-2026-100700 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100700?
A fix for CVE-2026-100700 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-100700 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-100700

Explore →

Is Your Infrastructure Affected by CVE-2026-100700?

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