# 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.

- **Severity:** Medium 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-v64r-gfrc-f6vq

## 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.

Weakness: CWE-862 (Missing Authorization), CWE-346 (Origin Validation Error), CWE-306 (Missing Authentication for Critical Functionality), CWE-352 (Cross-Site Request Forgery), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.

## Is CVE-2026-50025 being exploited?

There is no known exploitation of CVE-2026-50025 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50025 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-50025 in the wild and no public exploit code.

Affected product: t-mart mousehole. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50025/ (Markdown: https://insights.sbomify.com/CVE-2026-50025/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50025
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50025
- OSV: https://osv.dev/vulnerability/CVE-2026-50025

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50025/
Summaries are generated and may contain mistakes; the official description above is the record.