Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
Check your stack
CVE-2026-93290medium6.8

Use of Hard-coded Credentials in Eufy Omni C20

Impact

Omni C20 uses hard-coded credentials that could allow an attacker to monitor log files to obtain credentials to access information like mapping data.

Source excerpt · icscert

What to do

Eufy recommends users to upgrade to version 1.4.6 or later for Omni C2.

icscert guidance

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

Eufy · icscert

Omni C20

2 ranges

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 1.4.6

custom versions

unaffected

1.4.6

unknown

Other versions: unaffected

Original source description

Omni C20 uses hard-coded credentials that could allow an attacker to monitor log files to obtain credentials to access information like mapping data.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-93290

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-798 ↗

CWE-798 Use of Hard-coded Credentials

icscert

Related →
Contributing organizations · 2
icscert

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-09-24

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources