MiroFish CVE-2026-7041

The Werkzeug Debugger PIN Handler at the /console endpoint must be deployed and accessible (not restricted by network controls). Exploitation requires that the SECRET parameter handling in the debugger does not properly validate or sanitize input before processing it, and that the response or error messages leak sensitive information. The attacker must be able to craft HTTP requests to the /console path and receive responses; no authentication is required (PR:N). The high attack complexity (AC:H) suggests the exploit requires specific knowledge of the parameter name, format, or timing, or must work around additional protective mechanisms such as CSRF tokens or request validation. Exploitation is limited by: (1) the debugger typically being intended for development-only use and absent in standard production deployments, (2) proper firewall/network segmentation preventing external access, and (3) frameworks typically disabling debug mode by default in production.

This vulnerability presents LOW real-world risk despite public exploit availability. The CVSS score of 3.7 with AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N indicates: network-accessible but high complexity exploitation, only confidentiality impact (partial data disclosure), no integrity or availability impact, and unchanged system scope. The CVSS Environmental modifier E:P (Exploit Code Maturity: Proof of Concept) and RL:W (Release of Patch Level Workaround) suggest active research but not widespread weaponization. The absence of KEV (CISA Known Exploited Vulnerabilities) listing despite public POC availability further indicates this is not being actively exploited in real attacks. Risk is CONDITIONAL on: (1) the debugger endpoint being exposed in production (highly unlikely in properly configured deployments), (2) attacker knowing to target this specific parameter, and (3) the SECRET containing sensitive data worth extracting. Organizations with development instances exposed to the internet face higher risk; standard production deployments are unlikely to be vulnerable.

An attacker discovers that a MiroFish instance is exposed on the public internet with the /console debugger endpoint accessible. The attacker sends a crafted HTTP request to /console with a manipulated SECRET parameter, triggering information disclosure in the Werkzeug Debugger PIN Handler. By analyzing the response or error messages, the attacker extracts sensitive application secrets, configuration values, or authentication tokens that may be cached in the debugger state.