CVE-2026-10192
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 identified in Tenda W12 3.0.0.7(4763). The affected element is the function set_local_time_0 of the file /bin/httpd. Such manipulation of the argument Time leads to stack-based buffer overflow. The attack can be launched remotely. The exploit is publicly available and might 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 stack-based buffer overflow vulnerability exists in Tenda W12 router firmware version 3.0.0.7(4763) within the set_local_time_0 function in /bin/httpd. By manipulating the Time argument, an attacker can overflow a stack-based buffer, potentially achieving remote code execution.
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's web admin interface or check the device label to confirm it is a Tenda W12 modelAffected if The device is not a Tenda W12 router (this CVE does not apply)
-
Check the firmware versionLog into the router's web interface and navigate to System Settings or Firmware Upgrade page to view the current firmware version, or use telnet/SSH to access the device and run 'cat /proc/version' or check /etc/versionAffected if The firmware version is 3.0.0.7(4763) exactly, or falls within the affected range if additional versions are known
-
Verify the httpd service is runningAccess the router via telnet/SSH and run 'ps | grep httpd' or 'ps aux | grep httpd' to confirm the httpd process is activeAffected if The httpd process is not running (the vulnerable code path is not active)
-
Check if the web interface is exposed to remote accessReview router firewall settings to determine if ports 80 and 443 are accessible from WAN/internet, or run an external port scan against the router's public IP address on ports 80/443Affected if The router's web interface (port 80/443) is exposed to the internet, allowing remote attackers to reach the vulnerable function
-
Confirm the set_local_time_0 function exists in httpdIf you can extract the firmware, use binwalk to extract and then strings/grep to search for 'set_local_time_0' in the httpd binary, or check router filesystem at /bin/httpd if accessibleAffected if The vulnerable function set_local_time_0 is present in the httpd binary
A user is affected if they have a Tenda W12 router running firmware version 3.0.0.7(4763) with the httpd service active and the web interface exposed to the internet, allowing remote attackers to trigger the buffer overflow via the Time parameter in set_local_time_0.
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 management interface to minimize attack surface, and apply any available firmware update from Tenda once released. Consider disabling remote administration if not required.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-10192 — 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-10192 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