CVE-2026-50025 Mousehole: Unauthenticated HTTP/WebSocket boundary exposes and mutates MAM cookie state
Unauthenticated access to Mousehole allows attackers to read and modify MAM session cookies, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-50025?
CVE-2026-50025 is a medium-severity missing authorization vulnerability in t-mart mousehole, published on 11 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Which versions are affected by CVE-2026-50025?
How do I fix CVE-2026-50025?
No fix has been published for CVE-2026-50025 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-50025 being exploited?
There is no known exploitation of CVE-2026-50025 in the wild and no public exploit code.
Sources
Also known as GHSA-v64r-gfrc-f6vq.