Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDiscover exposed MiroFish API endpoint
-
DeliverySend unauthenticated HTTP request to protected endpoint
-
ExploitBypass missing authentication check in create_app
-
ExecutionAccess confidential data or modify application state
-
ImpactMaintain persistence through API manipulation
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication required for critical functions
MITRE ATT&CK
1 technique across 1 tactic: Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Remote unauthenticated exploitation against default REST API configurations. The vulnerability triggers when the create_app function in backend/app/__init__.py initializes the Flask application without properly configuring authentication middleware or endpoint decorators. No special configuration, user interaction, or authentication is required (CVSS PR:N/UI:N). Exploitation requires only network connectivity to the REST API endpoints (typically HTTP/HTTPS on standard ports). Limiting factors: exploitation impact is constrained to Low across C/I/A per CVSS vector, suggesting authentication bypass provides partial rather than complete unauthorized access - likely restricted to specific API operations or data subsets rather than full administrative control. The Scope:Unchanged (S:U) indicates the vulnerability does not enable lateral movement to other components. |
| Impact | Real-world risk is HIGH despite moderate CVSS impacts (C:L/I:L/A:L). The CVSS vector confirms this is a network-accessible, low-complexity attack requiring no privileges or user interaction (AV:N/AC:L/PR:N/UI:N), making it trivially exploitable by remote unauthenticated attackers. The Proof-of-Concept exploit published at GitHub issue #487 lowers the barrier to exploitation significantly. While individual impacts are rated Low rather than High, the combination of confidentiality, integrity, and availability impacts means attackers gain partial unauthorized access across all three security domains. The vendor's non-responsiveness to the vulnerability report (RL:X - remediation level unavailable) is a critical risk multiplier, as no official patch timeline exists. Organizations using MiroFish 0.1.2 or earlier with REST API exposed to the internet face immediate exploitation risk. The lack of EPSS data and KEV listing suggests this is not yet widely exploited in the wild, but the public POC makes automated scanning and exploitation likely in the near term. Priority should be CRITICAL for internet-facing deployments, MEDIUM for internal-only deployments with network segmentation. |
| Exploit ScenarioDerived | A remote attacker scans the internet for MiroFish installations using Shodan or similar tools, identifying exposed REST API endpoints. Using the publicly available exploit from GitHub issue #487, the attacker sends crafted HTTP requests directly to protected API endpoints without authentication credentials. The vulnerable create_app function processes these requests, bypassing intended authentication checks and allowing the attacker to read sensitive data, modify application state, or disrupt service availability depending on the specific API endpoints exposed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 26, 2026
Missing authentication in MiroFish REST API allows remote attackers to bypass security controls and access protected endpoints without credentials. The vulnerability affects MiroFish versions up to 0.1.2 in the create_app function within backend/app/__init__.py. A publicly available exploit demonstrates the attack (GitHub issue #487), and the vulnerability is trivially exploitable with CVSS complexity rated Low and no authentication required (CVSS:3.1/AV:N/AC:L/PR:N/UI:N). The vendor has not responded to responsible disclosure attempts, leaving users without an official patch. With CVSS 7.3 (High) and confirmed public POC, this represents an immediate risk to deployments exposing the REST API to untrusted networks.
RemediationAI
No vendor-released patch exists at time of analysis - the project maintainer has not responded to vulnerability disclosure via GitHub issue #487. Organizations must implement compensating controls immediately: (1) Deploy a reverse proxy (nginx, Apache, or cloud WAF) in front of MiroFish with authentication enforcement at the proxy layer using HTTP Basic Auth, OAuth2, or API keys; note this adds operational complexity for legitimate API clients who must now authenticate twice. (2) Restrict network access to the REST API endpoints using firewall rules, allowing only trusted IP ranges or internal networks; this breaks legitimate remote API access. (3) If the REST API is not required for operations, disable it entirely by modifying backend/app/__init__.py to comment out API route registration; this eliminates API functionality. (4) Monitor for unauthorized API access attempts via application logs and network intrusion detection. (5) Consider forking the project and applying authentication decorators to vulnerable endpoints, but this requires Python/Flask expertise and ongoing maintenance burden. Reference the exploit details at https://vuldb.com/vuln/359621 and https://github.com/666ghj/MiroFish/issues/487 to understand the exact attack pattern for detection signatures. Organizations should urgently evaluate alternative products given vendor unresponsiveness.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This vulnerability stems from CWE-306 (Missing Authentication for Critical Function) in the MiroFish REST API initialization code. The create_app function in backend/app/__init__.py fails to properly enforce authentication requirements on API endpoints, allowing unauthenticated remote callers to interact with protected resources. MiroFish appears to be a Python-based application using Flask or similar framework for its REST API (based on the create_app factory pattern common in Flask applications). The flaw likely involves missing decorators, middleware, or before_request handlers that should validate authentication tokens or session credentials before processing API requests. The CPE identifier cpe:2.3:a:666ghj:mirofish indicates this is a third-party open-source project maintained by developer 666ghj on GitHub.
Know when Mirofish gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from Vendor (VulDB) · only source for this CVE.
CVSS VectorVendor: VulDB
Lifecycle Timeline
5DescriptionCVE.org
A flaw has been found in 666ghj MiroFish up to 0.1.2. This affects the function create_app of the file backend/app/__init__.py of the component REST API Endpoint. Executing a manipulation can lead to missing authentication. It is possible to launch the attack remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Executive ViewAI
MiroFish versions up to 0.1.2 contain an unauthenticated REST API vulnerability that allows remote attackers to bypass all access controls and retrieve protected data without credentials. This HIGH-severity issue affects any organization running exposed MiroFish instances and requires immediate isolation pending vendor response, as the vulnerability is trivially exploitable and publicly documented.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict REST API network access to internal/allowlisted IPs only via firewall or WAF; (2) Disable REST API entirely if not required for operations; (3) Deploy network segmentation to isolate MiroFish from sensitive systems; (4) Implement continuous monitoring for suspicious API access patterns matching known exploit signatures.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Remote command injection in MiroFish versions up to 0.1.2 allows unauthenticated attackers to execute arbitrary system c
Path traversal in MiroFish up to version 0.1.2 allows remote unauthenticated attackers to read arbitrary files via manip
Information disclosure in MiroFish up to version 0.1.2 allows remote attackers to leak sensitive data through manipulati
EUVD-2026-25719
NVD
CVE.org
EPSS
Vulnrichment
GitHub
VulDB
Exploit-DB