CVE-2026-67448Network attack vectorHinoki check available

Message disclosure via WebSocket origin bypass

Published Aug 20, 2026 · Updated Aug 20, 2026

Origin validation error in Axllent Mailpit before 1.30.6 allows remote attackers to read message metadata via a crafted WebSocket path. In server/server.go, the CORS middleware keys its /api/ check on raw RequestURI while Go routes on decoded r.URL.Path; requesting /%61pi/events therefore skips corsOriginAccessControl() and still reaches /api/events, and server/websockets/client.go configured websocket.Upgrader.CheckOrigin to accept every origin before the fix. Exploitation requires a default unauthenticated Mailpit instance and user interaction to load a malicious website; deployments protected by --ui-auth-file are not exposed, and the observed disclosure is limited to live message IDs, Message-Id values, sender and recipient fields, subjects, tags, and body snippets.

CVSS severity6.5
Medium
EPSS probability0.15%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Origin validation error in Axllent Mailpit before 1.30.6 allows remote attackers to read message metadata via a crafted WebSocket path. In server/server.go, the CORS middleware keys its /api/ check on raw RequestURI while Go routes on decoded r.URL.Path; requesting /%61pi/events therefore skips corsOriginAccessControl() and still reaches /api/events, and server/websockets/client.go configured websocket.Upgrader.CheckOrigin to accept every origin before the fix. Exploitation requires a default unauthenticated Mailpit instance and user interaction to load a malicious website; deployments protected by --ui-auth-file are not exposed, and the observed disclosure is limited to live message IDs, Message-Id values, sender and recipient fields, subjects, tags, and body snippets.

The record

CVE
CVE-2026-67448
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
Axllent
Product
Mailpit
Classifications
CWE-346, CWE-177, T1189
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 1.29.0, < 1.30.6

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Axllent · Mailpitversion=>= 1.29.0, < 1.30.6

Published CVSS scores

6.5GitHub Advisory DatabaseCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-346Origin Validation Error
CWE-177Improper Handling of URL Encoding (Hex Encoding)
T1189Drive-by Compromise

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo