CVE-2026-19961

The CVSS 9.9 score for this buffer overflow in Edimax's WiFi scanning handler (/goform/formWlSiteSurvey) is technically accurate but practically misleading. It implies a remediation pathway that almost certainly doesn't exist — Edimax has no public patch history for this class of vulnerability, and second-tier consumer router vendors rarely patch at all. The handler processes WiFi survey requests on the device's web management interface. This is C code handling form input without bounds checking, running on a gateway device that sits at the network edge. The blast radius isn't the overflow itself — it's the pivot point. Compromising this handler gives attackers a foothold on the local network segment, from which they can reach whatever sits behind the router: internal services, IoT devices, workstations. What matters for defenders: segment these devices assume they will never receive a patch. Treat the management interface as hostile by default — it should never be exposed to the internet, and even internal access should be isolated to a dedicated VLAN. Monitor for unusual DNS patterns, unexpected outbound connections, or device behavior changes that would indicate compromise. The buffer overflow likely exists because the code was ported from a reference design and never audited — this is standard practice in this vendor tier, not an anomaly. If you manage Edimax devices, the operational reality is that your device is now permanent infrastructure with a known remote vector and no厂家 fix coming. The question isn't whether to patch — it's whether to continue operating an unpatchable gateway at all.

Reviewed through automated stages and approved by a human before publication.