<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-28T10:12:33.710388+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-67447</id>
    <title>fkie_cve-2026-67447</title>
    <updated>2026-09-28T10:12:33.714408+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Mailpit is an email testing tool and API for developers. From 1.30.0 until 1.30.5, Mailpit's internal/smtpd/smtpd.go readData() function calls bufio.Reader.ReadBytes before applying the len(data)+len(line) size check to the completed SMTP DATA line against Server.MaxSize. An unauthenticated SMTP client can send a single line larger than the configured MaxMessageSize, causing the full line to be allocated before Mailpit returns the 552 5.3.4 rejection. This post-fix gap remains after normal multi-line DATA accumulation was bounded, and concurrent oversized lines can create substantial memory pressure beyond the configured message-size cap. This issue is fixed in version 1.30.5.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-67447"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-r553-m4fv-5v97</id>
    <title>GHSA-r553-m4fv-5v97 — Mailpit: SMTP DATA line reader buffers over-limit input before size enforcement</title>
    <updated>2026-09-28T10:12:33.714605+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Go: github.com/axllent/mailpit</p>
<p>## Summary</p>
<p>Mailpit's SMTP DATA reader enforces the configured `MaxMessageSize` only after `bufio.Reader.ReadBytes('\n')` has already buffered a complete DATA line. A remote unauthenticated SMTP client can send one line larger than the configured message-size cap and force memory allocation before Mailpit returns the expected `552 5.3.4` rejection, leaving patched versions still exposed to a single-line incomplete-fix variant of the earlier SMTP DATA body-size issue.</p>
<p>## Technical Details</p>
<p>Mailpit enables SMTP by default. The SMTP server now wires `config.MaxMessageSize` into `srv.MaxSize`:</p>
<p>```go
if config.MaxMessageSize &gt; 0 {
    srv.MaxSize = config.MaxMessageSize * 1024 * 1024
}
```</p>
<p>The DATA reader then checks that cap, but only after reading a full newline-terminated line into memory:</p>
<p>```go
line, err := s.br.ReadBytes('\n')
if err != nil {
    return nil, err
}</p>
<p>if bytes.Equal(line, []byte(".\r\n")) {
    break
}
if line[0] == '.' {
    line = line[1:]
}</p>
<p>if s.srv.MaxSize &gt; 0 {
    if len(data)+len(line) &gt; s.srv.MaxSize {
        _, _ = s.br.Discard(s.br.Buffered())
        return nil, maxSizeExceeded(s.srv.MaxSize)
    }
}
```</p>
<p>This ordering violates the size-limit invariant. The configured cap can reject the message only after the attacker has supplied the line terminator and `ReadBytes('\n')` has allocated the over-limit line. With the default 50 MiB cap, a 64 MiB single DATA line is still buffered before Mailpit returns `552 5.3.4 Requested mail action aborted: ex…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-r553-m4fv-5v97"/>
  </entry>
</feed>
