A vulnerability was determined in Edimax BR-6208AC 1.32. This issue affects some unknown processing of the file /goform/formAutoFWupgrade. Executing a manipulation of the argument tftpsIP can lead to command injection. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.
CVE-2026-108917
CRITICALPre-NVD 10.010.0Trending — 5 sources updated this weekElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-12. A secondary CVSS source baseline 10.0; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 2.0%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed
A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).
- CVSS v3
- 10.0
- EG Score
- 10.0CRITICALhigh confidence
- EG Risk
- 76EG Risk 76/100
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 computed (value × EchelonGraph’s weight)Severity100% × 45%The EG Score, 10.0 of 10.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation. - EPSS PROB
- 2.0%
- EPSS %ILE
- 80th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 12, 2026
Last Modified
October 13, 2026
Advisory Details (1)
Auto-updated Oct 14, 2026Fix referenced — no release confirmed yet.
Web page
Iot_vuls/BR-6208AC/RCE_formAutoFWupgrade at main · fizz-is-on-the-way/Iot_vuls · GitHub
https://github.com/fizz-is-on-the-way/Iot_vuls/tree/main/BR-6208AC/RCE_formAutoFWupgradeVendor Advisories for CVE-2026-108917(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 15× in last 7d / 15× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-13 17:25 UTCEG score recompute
- 2026-10-13 17:25 UTCGHSA enrichmentGHSA-jm9w-v357-jj5j · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 17:25 UTCNVD updateCVSS v4 → 9.3
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 2.0% · 80th percentile
- 2026-10-13 16:32 UTCEG score recompute
- 2026-10-13 16:32 UTCGHSA enrichmentGHSA-jm9w-v357-jj5j · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 16:23 UTCEG score recompute
- 2026-10-13 16:23 UTCGHSA enrichmentGHSA-jm9w-v357-jj5j · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-13 16:19 UTCMITRE cvelistV5CVSS v4 → 10
- 2026-10-13 13:46 UTCEG score recompute
- 2026-10-13 13:45 UTCGHSA enrichmentGHSA-jm9w-v357-jj5j · GitHub severity CRITICAL · GitHub CVSS 10.0
- 2026-10-12 18:26 UTCEG score recompute
- 2026-10-12 18:24 UTCNVD updateCVSS v4 → 9.3
- 2026-10-12 17:55 UTCEG score recomputeFirst assessed: 10.0 CRITICAL
- 2026-10-12 17:55 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-74 · CWE-77
Frequently asked(5)
What is CVE-2026-108917?
CVE-2026-108917 is a critical-severity vulnerability; its CVE record was published on October 12, 2026. A vulnerability was determined in Edimax BR-6208AC 1.32. This issue affects some unknown processing of the file /goform/formAutoFWupgrade. Executing a manipulation of the argument tftpsIP can lead to command injection. The attack may be performed from remote. The exploit has been publicly disclosed…
When was the CVE record for CVE-2026-108917 published?
The CVE record for CVE-2026-108917 was published on October 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 13, 2026; the record at its source may have been updated since.
Is CVE-2026-108917 actively exploited?
CVE-2026-108917 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.0% probability of exploitation in the next 30 days (80th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-108917?
CVE-2026-108917 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-108917?
A fix for CVE-2026-108917 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-108917 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-108917
Is Your Infrastructure Affected by CVE-2026-108917?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.