Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-9295

HIGH · 8.8 CVSS v3.1 Published 2026-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in Edimax BR-6428NS 1.10. This affects the function formWirelessTbl of the file /goform/formWirelessTbl of the component POST Request Handler. Performing a manipulation of the argument vapurl results in buffer overflow. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in Edimax BR-6428NS v1.10 router's web interface POST handler. The formWirelessTbl function in /goform/formWirelessTbl fails to properly validate the vapurl parameter length before copying it to a fixed-size buffer, allowing remote attackers to overflow the buffer and potentially execute arbitrary code via crafted HTTP POST requests.

MitigationIf available, apply vendor firmware update; otherwise, disable or restrict access to the router's web management interface from untrusted networks, or consider replacing the end-of-life device.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Edimax BR-6428NS
    Check the router label or log into the web admin interface and look for the model number in the status or system information page
    Affected if The device is NOT an Edimax BR-6428NS router - you are not affected
  2. Identify the installed firmware version
    Log into the router web interface and navigate to Status or System > Firmware Version to view the running firmware
    Affected if The firmware version is 1.10 (the affected version) or if you are unable to determine the version and the device is a BR-6428NS, treat as potentially affected
  3. Verify the web management interface is accessible
    Attempt to access the router at its local IP address (typically 192.168.2.1) via HTTP on port 80
    Affected if The web interface is NOT accessible - the vulnerable POST handler cannot be reached from your current network position
  4. Confirm the vulnerable endpoint exists
    Send a POST request to http://[router-ip]/goform/formWirelessTbl with a minimal payload or check if the URL returns a response (authentication may be required)
    Affected if The /goform/formWirelessTbl endpoint does not exist or is not reachable - the specific vulnerable path is not present
  5. Check if the administrative interface is network-exposed
    Determine if the router web interface is accessible from untrusted networks (internet-facing WAN IP, port forwarded, or DMZ)
    Affected if The admin interface is ONLY accessible from a trusted LAN - the attack surface is reduced though the vulnerability still exists in firmware

You are affected if you own an Edimax BR-6428NS router running firmware version 1.10 with its web administrative interface accessible to the network where an attacker could send a crafted POST request to /goform/formWirelessTbl with an oversized vapurl parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

If available, apply vendor firmware update; otherwise, disable or restrict access to the router's web management interface from untrusted networks, or consider replacing the end-of-life device.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-9295 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data