CVE-2026-21859: Mailpit Proxy Endpoint has Server-Side Request Forgery (SSRF) vulnerability
Summary A Server-Side Request Forgery (SSRF) vulnerability exists in Mailpit's /proxy endpoint that allows attackers to make requests to internal network resources. Description The /proxy endpoint allows requests to internal network resources. While it validates http:// and https:// schemes, it does not block internal IP addresses, allowing attackers to access internal services and APIs.
Published Jan 6, 2026 · Updated Jan 20, 2026
Affected packages
github.com/axllent/mailpit
- Ecosystem
- Go
- Affected
- <= 1.28.0
- Fixed in
- 1.28.1
- Check
go list -m github.com/axllent/mailpit
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
A Server-Side Request Forgery (SSRF) vulnerability exists in Mailpit's /proxy endpoint that allows attackers to make requests to internal network resources.
Description
The /proxy endpoint allows requests to internal network resources. While it validates http:// and https:// schemes, it does not block internal IP addresses, allowing attackers to access internal services and APIs.
Proof of Concept
Basic SSRF Request
GET /proxy?url=http://127.0.0.1:8025/api/v1/infoThis returns internal API data including database path and runtime statistics.
Impact Assessment
1. Internal Network Scanning
Attacker can probe and discover internal services on the network.
2. Information Disclosure
Access to internal API data, database paths, and runtime statistics.
3. Email Content Access
Ability to read all captured emails via internal API endpoints.
4. Cloud Metadata Access
If deployed in cloud environments (AWS/GCP/Azure), potential access to instance metadata services (e.g., http://169.254.169.254/).
Attack Scenarios
Scenario 1: Development Environment Exposure
If Mailpit is accidentally exposed to the internet, attackers can leverage SSRF to access internal development resources and services.
Scenario 2: Container Escape Information
In containerized deployments, SSRF can reveal container metadata and internal service configurations.
Scenario 3: Lateral Movement
In corporate networks, SSRF can be used to discover and interact with internal services, facilitating lateral movement.
Mitigating Factors
This vulnerability is limited to HTTP GET requests with minimal headers. Additionally, Mailpit's web UI & API should be protected by basic authentication when exposed to the internet, which prevents access to the proxy endpoint.
References
Credited to omarkurt.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-67445
Mailpit: SMTP command parser buffers unbounded command lines before syntax rejection
high7.5Sep 2, 2026CVE-2026-67446
Mailpit: Thumbnail generation decodes unbounded image dimensions before scaling
high7.5Sep 2, 2026CVE-2026-67447
Mailpit: SMTP DATA line reader buffers over-limit input before size enforcement
medium5.3Aug 20, 2026CVE-2026-67448
Mailpit: WebSocket origin check bypass via percent-encoded path (regression of CVE-2026-22689)
medium6.5Aug 20, 2026CVE-2026-48824
Mailpit: Sibling-endpoint memory-exhaustion DoS via unbounded JSON body on /api/v1/messages, /api/v1/tags, and /api/v1/message/{id}/release (incomplete fix of GHSA-fpxj-m5q8-fphw)
medium5.3Jul 1, 2026CVE-2026-55187
Mailpit: Incomplete SSRF protection in Link Check API via IPv6 transition mechanisms
medium5.8Jun 19, 2026
