CVE-2026-50025

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.9
EG Score
6.9(medium)
EG Risk
46(Track)
EG Risk 46/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity69% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

September 11, 2026

Last Modified

September 14, 2026

Advisory Details (2)

Auto-updated Sep 11, 2026
Patch available. Sources: github.
generic

mousehole/CHANGELOG.md at master · t-mart/mousehole · GitHub

https://github.com/t-mart/mousehole/blob/master/CHANGELOG.md#v040---2026-06-04
github Patch Available

Unauthenticated HTTP/WebSocket boundary exposes and mutates Mousehole MAM cookie state · Advisory · t-mart/mousehole · GitHub

https://github.com/t-mart/mousehole/security/advisories/GHSA-v64r-gfrc-f6vq

Weakness Classification(5)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 15× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 00:43 UTCEG score recompute
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-17 23:52 UTCEG score recompute
  4. 2026-09-16 22:21 UTCEG score recompute
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-15 21:21 UTCEG score recompute
  8. 2026-09-14 20:27 UTCEG score recompute
  9. 2026-09-14 20:15 UTCEG score recompute
  10. 2026-09-13 23:03 UTCEG score recompute
  11. 2026-09-13 16:47 UTCEPSS rescore
  12. 2026-09-12 22:12 UTCEG score recompute
  13. 2026-09-11 21:21 UTCEG score recompute
  14. 2026-09-11 20:49 UTCEG score recompute
  15. 2026-09-11 20:48 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-50025?
CVE-2026-50025 is a medium vulnerability published on September 11, 2026. 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…
When was CVE-2026-50025 disclosed?
CVE-2026-50025 was first published in the National Vulnerability Database on September 11, 2026, with the most recent update on September 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50025 actively exploited?
CVE-2026-50025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 92.1% of all scored CVEs.
What is the CVSS score of CVE-2026-50025?
CVE-2026-50025 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-50025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50025, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50025

Explore →

Is Your Infrastructure Affected by CVE-2026-50025?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs