CVE-2026-10163
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-6478AC 1.23. This issue affects the function formUSBAccount of the file /goform/formUSBAccount of the component POST Request Handler. The manipulation of the argument UserName/Password leads to buffer overflow. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.
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 confidenceA buffer overflow vulnerability exists in the POST request handler for the formUSBAccount function in Edimax BR-6478AC v1.23 firmware. The UserName and Password parameters submitted via POST to /goform/formUSBAccount are not properly bounds-checked before being copied into fixed-size buffers, allowing remote attackers to overflow the buffer with excessive input.
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.
-
Identify the router modelAccess the router web admin interface (typically at 192.168.1.1) and check the device model/model number, or check the device label on the hardware itselfAffected if The device is an Edimax BR-6478AC router
-
Check the firmware versionIn the router web interface, navigate to System Settings or Administration > Firmware Upgrade to view the current firmware versionAffected if The firmware version is 1.23 (the only version listed as affected)
-
Confirm web interface accessibilityAttempt to access the router login page via HTTP on the LAN IP address (default 192.168.1.1)Affected if The administrative web interface is accessible and responds to requests
-
Check USB sharing statusIn the router web interface, locate USB/Storage settings (often under USB/Applications or Storage settings) and check if USB storage or sharing features are enabledAffected if USB storage sharing features are enabled and the formUSBAccount function is accessible
All four conditions must be true: the device is an Edimax BR-6478AC, running firmware version 1.23, with the web administrative interface accessible, and with USB sharing features 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 dataRestrict access to the router's web management interface from untrusted networks, disable remote administration if enabled, and contact Edimax for an official firmware patch to address the input validation failure.
- Consultation4.0 h
- Implementation16.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10163 — 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-10163 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