CVE-2026-10188
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 W12 3.0.0.7(4763). This affects the function cgistaKickOff of the file /bin/httpd. Executing a manipulation of the argument staMac can lead to stack-based buffer overflow. The attack may be performed from remote. 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 · moderate confidenceStack-based buffer overflow in the cgistaKickOff function of the Tenda W12 router httpd web server. The staMac parameter passed to this function is not properly bounds-checked before being copied to a stack buffer, allowing remote attackers to overwrite return addresses 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.
-
Identify device modelAccess the router web interface or check the device label to confirm it is a Tenda W12 routerAffected if Device is not a Tenda W12 router (not affected)
-
Check firmware versionLog into the router web interface and navigate to System Settings or Administration to view the firmware version. Alternatively, check via CLI if available or inspect the firmware binary fileAffected if Firmware version is within the affected range and has not been patched
-
Verify httpd service accessibilityAttempt to access the router's web interface from LAN (e.g., http://192.168.0.1) to confirm the httpd service is running and respondingAffected if httpd service is not running (reduced attack surface but vulnerability may still exist in code)
-
Check WAN remote administration settingsIn the router web interface, go to Advanced Settings or Administration and check if 'Remote Management' or 'WAN Access' is enabled for the httpd serviceAffected if Remote management via WAN is enabled, exposing the vulnerable httpd service to the internet
-
Review access logs for exploitation attemptsCheck router logs (if available) or network firewall logs for suspicious requests to the httpd interface, especially those containing unusually long staMac parameter valuesAffected if Logs show requests with oversized staMac values or signs of attempted exploitation
A user is affected if they own a Tenda W12 router running a vulnerable firmware version with the httpd web server exposed, particularly if remote WAN administration 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 dataApply vendor firmware update when available. Until then, disable remote web management and restrict network access to the router's administration interface from untrusted networks.
- Consultation4.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10188 — 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-10188 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