CVE-2026-67448: axllent mailpit · Improper Handling of URL Encoding
Affects axllent mailpitSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 1.30.6 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.30.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade mailpit and axllent/mailpit to 1.30.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| axllentmailpit | Affected
| Fixed in
|
GitHubaxllent/mailpitpkg:github/axllent/mailpitOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The suggested fix is to perform origin checks on the decoded URL path (r.URL.Path) rather than the raw request URI, ensuring the origin check aligns with routing. Additionally, restoring a proper CheckOrigin function in the WebSocket upgrader to enforce origin validation independently is recommended. Enabling UI authentication (--ui-auth-file) prevents this bypass by requiring authentication. If you cannot patch yet, users should enable UI authentication to mitigate risk.
Description
CVE-2026-67448 is a vulnerability in axllent mailpit versions 1.29.0 through 1.30.5 involving improper handling of URL encoding in WebSocket origin checks. The origin check relies on the raw request URI prefix, but Go's ServeMux routes on the percent-decoded path, allowing an attacker to bypass origin validation by encoding the path. This leads to unauthorized WebSocket connections that can leak sensitive email data. The issue arises because the upgrader accepts all origins and the middleware origin check is bypassed due to inconsistent handling of encoded URLs.