Skip to content
IoT

CVE-2026-77966

8.7
High
EPSS 0.44%Sep 1, 2026

Authenticated low-privilege users can access admin functions on Ebyte devices.

common questions

Is CVE-2026-77966 being exploited?

Not confirmed. CVE-2026-77966 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2026-77966?

CVE-2026-77966 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77966?

Not known from our data. No patch reference has been recorded for CVE-2026-77966, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-77966 affect?

CVE-2026-77966 affects Ebyte wireless modules, Ebyte device management interfaces, Embedded IoT devices using Ebyte modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77966?

Restrict management access, enforce RBAC, apply vendor firmware updates when released, monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Ebyte wireless modulesEbyte device management interfacesEmbedded IoT devices using Ebyte modules
impact

Low-privileged authenticated attacker can escalate privileges to admin, change security settings, compromise confidentiality/integrity/availability, enable lateral movement or device disruption.

action required

Immediate action required

affected versions
Ebyte Ebyte NA111-M Firmware
  • affected9013-2-17

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free