CVE-2026-7042
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA missing authentication vulnerability exists in the create_app function of the MiroFish REST API endpoint (backend/app/__init__.py). This allows remote unauthenticated attackers to manipulate application creation, as the endpoint does not verify user identity before processing requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the MiroFish REST API deploymentSearch your codebase or deployed services for files containing 'MiroFish' or 'backend/app/__init__.py' to confirm the product is in useAffected if The MiroFish REST API software is present in your environment
-
Identify the create_app endpointInspect backend/app/__init__.py and look for the create_app function definition and its route mapping (e.g., @app.route or @router.post for '/create_app' or similar)Affected if The create_app function exists and is exposed as an API endpoint
-
Check for authentication decorator on the endpointExamine the code immediately above the create_app function definition for authentication decorators such as @require_auth, @login_required, @token_required, or authentication middleware. Also check if the endpoint handler itself contains any auth verification logicAffected if No authentication decorator or auth verification logic is present before the create_app function
-
Test endpoint accessibility without credentialsSend an HTTP POST request to the create_app endpoint using a tool like curl or an HTTP client, omitting any authentication headers (Authorization, cookies, tokens). Example: curl -X POST http://<host>/api/create_app -H 'Content-Type: application/json' -d '{}'Affected if The request is accepted and processed without returning a 401 Unauthorized, 403 Forbidden, or authentication error response
-
Verify user identity is not validated in the handlerReview the create_app function body to confirm it does not call any user verification methods, session checks, or permission validation before processing the requestAffected if The function processes requests without any user identity or permission validation
You are affected if the MiroFish REST API is deployed with the create_app endpoint exposed and either no authentication is enforced or unauthenticated requests are accepted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization checks on the create_app endpoint, requiring valid credentials for all application creation requests, and validate user permissions before allowing any manipulation.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7042 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-7042 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data