CVE-2026-92598

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

Score 6.5 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 6.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-81298 (ENISA EUVD) · GHSA-r7q5-h7cx-p54x (GitHub Security Advisories)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (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.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Nodemailer before 9.1.0 fails to apply UTS-46 normalization when encoding international domain names, causing the domain resolver to compute a different Punycode A-label than standards-compliant parsers. Attackers can craft recipient addresses with invisible characters or compatibility mappings that pass domain allow-list checks but are delivered to attacker-controlled domains via SMTP.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
45
EG Risk 45/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.4%
EPSS %ILE
34th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% 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; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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; Track* at high (mission-essential systems).

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

Exploitation public PoC (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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 16, 2026

Last Modified

September 22, 2026

Advisory Details (4)

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

Nodemailer before 9.1.0 IDN/Punycode Domain Allow-list Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/nodemailer-before-9.1.0-idn-punycode-domain-allow-list-bypass
GitHub commit Patch Available

commit b212ac4 (nodemailer/nodemailer)

Patch available: nodemailer/nodemailer v9.1.0 (contains commit b212ac4)

https://github.com/nodemailer/nodemailer/commit/b212ac4
GitHub commit Patch Available

commit 259c32d (nodemailer/nodemailer)

Patch available: nodemailer/nodemailer v9.1.0 (contains commit 259c32d)

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

IDN/Punycode domain allow-list bypass leads to email delivery to an attacker-controlled domain · Advisory · nodemailer/nodemailer · GitHub

Affected: 9.1.0

https://github.com/nodemailer/nodemailer/security/advisories/GHSA-wmmp-3585-3rmp

Vendor Advisories for CVE-2026-92598(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 (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-nodemailer6.10.0+~6.4.17-1 ... 9.0.6+~8.0.1-1 (16 versions)
  • every version up to 10.0.0+~8.0.1-1: fixed in 10.0.0+~8.0.1-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
nodemailer—
  • every version up to 9.1.0: fixed in 9.1.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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, 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 15 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-92598?
CVE-2026-92598 is a medium-severity vulnerability; its CVE record was published on September 16, 2026. Nodemailer before 9.1.0 fails to apply UTS-46 normalization when encoding international domain names, causing the domain resolver to compute a different Punycode A-label than standards-compliant parsers. Attackers can craft recipient addresses with invisible characters or compatibility mappings…
When was CVE-2026-92598 made public?
CVE-2026-92598 was made public on September 1, 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 16, 2026. EchelonGraph's copy of the record carries a last-modified date of September 22, 2026; the record at its source may have been updated since.
Is CVE-2026-92598 actively exploited?
CVE-2026-92598 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (34th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92598?
CVE-2026-92598 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92598?
A fix for CVE-2026-92598 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92598 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-92598

Explore →

Is Your Infrastructure Affected by CVE-2026-92598?

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