Debugger secret disclosure via exposed console
Published Apr 26, 2026 · Updated Apr 26, 2026
Information disclosure in 666ghj MiroFish 0.1.0 through 0.1.2 allows remote attackers to read a Werkzeug debugger secret via /console. The debug-enabled Flask backend renders its Werkzeug interactive console with the SECRET value embedded in page JavaScript. Network access to backend port 5001 is sufficient for disclosure; code execution additionally requires the debugger PIN from logs or guessing.
Summary
What happened
Information disclosure in 666ghj MiroFish 0.1.0 through 0.1.2 allows remote attackers to read a Werkzeug debugger secret via /console. The debug-enabled Flask backend renders its Werkzeug interactive console with the SECRET value embedded in page JavaScript. Network access to backend port 5001 is sufficient for disclosure; code execution additionally requires the debugger PIN from logs or guessing.
The record
- CVE
- CVE-2026-7041
- Published
- Apr 26, 2026
- Updated
- Apr 26, 2026
- Vendor
- 666ghj
- Product
- MiroFish
- Classifications
- CWE-284, CWE-200
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 26, 2026CVE publishedPublication date reported by the CVE source.
- Apr 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.1.0
- Affected versionversion=0.1.1
- Affected versionversion=0.1.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- MiroFish Werkzeug debugger reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo