An improper protection of authentication tokens vulnerability exists in certain Ebyte gateway products. Authentication tokens used by the web management interface are insufficiently protected during client-side session handling, which may allow an attacker with access to exposed session information to obtain and reuse a valid token. Successful exploitation could allow an attacker to impersonate an authenticated user and gain unauthorized access to device management functionality.
CVE-2026-76179
Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-28. a secondary CVSS source baseline 9.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.8
- EG Score
- 9.8(high)
- EG Risk
- 59(Track)EG Risk 59/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity98% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 36%
- KEV
- Not listed
Published
August 27, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 28, 2026Ebyte NE2-D11 | CISA
https://www.cisa.gov/news-events/ics-advisories/icsa-26-237-06CSAF/csaf_files/OT/white/2026/icsa-26-237-06.json at develop · cisagov/CSAF · GitHub
https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-06.jsonVendor Advisories for CVE-2026-76179(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 04:23 UTCEG score recompute
- 2026-08-30 04:23 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-30 00:18 UTCGHSA enrichment
- 2026-08-29 20:15 UTCGHSA enrichment
- 2026-08-29 16:12 UTCGHSA enrichment
- 2026-08-29 12:06 UTCGHSA enrichment
- 2026-08-29 08:00 UTCGHSA enrichment
- 2026-08-29 03:57 UTCGHSA enrichment
- 2026-08-28 23:52 UTCEG score recompute
- 2026-08-28 23:52 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 16:39 UTCEG score recompute
- 2026-08-28 16:39 UTCGHSA enrichment
- 2026-08-28 15:39 UTCEG score recompute
- 2026-08-28 15:39 UTCGHSA enrichment
- 2026-08-28 12:46 UTCGHSA enrichment
- 2026-08-28 08:41 UTCGHSA enrichment
- 2026-08-28 04:35 UTCEG score recompute
- 2026-08-28 04:35 UTCGHSA enrichment
- 2026-08-28 00:31 UTCEG score recompute
- 2026-08-27 23:23 UTCEG score recompute
- 2026-08-27 23:22 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-76179?
When was CVE-2026-76179 disclosed?
Is CVE-2026-76179 actively exploited?
What is the CVSS score of CVE-2026-76179?
How do I remediate CVE-2026-76179?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-76179
Is Your Infrastructure Affected by CVE-2026-76179?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.