# CVE-2026-50025

## Summary

- **CVE ID:** CVE-2026-50025
- **Severity:** MEDIUM
- **CVSS Score:** 6.9 (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)
- **CWE:** CWE-200, CWE-306, CWE-346, CWE-352, CWE-862
- **Published:** Sep 11, 2026
- **Last Modified:** Sep 11, 2026

## 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 (< 0.4.0)

## References

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

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-12._