Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the mailpit dump --http sub-command downloads every message from a remote Mailpit instance and writes each one as .eml inside the user-supplied output directory. The message ID field is taken verbatim from the JSON response of the remote server and concatenated into the output path with path.Join, which silently normalizes .. segments. A malicious HTTP server impersonating Mailpit can therefore make mailpit dump write attacker-controlled bytes to any path the running user can write, fully outside the intended output directory. Version 1.30.0 contains a patch.
CVE-2026-45711
This medium-severity CVE scores 5.9 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.0%, top 90% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.9
- EG Score
- 5.9(low)
- EPSS
- 16.4%
- KEV
- Not listed
Published
May 19, 2026
Last Modified
July 21, 2026
Advisory Details (2)
Auto-updated Jul 21, 2026Path traversal & arbitrary file write in mailpit dump --http via attacker-controlled message IDs · Advisory · axllent/mailpit · GitHub
https://github.com/axllent/mailpit/security/advisories/GHSA-qx5x-85p8-vg4jRelease v1.30.0 (axllent/mailpit)
Patch available: axllent/mailpit v1.30.0
https://github.com/axllent/mailpit/releases/tag/v1.30.0Vendor Advisories for CVE-2026-45711(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)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| github.com/axllent/mailpit | — | 1.30.0 | — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 2× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-05-24 06:14 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-829 · CWE-22
Frequently asked(5)
What is CVE-2026-45711?
When was CVE-2026-45711 disclosed?
Is CVE-2026-45711 actively exploited?
What is the CVSS score of CVE-2026-45711?
How do I remediate CVE-2026-45711?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45711
Is Your Infrastructure Affected by CVE-2026-45711?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.