CVE-2026-108917
waiting for further signalsZero needs more public information before it can validate it.GHSA-jm9w-v357-jj5j ↗EUVD-2026-97732 ↗
description
Edimax BR-6208AC version 1.32 is affected by command injection in firmware-upgrade request processing. A remote attacker able to reach the affected management functionality may be able to execute commands on the device; the evidence does not establish whether authentication is required.
mitigation
Retire and replace affected BR-6208AC devices with supported equipment, as no fixed version is recorded. Until replacement, restrict management access to trusted administrators and isolate the device from untrusted networks.
outcome
Contextual: an exploit technique exists, but no deterministic check could cover this one.
source signals
Public signals that triggered or updated the pipeline. These are inputs for the deltas above.
- 2026-10-12 17:45Zcve_org: trigger signal, started the run
- 2026-10-12 18:37Zfizz-is-on-the-way/Iot_vuls
this entry in the feed
GET /api/v1/feed/CVE-2026-108917
{ "etk_id": "ETK-2026-1396", "cve_id": "CVE-2026-108917", "display_id": "CVE-2026-108917", "ghsa_id": "GHSA-jm9w-v357-jj5j", "euvd_id": "EUVD-2026-97732", "status": "published", "anchor_state": "anchored", "title": "Command injection in Edimax BR-6208AC firmware upgrade handling", "summary": "Edimax BR-6208AC version 1.32 is affected by command injection in firmware-upgrade request processing. A remote attacker able to reach the affected management functionality may be able to execute commands on the device; the evidence does not establish whether authentication is required.", "mitigation": "Retire and replace affected BR-6208AC devices with supported equipment, as no fixed version is recorded. Until replacement, restrict management access to trusted administrators and isolate the device from untrusted networks.", "vendor": "Edimax", "product": "BR-6208AC", "affected": [ { "affected_notes": [], "affected_ranges": [ "1.32" ], "ecosystem": null, "fixed_versions": [], "package_name": "BR-6208AC", "purl": null } ], "cwes": [ 77 ], "cvss_score": 10, "cvss_src": "cna_vendor", "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P", "epss_score": 0.0199, "epss_percentile": 0.8037, "epss_asof": "2026-10-20", "automation": "contextual", "check": false, "check_confidence_basis": null, "exploit": false, "pipeline_minutes": 11.1451462, "t0_at": "2026-10-12T17:45:15.881000+00:00", "signals": { "public_poc": { "at": "2025-04-02T07:53:04+00:00", "days": -558.4112486226852, "is_lower_bound": false, "measured_at": "2026-10-12T17:45:15.881000+00:00", "url": "https://github.com/fizz-is-on-the-way/Iot_vuls" }, "trigger_signal": { "at": "2026-10-12T17:45:15.881000+00:00", "days": 0, "is_lower_bound": false, "measured_at": "2026-10-12T17:45:15.881000+00:00", "url": "https://www.cve.org/CVERecord?id=CVE-2026-108917" } } }
published 2026-10-12 18:09Z
last change 2026-10-21 04:45Z
Need the technical details behind an entry?
Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.