CVE-2025-9089
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 was determined in Tenda AC20 16.03.08.12. This issue affects the function sub_48E628 of the file /goform/SetIpMacBind. The manipulation of the argument list leads to stack-based buffer overflow. The attack may be initiated remotely. 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 · high confidenceStack-based buffer overflow in Tenda AC20 router firmware 16.03.08.12 within the /goform/SetIpMacBind function. The vulnerability exists in argument parsing for the 'list' parameter in function sub_48E628, allowing remote attackers to overflow a stack buffer and potentially execute arbitrary code. The CVSS 9.8 score indicates trivial network exploitation with no authentication required.
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.08.12CVSS 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 Tenda AC20 firmware versionAccess the router's web management interface (typically at 192.168.0.1) and navigate to the System Status or Firmware Version page. Alternatively, check via telnet/SSH console using 'cat /etc/version' or '固件版本' command if available.Affected if The displayed firmware version is exactly 16.03.08.12
-
Confirm the vulnerable endpoint existsMake an HTTP GET or POST request to http://<router-ip>/goform/SetIpMacBind. This endpoint handles IP-MAC binding functionality and is present in the vulnerable firmware version.Affected if The router responds to requests at /goform/SetIpMacBind (the handler exists in the firmware)
-
Verify the IP-MAC binding feature is accessibleCheck if the IP-MAC binding feature is enabled in the router's web interface under Advanced Settings or Security settings. The vulnerability triggers when manipulating argument lists sent to this handler.Affected if The IP-MAC binding feature is present and accessible on the management interface
You are affected if your Tenda AC20 router runs firmware version 16.03.08.12 and the /goform/SetIpMacBind endpoint is accessible.
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 dataSince Tenda AC20 is end-of-life with no vendor patch available, immediate mitigation requires network isolation (restrict management interface to trusted IPs or VPN), disable the IP/MAC binding feature if unused, and plan for hardware replacement with a supported device. No CVE-side fix is available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-9089 — 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-2025-9089 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