dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-3667

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

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 · unedited
A security flaw has been discovered in Freedom Factory dGEN1 up to 20260221. The impacted element is the function FakeAppService of the component org.ethosmobile.ethoslauncher. The manipulation results in improper authorization. The attack must be initiated from a local position. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

A local authorization vulnerability exists in the FakeAppService function of the org.ethosmobile.ethoslauncher component in Freedom Factory dGEN1 Android application. The improper authorization flaw allows a local attacker to potentially access or manipulate functionality they should not have access to. A public exploit is available, increasing the risk of active attacks.

MitigationImplement proper authorization checks within the FakeAppService function to validate user permissions before allowing access to protected operations. Since the vendor has not responded, consider alternative mitigation such as restricting app permissions or using mobile device management (MDM) solutions to control access until an official patch is available.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if the vulnerable app is installed
    Use Android package manager: 'pm list packages | grep ethosmobile' or check app settings for org.ethosmobile.ethoslauncher
    Affected if The package org.ethosmobile.ethoslauncher is installed on the device
  2. Determine the installed application version
    Check app version in Android Settings > Apps > ethoslauncher, or use 'dumpsys package org.ethosmobile.ethoslauncher' to retrieve versionInfo
    Affected if The installed version cannot be determined or falls within any vulnerable version range (compare to known affected versions if available)
  3. Check if FakeAppService component is exported
    Analyze the AndroidManifest.xml or use 'dumpsys package org.ethosmobile.ethoslauncher' to check if FakeAppService has android:exported=true
    Affected if FakeAppService is exported and accessible to other apps or untrusted callers
  4. Verify authorization behavior of FakeAppService
    Attempt to interact with the FakeAppService component via ADB or intent inspection to observe if authorization checks are properly enforced
    Affected if The component allows access or returns sensitive data without requiring proper authentication/authorization
  5. Audit app permissions and component exposure
    Review app permissions and exported components using 'pm dump org.ethosmobile.ethoslauncher' or security scanning tools
    Affected if The app has overly permissive components or FakeAppService lacks proper permission requirements

A user is affected if the org.ethosmobile.ethoslauncher app is installed and the FakeAppService component is exposed without proper authorization checks, allowing unauthorized access to protected functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization checks within the FakeAppService function to validate user permissions before allowing access to protected operations. Since the vendor has not responded, consider alternative mitigation such as restricting app permissions or using mobile device management (MDM) solutions to control access until an official patch is available.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3667 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3667 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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