Answer in brief
CVE-2026-67448 records a Medium severity (CVSS 6.5) vulnerability in Mailpit: WebSocket origin check bypass via percent-encoded path (regression of CVE-2026-22689). The current sources do not mark it as known exploited. The current feed maps axllent/mailpit (generic), github.com/axllent/mailpit (go), github.com/axllent/mailpit (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.5. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps axllent/mailpit (generic), github.com/axllent/mailpit (go), github.com/axllent/mailpit (go). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| axllent/mailpitgeneric | >=1.29.0 <1.30.6 | 1.30.6 |
| github.com/axllent/mailpitgo | >=1.29.0 <1.30.6 | 1.30.6 |
| github.com/axllent/mailpitgo | >=1.29.0,<=1.30.5 | 1.30.6 |
Published upstream
Aug 20, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 20, 2026
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.
Quoted source text, attributed separately from HOL analysis.