Skip to main content
VulnerabilityPublished Updated

CVE-2026-93290: Eufy Omni C20 · Use of Hard-coded Credentials

Affects Eufy Omni C20Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.4.6 when convenient.

Data as of 8 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (icscert)CVSS 4.06.8
CNA (icscert)CVSS 3.15.5
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.4.6
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.

What to do

Upgrade Eufy Omni C20 to 1.4.6.

Affected software

ProductAffectedFixed in
EufyOmni C20Affected
  • <1.4.6
Fixed in
  • 1.4.6

AI-suggested

Upgrade the Eufy Omni C20 device firmware to version 1.4.6 or later, where the hard-coded credentials vulnerability has been fixed. No other specific mitigations are indicated.

Description

The Eufy Omni C20 device contains a vulnerability due to the use of hard-coded credentials. This flaw could allow an attacker with local access to monitor log files and extract these credentials, potentially gaining unauthorized access to sensitive information such as mapping data. The vulnerability affects versions prior to 1.4.6. A fix is available in version 1.4.6.

References

Community reviews

Loading reviews…