Skip to main content
VulnerabilityPublished Updated

CVE-2026-7685: Edimax BR-6208AC · Buffer Overflow

Affects Edimax BR-6208ACSource CVE Database V5

0
Compare

Public exploit available · CVSS 8.7 High.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
EdimaxBR-6208ACAffected
  • =1.02
Fixed in–

AI-suggested

Since the vendor has not responded or released a fix, users should consider mitigating exposure by restricting remote access to the device management interface, disabling vulnerable services if possible, or replacing the device with a secure alternative until a patch is available.

Description

CVE-2026-7685 is a high-severity buffer overflow vulnerability in the Edimax BR-6208AC router firmware version 1.02. The flaw exists in an unknown function within the /goform/setWAN file, where manipulation of the pptpDfGateway argument can trigger the overflow. This vulnerability can be exploited remotely without user interaction or privileges. Although the exploit code is publicly available, there is no known exploit activity in the wild. The vendor has not responded or provided a patch or mitigation guidance as of the publication date.

References

Community reviews

Loading reviews…