Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-3674

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

NVD · unedited

A vulnerability was found in Freedom Factory dGEN1 up to 20260221. Affected by this vulnerability is the function FakeAppProvider of the component org.ethosmobile.ethoslauncher. Performing a manipulation results in improper authorization. The attack must be initiated from a local position. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary

dbcve analysis · moderate confidence

The FakeAppProvider function in the org.ethosmobile.ethoslauncher component of the Freedom Factory dGEN1 mobile application suffers from improper authorization, allowing a local attacker to perform actions they should not be permitted to execute. The vulnerability has been publicly disclosed and can be exploited without remote network access.

MitigationSince the vendor did not respond to disclosure, apply compensating controls such as restricting device physical access, deploying alternative secure launchers, or implementing application-level authorization checks at the OS layer if available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown

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?

dbcve checks

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

Identify if the Freedom Factory dGEN1 app is installed

List installed packages on the Android device using 'adb shell pm list packages | grep -i ethos' or 'adb shell pm list packages | grep -i dgen' or 'adb shell pm list packages | grep -i freedom'

Affected if The package for the Freedom Factory dGEN1 application (containing org.ethosmobile.ethoslauncher) is present on the device
Verify the ethOS Launcher component exists

Run 'adb shell pm list packages' to find the full package name, then check for the component using 'adb shell dumpsys package <package_name>' and look for org.ethosmobile.ethoslauncher

Affected if The org.ethosmobile.ethoslauncher component is present in the installed application
Check if FakeAppProvider is exported

Use 'adb shell dumpsys package <package_name>' and examine the exported providers, or use 'adb shell pm dump <package_name> | grep -A 10 FakeAppProvider' to see if the provider has android:exported=true

Affected if FakeAppProvider component is exported (android:exported=true) allowing other apps or unauthorized users to access it
Determine application version

Run 'adb shell pm dump <package_name> | grep versionName' or check the app info in Settings > Apps > [App Name] to obtain the installed version number

Affected if The installed version cannot be determined as patched or is older than any available fixed version (contact vendor for version details)
Assess device physical access controls

Verify the device is not left unlocked, unattended, or in an environment with untrusted physical access. Check if 'Screen lock' is enabled in Settings > Security

Affected if The device has weak physical access controls, making local exploitation feasible

A user is affected if the Freedom Factory dGEN1 app with the org.ethosmobile.ethoslauncher component is installed and the FakeAppProvider is exported, especially on devices with insufficient physical access controls.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Since the vendor did not respond to disclosure, apply compensating controls such as restricting device physical access, deploying alternative secure launchers, or implementing application-level authorization checks at the OS layer if available.

Have this fixed Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA3.0 h

21.0 hours of engineering $3,680

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-3674 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-3674?

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.

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

At a glance

A fix existsA vendor remedy is published

Severity 5.3 Medium

Exploit likelihood EPSS, next 30 days 0.1%

Remediation

Need this fixed?

Have this fixed 21 hrs · Moderate

Typical engagement from $3,680

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2026-3674 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References