CVE-2026-1420
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 flaw has been found in Tenda AC23 16.03.07.52. This impacts an unknown function of the file /goform/WifiExtraSet. This manipulation of the argument wpapsk_crypto causes buffer overflow. Remote exploitation of the attack is possible. The exploit has been published 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 · high confidenceA critical buffer overflow vulnerability exists in Tenda AC23 firmware 16.03.07.52 within the /goform/WifiExtraSet function. The wpapsk_crypto parameter is not properly bounds-checked before use, allowing an attacker to overwrite adjacent memory. Given the CVSS 9.8 and remote exploitability, unauthenticated attackers can likely achieve remote code execution on the affected router.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 16.03.07.52CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 modelLog into the router admin panel or check the physical device label to confirm the model is Tenda AC23Affected if The device is not a Tenda AC23 router, then this CVE does not apply
-
Check the firmware versionNavigate to the router admin panel (typically at 192.168.0.1), look under System Settings, Firmware Upgrade, or Status page to find the installed firmware version. Alternatively, check via command line if you have telnet/ssh accessAffected if The firmware version is exactly 16.03.07.52 - this is the only affected version listed for this CVE
-
Verify the web management interface is accessibleAttempt to access the router login page from both LAN and WAN IP addresses using HTTP (port 80) or HTTPS (port 443)Affected if The router web interface responds to requests, indicating the vulnerable /goform/WifiExtraSet function is potentially reachable
-
Check WAN accessibility of the admin interfaceFrom an external network, attempt to reach the router's public IP on port 80/443, or check the router settings under Remote Management or Access Control to see if WAN web management is enabledAffected if The router admin interface is exposed to the WAN/Internet side, making it remotely exploitable by unauthenticated attackers
You are affected if you have a Tenda AC23 router running firmware version 16.03.07.52 with the web management interface accessible, especially if exposed to WAN.
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 dataApply the vendor firmware patch when available. As an interim control, disable the router's web management interface from the WAN/Internet side and restrict access to trusted IP addresses only.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1420 — 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-1420 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