CVE-2026-108918

waiting for further signalsZero needs more public information before it can validate it.

GHSA-x6qv-gj4w-78gc ↗EUVD-2026-97738 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
edimax BR-6208AC 1.32
ETK-2026-1401Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 09h 52msince last run
13mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h57m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Edimax BR-6208AC firmware version 1.32 is affected by command injection in a web-management handler. An attacker may execute commands if they can reach the affected interface remotely; the device line is no longer supported.

mitigation

Remove affected devices from service or replace them with supported hardware. Until replacement, block access to the management interface from untrusted networks and limit administration to a segregated trusted network.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
2.0%80th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 18:00Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-12 18:00Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 18:00Z

this entry in the feed

GET /api/v1/feed/CVE-2026-108918

{
  "etk_id": "ETK-2026-1401",
  "cve_id": "CVE-2026-108918",
  "display_id": "CVE-2026-108918",
  "ghsa_id": "GHSA-x6qv-gj4w-78gc",
  "euvd_id": "EUVD-2026-97738",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Command injection in Edimax BR-6208AC",
  "summary": "Edimax BR-6208AC firmware version 1.32 is affected by command injection in a web-management handler. An attacker may execute commands if they can reach the affected interface remotely; the device line is no longer supported.",
  "mitigation": "Remove affected devices from service or replace them with supported hardware. Until replacement, block access to the management interface from untrusted networks and limit administration to a segregated trusted network.",
  "vendor": "edimax",
  "product": "BR-6208AC",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.32"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "BR-6208AC",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": 0.0203,
  "epss_percentile": 0.8075,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.559529366666666,
  "t0_at": "2026-10-12T18:00:18.352000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T18:00:18.352000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T18:00:18.352000+00:00",
      "url": "https://github.com/advisories/GHSA-x6qv-gj4w-78gc"
    }
  }
}

published 2026-10-12 18:45Z
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.