CVE-2026-50025
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Summary
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 Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| t-mart | mousehole | < 0.4.0 | affected |
Weaknesses
- CWE-200: CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
- CWE-306: CWE-306: Missing Authentication for Critical Function
- CWE-346: CWE-346: Origin Validation Error
- CWE-352: CWE-352: Cross-Site Request Forgery (CSRF)
- CWE-862: CWE-862: Missing Authorization
References
- https://github.com/t-mart/mousehole/security/advisories/GHSA-v64r-gfrc-f6vq
- https://github.com/t-mart/mousehole/blob/master/CHANGELOG.md#v040—2026-06-04
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.