VulnerabilityPublished 7 Mar 2026Updated 11 Mar 2026

CVE-2026-3668: Freedom Factory dGEN1 · Improper Access Controls

Affects Freedom Factory dGEN1Source CVE Database V5

Compare

Public exploit available · CVSS 2.3 Low.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

2.3Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: Low
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 7 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Freedom FactorydGEN1	Affected =20260221	Fixed in–

AI-suggested

Given the absence of official patches, organizations should implement compensating controls to mitigate CVE-2026-3668. These include restricting access to the affected AndroidEthereum function by enforcing strict access control policies and minimizing user interaction with untrusted sources that could trigger exploitation. Employing mobile device management (MDM) solutions to control application permissions and monitor suspicious activities can reduce risk. Educating users about phishing and social engineering tactics is critical to prevent the user interaction needed for exploitation. Network-level protections such as firewall rules and intrusion detection systems should be tuned to detect anomalous traffic related to the dGEN1 product. Organizations should also monitor Freedom Factory communications for any future patches or advisories and plan for timely updates. If feasible, consider isolating or limiting the use of the vulnerable component until a fix is available. Finally, conducting regular security assessments and penetration testing focused on blockchain-related components can help identify and remediate related weaknesses.

Description

A weakness has been identified in Freedom Factory dGEN1 up to 20260221. This affects the function AndroidEthereum of the component org.ethosmobile.webpwaemul. This manipulation causes improper access controls. Remote exploitation of the attack is possible. The attack is considered to have high complexity. The exploitability is reported as difficult. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The potential impact of CVE-2026-3668 is relatively limited due to its low CVSS score and high exploitation complexity. However, organizations using Freedom Factory dGEN1, especially those leveraging its Ethereum-related features on Android, could face unauthorized access or manipulation risks. This could lead to minor breaches of confidentiality or integrity within the affected component, potentially exposing sensitive blockchain transaction data or enabling unauthorized operations. Since the vulnerability requires user interaction, social engineering or phishing could be vectors for exploitation. The lack of vendor response and patches increases the risk exposure duration. While no widespread exploitation is currently known, the availability of public exploit code raises the possibility of targeted attacks, particularly against organizations involved in cryptocurrency or blockchain activities. Overall, the impact is low but non-negligible, warranting attention from affected users to prevent potential misuse.

Summary

CVE-2026-3668 identifies an improper access control vulnerability in the Freedom Factory dGEN1 product, specifically affecting the AndroidEthereum function of the org.ethosmobile.webpwaemul component. This flaw allows an attacker to remotely manipulate access controls, potentially bypassing intended restrictions. The vulnerability does not require authentication but does require user interaction, which limits the ease of exploitation. The attack complexity is high, indicating that a successful exploit demands significant skill or specific conditions. The CVSS 4.0 score of 2.3 reflects a low severity, primarily due to limited impact on confidentiality, integrity, and availability, and the difficulty of exploitation. Despite the low score, public exploit code has been released, increasing the risk of opportunistic attacks. The vendor has not issued any patches or responded to the disclosure, leaving users without an official remediation path. The vulnerability resides in a component related to Ethereum functionality on Android, which may be part of blockchain or cryptocurrency-related features within the product. Given the nature of the flaw, attackers could potentially gain unauthorized access or perform unauthorized actions within the affected component, but the overall impact remains constrained by the complexity and user interaction requirements.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Mar 2026, 19:22 UTC

Technical details

References

Community reviews

Related threats