Critical

CVE-2026-71187 — Ebyte NA111-M Use of Client-Side Authentication

The Ebyte device relies on client side authentication logic that can be reproduced by unauthenticated users. An attacker may generate valid authentication requests and bypass authentication to obtain administrative access to the device.

Published Aug 27, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: icscert

Low

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.

How the score was calculated

Technical severity (critical)+10
Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation

Not confirmed

Not in CISA KEV — an absence of record, not proof it is unexploited.

EPSS FIRST

—

No EPSS score.

Affects

Ebyte

Ebyte NA111-M Firmware

CVSS base

9.8

Critical · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation

None

none · proof-of-concept · active

Automatable

Yes

can an attacker script the kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

Identify exposed assets running the affected vendor/product/version combinations (Ebyte Ebyte NA111-M Firmware).
The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
No fix documented in the sources: reduce exposure and monitor the vendor advisory.
Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

Vendor	Product	Versions	Status	Source
Ebyte	Ebyte NA111-M Firmware	version 9013-2-17	Vulnerable	CVE Program (cve.org) e CISA ADP

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector

Network

Attack complexity

Low

Privileges required

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Scored by
9.3	CVSS 4.0	Critical	—	—	ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.3	CVSS 4.0	Critical	—	—	icscert via CVE Program (cve.org) e CISA ADP
9.8	CVSS 3.1	Critical	3.9	5.9	ics-cert@hq.dhs.gov via NIST National Vulnerability Database
9.8	CVSS 3.1	Critical	—	—	icscert via CVE Program (cve.org) e CISA ADP

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: ics-cert@hq.dhs.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-603

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).

web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

2026
Affected products added · ebyte/ebyte na111-m firmware
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
SSVC assessment updated
Oct 15, 2026 · CVE Program (cve.org) e CISA ADP
Record published
Oct 15, 2026
CVSS changed · 9.8
Oct 15, 2026 · NIST National Vulnerability Database
Source status changed · → Deferred
Oct 15, 2026 · NIST National Vulnerability Database
Record created in this database
Oct 15, 2026 · NIST National Vulnerability Database
CVE published
Aug 27, 2026 · icscert

Source activity

Repeated readings are counted rather than listed.

1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

2 on the record

github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-06.jso
NIST National Vulnerability Database
www.cisa.gov/news-events/ics-advisories/icsa-26-237-06
NIST National Vulnerability Database

Elsewhere on this site

Ebyte
every CVE for this vendor

CWE-603
other pages naming this weakness

Related CVEs (same products)

High CVE-2026-77966 Ebyte NA111-M Missing Authorization Aug 31, 2026
Critical CVE-2026-76133 Ebyte NA111-M Use of a Broken or Risky Cryptographic Algorithm Aug 31, 2026
Critical CVE-2026-73819 Ebyte NA111-M Weak Authentication Aug 31, 2026
High CVE-2026-76940 Ebyte NA111-M Improper Restriction of Excessive Authentication Attempts Aug 27, 2026
High CVE-2026-77977 Ebyte NA111-M Missing Authentication for Critical Function Aug 27, 2026
High CVE-2026-75814 Ebyte NA111-M Cross-Site Request Forgery Aug 27, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No FIRST EPSS score.
No fixed version, patch or mitigation documented.
No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-71187 is "Ebyte NA111-M Use of Client-Side Authentication", rated Critical. It affects Ebyte NA111-M Firmware (Ebyte); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.