CVE-2026-67447 json
Mailpit: SMTP DATA line reader buffers over-limit input before size enforcement
published 2mo ago modified 24d ago also EUVD-2026-63664 , GHSA-r553-m4fv-5v97 , GO-2026-6272
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/axllent/mailpit 1.30.5
- axllent mailpit 1.30.5
- govulncheck-vulndb SLES for SAP applications 16.0, SLES 16.0 0.0.20260827T195228-160000.1.1
suse advisories SUSE-SU-2026:23625-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260827T195228-160000.1.1
opensuse advisories openSUSE-SU-2026:21761-1
Is CVE-2026-67447 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/axllent/mailpit/security/advisories/GHSA-r553-m4fv-5v97 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/axllent/mailpit | >=1.30.0, <1.30.5 |
1.30.5 |
Affected products
- axllent mailpit
Classification
- Weakness
-
- CWE-770 Allocation of Resources Without Limits or Throttling
References
-
github.com
/axllent/mailpit/commit/8720c6bd8281fc00d458081908f1dbef8e59a98c
web, patch
-
github.com
/axllent/mailpit/security/advisories/GHSA-r553-m4fv-5v97
exploit, web, advisory
-
github.com
/axllent/mailpit/releases/tag/v1.30.5
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-67447
advisory
-
github.com
/axllent/mailpit
package
Sources
- CVE List CVE-2026-67447
- GitHub Advisory GHSA-r553-m4fv-5v97
- NVD CVE-2026-67447
- OSV GO-2026-6272
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.