CVE Catalog

CVE-2026-50025

MediumCVSS 6.9
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.26%

16th percentile - higher than 16% of all known CVEs

Summary

Mousehole prior to version 0.4.05 has its HTTP/WebSocket management boundary reachable without application-layer authentication or browser/LAN provenance checks. The service stores a MyAnonamouse (MAM) session cookie and reuses the same cookie-bearing serialization for state, API responses, and WebSocket updates, allowing any client reaching the port to read state, replace the cookie, or force MAM update side effects.

Risk Assessment

An attacker with network access to the port can hijack the MAM session or force unauthorized updates. The risk is especially high in mixed-trust LAN/VPN environments.

Recommendation

Update Mousehole to version 0.4.0 or later. Restrict exposure of port 5010 to trusted networks.

Related vulnerabilities

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS