CVE-2025-59937

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.5% (46th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Elevated

Also known asEUVD-2025-31582 (ENISA EUVD) · GHSA-wpwj-69cm-q9c5 (GitHub Security Advisories) · GO-2025-3988 (OSV.dev)Source: ENISA EUVD

9.1EG
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.5%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

go-mail is a comprehensive library for sending mails with Go. In versions 0.7.0 and below, due to incorrect handling of the mail.Address values when a sender- or recipient address is passed to the corresponding MAIL FROM or RCPT TO commands of the SMTP client, there is a possibility of wrong address routing or even ESMTP parameter smuggling. For successful exploitation, it is required that the user's code allows for arbitrary mail address input (i. e. through a web form or similar). If only static mail addresses are used (i. e. in a config file) and the mail addresses in use do not consist of quoted local parts, this should not affect users. This issue is fixed in version 0.7.1

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
57
EG Risk 57/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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.5%
EPSS %ILE
46th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.5% 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 29, 2025

Last Modified

October 9, 2026

Advisory Details (4)

Auto-updated Aug 1, 2026
Patch available. Sources: github_pr, github, github_commit.
Web page

Mail address parsing bug: RCPT misroute + ESMTP parameter smuggling · Issue #495 · wneessen/go-mail · GitHub

https://github.com/wneessen/go-mail/issues/495
GitHub advisoryMentions a patch (unverified)

Insufficient address encoding when passing mail addresses to the SMTP client · Advisory · wneessen/go-mail · GitHub

https://github.com/wneessen/go-mail/security/advisories/GHSA-wpwj-69cm-q9c5
GitHub pull request Patch Available

Fix vulnerability in mail address passing to the smtp client

Patch available: wneessen/go-mail v0.7.1 (PR #496 merged 2025-09-26)

https://github.com/wneessen/go-mail/pull/496
GitHub commit Patch Available

commit 42e92cfe027b (wneessen/go-mail)

Patch available: wneessen/go-mail v0.7.1 (contains commit 42e92cfe027b)

https://github.com/wneessen/go-mail/commit/42e92cfe027be04aff72921adb0f72f11d517479

Vendor Advisories for CVE-2025-59937(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
gogithub.com/wneessen/go-mail @ 0.7.1 (fixes < 0.7.1)—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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/wneessen/go-mail—
  • every version up to 0.7.1: fixed in 0.7.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 254 rows on record for this CVE, as 98 entries (2 repeats 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 154 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-59937?
CVE-2025-59937 is a critical-severity vulnerability; its CVE record was published on September 29, 2025. go-mail is a comprehensive library for sending mails with Go. In versions 0.7.0 and below, due to incorrect handling of the mail.Address values when a sender- or recipient address is passed to the corresponding MAIL FROM or RCPT TO commands of the SMTP client, there is a possibility of wrong…
When was the CVE record for CVE-2025-59937 published?
The CVE record for CVE-2025-59937 was published on September 29, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2025-59937 actively exploited?
CVE-2025-59937 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (46th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-59937?
CVE-2025-59937 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-59937?
A fix for CVE-2025-59937 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-59937 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-2025-59937

Explore →

Is Your Infrastructure Affected by CVE-2025-59937?

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

Book a Demo →Browse All CVEs