CVE-2026-45713

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated
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.6%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the Mailpit SMTP server has a Server.MaxSize int field that controls the maximum allowed DATA payload size, but the field is never assigned anywhere outside test code, leaving it at Go's zero value (0 ⇒ "no limit"). The same applies to the HTTP /api/v1/send endpoint, whose request body is decoded with json.NewDecoder(r.Body) and no http.MaxBytesReader. Because Mailpit's default listeners bind [::]:1025 (SMTP) and [::]:8025 (HTTP), with no authentication required on either, a single network-reachable attacker can push an arbitrarily large message into Mailpit and watch RAM consumption spike with a ~7-10× amplification factor (raw frame → enmime envelope tree → search-text index → zstd-encoded write to SQLite). Repeating the attack — or running it concurrently from multiple connections — drives the process to OOM-kill. Version 1.30.0 contains a patch.

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.6%
EPSS %ILE
48th
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.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-19). 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: 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.

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

May 19, 2026

Last Modified

July 28, 2026

Advisory Details (2)

Auto-updated Jul 20, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Unauthenticated remote memory-exhaustion DoS via unlimited SMTP DATA and /api/v1/send body sizes · Advisory · axllent/mailpit · GitHub

https://github.com/axllent/mailpit/security/advisories/GHSA-fpxj-m5q8-fphw
GitHub release Patch Available

Release v1.30.0 (axllent/mailpit)

Patch available: axllent/mailpit v1.30.0

https://github.com/axllent/mailpit/releases/tag/v1.30.0

Vendor Advisories for CVE-2026-45713(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/axllent/mailpit—
  • every version up to 1.30.0: fixed in 1.30.0
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 it from the CNA feed. 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). Most recent first.

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

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-45713?
CVE-2026-45713 is a high-severity vulnerability; its CVE record was published on May 19, 2026. Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the Mailpit SMTP server has a Server.MaxSize int field that controls the maximum allowed DATA payload size, but the field is never assigned anywhere outside test code, leaving it at Go's zero value (0 ⇒ "no limit").…
When was the CVE record for CVE-2026-45713 published?
The CVE record for CVE-2026-45713 was published on May 19, 2026. 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 July 28, 2026; the record at its source may have been updated since.
Is CVE-2026-45713 actively exploited?
CVE-2026-45713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-45713?
CVE-2026-45713 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-45713?
A fix for CVE-2026-45713 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-45713 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-45713

Explore →

Is Your Infrastructure Affected by CVE-2026-45713?

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

Book a Demo →Browse All CVEs