CVE-2026-9401
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 · uneditedA vulnerability has been found in Edimax BR-6675nD 1.12. Impacted is the function formWanTcpipSetup of the file /goform/formWanTcpipSetup of the component POST Request Handler. The manipulation of the argument pppUserName leads to buffer overflow. The attack can be initiated remotely. The exploit has been disclosed to the public 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 confidenceBuffer overflow vulnerability in Edimax BR-6675nD router firmware version 1.12 in the POST request handler for WAN TCP/IP settings. The pppUserName parameter in the /goform/formWanTcpipSetup form is not properly bounds-checked, allowing remote attackers to overflow a buffer and potentially execute arbitrary code.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Edimax BR-6675nDAccess the router's web admin interface and check the device information page, or check the device label/markings for the model number BR-6675nDAffected if The device is not an Edimax BR-6675nD router - if it is a different model, this specific CVE does not apply
-
Check firmware version is 1.12In the router web interface, navigate to Status or System Info page and locate the firmware version field. Compare the displayed version to 1.12Affected if The firmware version is exactly 1.12 - other versions may have different vulnerabilities or may have fixed this issue
-
Verify web administrative interface is accessibleAttempt to access the router's IP address on ports 80 or 443 from the network segment you are checking. Confirm the /goform/formWanTcpipSetup endpoint responds to HTTP requestsAffected if The web interface is accessible on the network and the vulnerable endpoint responds to requests - this is required for exploitation
-
Check if remote administrative access is enabledIn the router web interface under Administration or Remote Management settings, determine if remote access to the web interface is permitted from external IP addressesAffected if Remote management/remote access to the admin web interface is enabled - this increases exposure since the vulnerability is remotely exploitable
You are affected if you are running an Edimax BR-6675nD router with firmware version 1.12 that has its web administrative interface accessible, especially if remote management is enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataThis is a legacy consumer router that appears unpatched since the vendor did not respond to disclosure. Recommended remediation is to replace the device with a currently supported router. If replacement is not feasible, implement network segmentation and external firewall rules to restrict access to the router's web management interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9401 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-9401 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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