Use of Hard-coded Credentials in Eufy Omni C20

Why this deserves its current priority

CVSS is 6.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Eufy/Omni C20 (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Eufy/Omni C20.
2. 2Review the reported fix. Source-reported solution: Eufy recommends users to upgrade to version 1.6.4 or later.

Evidence timeline and material changes

1. Published upstream

   Sep 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 24, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 25, 2026

Sources and claim methodology

• CISA Known Exploited Vulnerabilities catalogcisa.gov

Related CVEs

• Improper certificate validation in Eufy Omni C20Same eufy/omni c20 package
• Botslab G980H Dashcams Use of Hard-coded CredentialsAlso CWE-798
• CSS & JavaScript Toolbox <= 12.0.6 - Authenticated (Contributor+) Stored Cross-Site Scripting via cjtoolbox ShortcodeSame generic ecosystem
• Logic flaw in SANnav Java cache key handling object comparison handlingSame generic ecosystem
• Information exposure vulnerability in the job scheduling component of SANnav before 3.0.1aSame generic ecosystem
• Incomplete log sanitization during bulk IPsec policy collection in Brocade SANnav before 3.0.1aSame generic ecosystem