What’s Vulnerable › Vulnerabilities

CVE-2026-50025: Mousehole: Unauthenticated HTTP/WebSocket boundary exposes and mutates MAM cookie state

• Severity: medium (CVSS 6.9 v4.0)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-09-11 · updated 2026-09-30
• Weakness: CWE-200

Description

Mousehole is a background service to update a seedbox IP for MAM and web app to manage it. Prior to version 0.4.05, Mousehole's HTTP/WebSocket management boundary is reachable without application-layer authentication or browser/LAN provenance checks. The service stores a MyAnonamouse (MAM) session cookie in state and reuses the same cookie-bearing serialization for persisted state, public API responses, and WebSocket state updates. Any client that can reach the published Mousehole port can read cookie-bearing state, connect to WebSocket state updates, replace the stored cookie, or force MAM update side effects. The deployment examples publish port 5010 broadly with Docker's `5010:5010` syntax, which can make the issue reachable on mixed-trust LAN/VPN interfaces. Version 0.4.0 patches the issue.

Affected products

• t-mart mousehole: before 0.4.0

References

• https://github.com/t-mart/mousehole/blob/master/CHANGELOG.md#v040---2026-06-04
• https://github.com/t-mart/mousehole/security/advisories/GHSA-v64r-gfrc-f6vq

Get alerted when CVE-2026-50025 or the next vulnerability affects your stack