CVE-2026-45713: CWE-400: Uncontrolled Resource Consumption in axllent mailpit
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.
AI Analysis
Technical Summary
CVE-2026-45713 describes a resource exhaustion vulnerability in Mailpit's SMTP server and HTTP /api/v1/send endpoint prior to version 1.30.0. The Server.MaxSize integer field, intended to limit the maximum allowed DATA payload size, is never assigned outside test code, defaulting to zero which means no limit. The HTTP endpoint similarly lacks request body size limits. Both listeners bind to network-accessible ports without authentication, allowing remote attackers to send arbitrarily large messages. These messages cause amplified RAM consumption through internal processing steps, potentially leading to out-of-memory kills. The vulnerability is fixed in Mailpit 1.30.0.
Potential Impact
An unauthenticated remote attacker can cause Mailpit to consume excessive memory by sending very large email messages or HTTP requests. This can lead to denial of service via process termination (OOM kill). There is no impact on confidentiality or integrity reported. The CVSS 3.1 base score is 7.5 (High) reflecting network attack vector, no privileges required, no user interaction, and high impact on availability.
Mitigation Recommendations
Version 1.30.0 of Mailpit contains a patch that properly enforces maximum payload sizes to prevent uncontrolled resource consumption. Users should upgrade to version 1.30.0 or later. No other official remediation or temporary fixes are documented. Until patched, restricting network access to Mailpit's SMTP and HTTP ports can reduce exposure.
CVE-2026-45713: CWE-400: Uncontrolled Resource Consumption in axllent mailpit
Description
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.1
Score 7.5high
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-45713 describes a resource exhaustion vulnerability in Mailpit's SMTP server and HTTP /api/v1/send endpoint prior to version 1.30.0. The Server.MaxSize integer field, intended to limit the maximum allowed DATA payload size, is never assigned outside test code, defaulting to zero which means no limit. The HTTP endpoint similarly lacks request body size limits. Both listeners bind to network-accessible ports without authentication, allowing remote attackers to send arbitrarily large messages. These messages cause amplified RAM consumption through internal processing steps, potentially leading to out-of-memory kills. The vulnerability is fixed in Mailpit 1.30.0.
Potential Impact
An unauthenticated remote attacker can cause Mailpit to consume excessive memory by sending very large email messages or HTTP requests. This can lead to denial of service via process termination (OOM kill). There is no impact on confidentiality or integrity reported. The CVSS 3.1 base score is 7.5 (High) reflecting network attack vector, no privileges required, no user interaction, and high impact on availability.
Mitigation Recommendations
Version 1.30.0 of Mailpit contains a patch that properly enforces maximum payload sizes to prevent uncontrolled resource consumption. Users should upgrade to version 1.30.0 or later. No other official remediation or temporary fixes are documented. Until patched, restricting network access to Mailpit's SMTP and HTTP ports can reduce exposure.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-13T05:51:48.665Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5e3e5d2a4a8d5989464da3
Added to database: 07/20/2026, 15:27:25 UTC
Last enriched: 07/20/2026, 15:42:05 UTC
Last updated: 07/20/2026, 20:55:48 UTC
Views: 11
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.