dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-9346

HIGH · 8.8 CVSS v3.1 Published 2026-05-24
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 flaw has been found in Edimax EW-7438RPn up to 1.31. This impacts the function formWirelessTbl of the file /goform/formWirelessTbl of the component webs. Executing a manipulation of the argument submit-url can lead to buffer overflow. The attack may be performed from remote. The exploit has been published and may be used. 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 EW-7438RPn wireless range extender web interface (webs component). The formWirelessTbl function in /goform/formWirelessTbl fails to properly validate the submit-url parameter, allowing remote attackers to overflow a buffer via crafted input.

MitigationIsolate affected devices on restricted network segments; since vendor did not respond to disclosure, consider replacing device with a supported model. If continued use is required, disable remote web management and limit access to local admin only.

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. Identify the device model
    Access the device admin interface or check the device label to confirm the model is Edimax EW-7438RPn
    Affected if The device is an Edimax EW-7438RPn range extender
  2. Check the installed firmware version
    Log into the device web interface and navigate to System Settings or Status page to view the firmware version, or use the device's web API to retrieve version information
    Affected if The firmware version is 1.31 or any earlier version (the vulnerability affects firmware up to 1.31)
  3. Verify the web interface is accessible
    Attempt to access the device web interface via HTTP on the LAN IP address (default is often 192.168.1.1 or 192.168.2.1)
    Affected if The web management interface is exposed and responds to requests
  4. Confirm the vulnerable endpoint exists
    Check if the /goform/formWirelessTbl endpoint is present by accessing it via HTTP GET request to the device
    Affected if The /goform/formWirelessTbl endpoint responds, indicating the vulnerable web component is enabled

The environment is affected if you have an Edimax EW-7438RPn device running firmware version 1.31 or earlier with the web interface accessible and the /goform/formWirelessTbl endpoint present.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Isolate affected devices on restricted network segments; since vendor did not respond to disclosure, consider replacing device with a supported model. If continued use is required, disable remote web management and limit access to local admin only.

Recommended fix Moderate confidence
  1. This vulnerability is in the firmware of the Edimax EW-7438RPn wireless range extender.
  2. The vendor (Edimax) was contacted about this disclosure but did not respond in any way.
  3. There is no publicly available patch or firmware update for this vulnerability.
  4. As a mitigation, disable remote web management (HTTP/HTTPS) on the device if not needed, or restrict access to the web interface using firewall rules to only trusted IP addresses.
  5. Consider replacing the device with a newer model that receives active security support.
  6. If the device must remain in service, place it behind a NAT/firewall and ensure it is not directly exposed to the internet.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-9346 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