CVE-2026-67448 json
Mailpit: WebSocket origin check bypass via percent-encoded path (regression of CVE-2026-22689)
published 2mo ago modified 24d ago also EUVD-2026-63668 , GHSA-8r62-w5wh-fc5m , GO-2026-6271
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
Mailpit is an email testing tool and API for developers. From 1.29.0 until 1.30.6, Mailpit's server/server.go origin middleware checks the raw RequestURI for the /api/ prefix while Go's ServeMux routes using the percent-decoded URL path, and server/websockets/client.go configures websocket.Upgrader.CheckOrigin to return true. A malicious website can request /%61pi/events, skip corsOriginAccessControl(), reach the /api/events WebSocket handler, and receive live message IDs, Message-Id values, sender and recipient fields, subjects, tags, and body snippets from an unauthenticated default Mailpit instance after the user visits the site. This is a regression of the earlier WebSocket origin protection and does not affect deployments protected by --ui-auth-file. This issue is fixed in version 1.30.6.
Patch / fix
- go github.com/axllent/mailpit 1.30.6
- axllent mailpit 1.30.6
- 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-67448 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
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/axllent/mailpit | >=1.29.0, <1.30.6 |
1.30.6 |
Affected products
- axllent mailpit
Classification
References
-
github.com
/axllent/mailpit/commit/fbe5e006c3f1682b819df58b4a932d7a84920be9
web, patch
-
github.com
/axllent/mailpit/security/advisories/GHSA-8r62-w5wh-fc5m
web, advisory
-
github.com
/axllent/mailpit/releases/tag/v1.30.6
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-67448
advisory
-
github.com
/axllent/mailpit
package
Sources
- CVE List CVE-2026-67448
- GitHub Advisory GHSA-8r62-w5wh-fc5m
- NVD CVE-2026-67448
- OSV GO-2026-6271
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.