Unauthenticated data access and deletion via REST APIs
Published Apr 26, 2026 · Updated Apr 26, 2026
Missing authentication in 666ghj MiroFish 0.1.0 through 0.1.2 allows remote attackers to read or delete project data via REST APIs. The create_app factory registers graph, simulation, and report blueprints without authentication middleware or per-route checks. Any client that can reach the backend API can list sensitive project and report data, delete stored files, or interrupt simulations.
Summary
What happened
Missing authentication in 666ghj MiroFish 0.1.0 through 0.1.2 allows remote attackers to read or delete project data via REST APIs. The create_app factory registers graph, simulation, and report blueprints without authentication middleware or per-route checks. Any client that can reach the backend API can list sensitive project and report data, delete stored files, or interrupt simulations.
The record
- CVE
- CVE-2026-7042
- Published
- Apr 26, 2026
- Updated
- Apr 26, 2026
- Vendor
- 666ghj
- Product
- MiroFish
- Classifications
- CWE-287, CWE-306, T1190
- 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
- Unauthenticated REST API request proof of conceptproof 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