CVE-2026-90776

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-30. 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-77000 (ENISA EUVD) · GHSA-prgh-xp8r-p3m5 (GitHub Security Advisories) · GHSA-vm5r-23w9-m8hx (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.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Nodemailer versions 9.1.0 through 10.0.4 contain a quadratic time complexity vulnerability in the addressparser component when parsing email addresses with RFC 5322 comments. Attackers can craft malicious email headers with comment-separated atoms to consume excessive CPU and block the Node.js event loop for several seconds, causing denial of service.

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.7%
EPSS %ILE
53rd
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.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). 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 13, 2026

Last Modified

September 24, 2026

Advisory Details (6)

Auto-updated Sep 13, 2026
Patch available. Sources: github, github_commit, github_release.
Web page

Nodemailer 9.1.0 through 10.0.4 Denial of Service via Quadratic Address Parsing | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nodemailer-9.1.0-through-10.0.4-denial-of-service-via-quadratic-address-parsing
Web page

GitHub - nodemailer/nodemailer: ✉️ Send e-mails with Node.JS – easy as cake! · GitHub

https://github.com/nodemailer/nodemailer
GitHub release Patch Available

v10.0.5

Patch available: nodemailer/nodemailer v10.0.5

https://github.com/nodemailer/nodemailer/releases/tag/v10.0.5
Web page

nodemailer/src/addressparser/index.ts at v10.0.4 · nodemailer/nodemailer · GitHub

https://github.com/nodemailer/nodemailer/blob/v10.0.4/src/addressparser/index.ts#L251
GitHub commit Patch Available

commit c07f17518d25 (nodemailer/nodemailer)

Patch available: nodemailer/nodemailer v10.0.5 (contains commit c07f17518d25)

https://github.com/nodemailer/nodemailer/commit/c07f17518d25aca8ab2ad66968dcbca538c24b89
GitHub advisoryMentions a patch (unverified)

addressparser: O(n^2) on comment-joined addresses enables a remote DoS (reachable via mailparser) · Advisory · nodemailer/nodemailer · GitHub

https://github.com/nodemailer/nodemailer/security/advisories/GHSA-prgh-xp8r-p3m5

Vendor Advisories for CVE-2026-90776(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmnodemailer @ 10.0.5 (fixes >= 9.1.0, <= 10.0.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

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 (26 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 (19 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—
  • 9.1.0 up to 10.0.5: fixed in 10.0.5
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 149 rows on record for this CVE, as 99 entries (1 repeat merged).

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. 1 repeat row among the latest 100 is merged into the row it repeats. The 49 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-90776?
CVE-2026-90776 is a high-severity vulnerability; its CVE record was published on September 13, 2026. Nodemailer versions 9.1.0 through 10.0.4 contain a quadratic time complexity vulnerability in the addressparser component when parsing email addresses with RFC 5322 comments. Attackers can craft malicious email headers with comment-separated atoms to consume excessive CPU and block the Node.js…
When was CVE-2026-90776 made public?
CVE-2026-90776 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 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-90776 actively exploited?
CVE-2026-90776 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90776?
CVE-2026-90776 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-90776?
A fix for CVE-2026-90776 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90776 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-90776

Explore →

Is Your Infrastructure Affected by CVE-2026-90776?

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