<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Cve-2026-45713 — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/cve-2026-45713/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Tue, 19 May 2026 15:54:46 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/cve-2026-45713/feed.xml" rel="self" type="application/rss+xml"/><item><title>Mailpit Unauthenticated Remote Memory Exhaustion DoS Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-05-mailpit-dos/</link><pubDate>Tue, 19 May 2026 15:54:46 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-05-mailpit-dos/</guid><description>Mailpit is vulnerable to an unauthenticated remote memory-exhaustion denial-of-service attack due to missing size limits on incoming SMTP DATA and HTTP requests, leading to unbounded memory and disk growth, potentially crashing the application.</description><content:encoded><![CDATA[<p>Mailpit is susceptible to an unauthenticated remote denial-of-service (DoS) attack due to the absence of input size validation for SMTP DATA payloads and HTTP requests to the <code>/api/v1/send</code> endpoint. Specifically, the <code>Server.MaxSize</code> field in the Mailpit SMTP server, intended to control the maximum allowed DATA payload size, is never assigned a value, effectively disabling the size limit. Similarly, the HTTP endpoint lacks <code>http.MaxBytesReader</code>, resulting in unbounded memory allocation when processing requests. This vulnerability allows a network-reachable attacker to exhaust server memory by sending arbitrarily large messages via SMTP or HTTP, leading to an out-of-memory (OOM) condition and subsequent process termination. The default configuration binds listeners to <code>[::]:1025</code> (SMTP) and <code>[::]:8025</code> (HTTP) without authentication, exacerbating the risk. The issue affects Mailpit versions prior to 1.30.0.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker establishes a connection to the Mailpit SMTP server on <code>[::]:1025</code> or the HTTP server on <code>[::]:8025</code>.</li>
<li>For SMTP, the attacker sends <code>HELO</code>, <code>MAIL FROM</code>, and <code>RCPT TO</code> commands to initiate a mail transaction.</li>
<li>The attacker sends the <code>DATA</code> command, signaling the start of the message body.</li>
<li>The attacker sends an arbitrarily large amount of data as the message body. Since the <code>MaxSize</code> limit is not enforced, the server buffers all incoming data in memory.</li>
<li>For HTTP, the attacker sends a <code>POST</code> request to <code>/api/v1/send</code> with a large JSON payload in the request body, without exceeding the server&rsquo;s read timeout.</li>
<li>Mailpit attempts to process the excessively large message, leading to high memory consumption.</li>
<li>Memory usage continues to increase as the attacker sends more data, exceeding available system resources.</li>
<li>The Mailpit process is terminated by the operating system due to an out-of-memory (OOM) condition, resulting in a denial-of-service.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows unauthenticated remote attackers to perform a denial-of-service attack against Mailpit installations. This can lead to service disruption, preventing legitimate users from utilizing the email testing functionality. Observed memory amplification reaches factors of 7-10x. The attack also fills disk space as oversized messages are persisted to the SQLite store.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Mailpit to version 1.30.0 or later to remediate CVE-2026-45713.</li>
<li>Deploy the Sigma rule &ldquo;Detect Mailpit Excessive SMTP Data&rdquo; to identify potential exploitation attempts by monitoring for unusually large SMTP data transfers.</li>
<li>Deploy the Sigma rule &ldquo;Detect Mailpit Excessive HTTP API Send Payload&rdquo; to identify potential exploitation attempts by monitoring for unusually large HTTP POST requests to the <code>/api/v1/send</code> endpoint.</li>
<li>Consider implementing network-level rate limiting on ports 1025 (SMTP) and 8025 (HTTP) to mitigate the impact of potential DoS attacks.</li>
<li>Monitor system resource utilization (CPU, memory, disk I/O) on servers running Mailpit to detect anomalous behavior.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>dos</category><category>memory exhaustion</category><category>cve-2026-45713</category><category>mailpit</category></item></channel></rss>