dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-9425

HIGH · 8.8 CVSS v3.1 Published 2026-05-25
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 vulnerability has been detected in Edimax EW-7438RPn 1.31. The impacted element is the function formWlanMP of the file /goform/formWlanMP. The manipulation of the argument ateFunc/ateGain/ateTxCount/ateChan/ateRate/ateMacID/e2pTxPower1/e2pTxPower2/e2pTxPower3/e2pTxPower4/e2pTxPower5/e2pTxPower6/e2pTxPower7/e2pTx2Power1/e2pTx2Power2/e2pTx2Power3/e2pTx2Power4/e2pTx2Power5/e2pTx2Power6/e2pTx2Power7/ateTxFreqOffset/ateMode/ateBW/ateAntenna/e2pTxFreqOffset/e2pTxPwDeltaB/e2pTxPwDeltaG/e2pTxPwDeltaMix/e2pTxPwDeltaN/readE2P leads to stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed publicly 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 · high confidence

Stack-based buffer overflow in Edimax EW-7438RPn v1.31 web interface (formWlanMP function in /goform/formWlanMP). Multiple parameters including ateFunc, ateGain, e2pTxPower1-7, and others accept excessive input that overflows a fixed-size buffer on the stack. Exploitable remotely without authentication, allowing arbitrary code execution.

MitigationNetwork-level mitigations (firewall rules blocking access to the web interface, network segmentation) are the primary option since the vendor did not respond and no firmware update is expected. Consider replacing the end-of-life device with a supported model.

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 device model
    Access the device's web administration interface or check the device label/metadata to confirm the model is Edimax EW-7438RPn
    Affected if Device is not an Edimax EW-7438RPn model
  2. Check firmware version
    Log into the web interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version; compare against v1.31
    Affected if Firmware version is 1.31 or earlier
  3. Verify web interface is enabled
    Confirm the device's HTTP/HTTPS management interface is active by attempting to access the device's IP address from the local network
    Affected if Web interface is disabled or not accessible
  4. Confirm formWlanMP function exists
    Access the web interface and navigate to wireless settings or examine the HTML forms to identify if a formWlanMP or similar wireless management function is present and accessible
    Affected if The formWlanMP web form function is not present or not accessible
  5. Check network exposure
    Determine if the device's web management port is exposed to untrusted networks by reviewing firewall rules or NAT configurations
    Affected if Web interface is directly accessible from untrusted networks (e.g., WAN/internet)

The environment is affected if it is an Edimax EW-7438RPn device running firmware v1.31 (or earlier) with the web management interface and formWlanMP function accessible, especially from untrusted networks.

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

Network-level mitigations (firewall rules blocking access to the web interface, network segmentation) are the primary option since the vendor did not respond and no firmware update is expected. Consider replacing the end-of-life device with a supported model.

Recommended fix Moderate confidence
  1. This vulnerability affects Edimax EW-7438RPn version 1.31, a legacy wireless range extender that is likely end-of-life and no longer supported by the vendor.
  2. The vendor was contacted but did not respond, indicating no official patch or firmware update will be provided.
  3. As this is a hardware device with a stack-based buffer overflow vulnerability, user-configurable mitigations within the device firmware are not available.
  4. If the device cannot be retired or replaced, network-level mitigations such as restricting access to the device's management interface to trusted IPs only, or placing the device in an isolated network segment, may reduce exposure but do not eliminate the vulnerability.
  5. Consider migrating to a supported, actively maintained wireless networking solution.

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-9425 — 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-9425 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