Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10189

HIGH · 8.8 CVSS v3.1 Published 2026-05-31
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in Tenda W12 3.0.0.7(4763). This vulnerability affects the function cgiSysTimeInfoSet of the file /bin/httpd. The manipulation of the argument sec leads to stack-based buffer overflow. It is possible to initiate the attack 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 confidence

Stack-based buffer overflow in Tenda W12 router firmware 3.0.0.7(4763) in the cgiSysTimeInfoSet function within /bin/httpd. The 'sec' parameter lacks proper bounds checking, allowing remote attackers to overflow a stack buffer via crafted HTTP requests.

MitigationApply vendor firmware update if available; otherwise, restrict network access to the device's web interface or implement input validation filters at an upstream network device to block malicious requests targeting the cgiSysTimeInfoSet endpoint.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model and firmware version
    Access the router's web administration interface or check via telnet/SSH console for the exact firmware version. On Tenda W12, this is typically visible in the web UI footer or in System Settings > Firmware Version.
    Affected if The firmware version is 3.0.0.7(4763)
  2. Confirm /bin/httpd is running
    Check if the httpd process is active on the device. This can be done via console with 'ps' command or by attempting to access the web interface on port 80/443.
    Affected if The httpd service is running and the web management interface is accessible on the network
  3. Verify the cgiSysTimeInfoSet function exists
    Extract and analyze the /bin/httpd binary from the firmware image. Use binwalk to extract and strings or radare2 to confirm the presence of 'cgiSysTimeInfoSet' function.
    Affected if The binary contains the cgiSysTimeInfoSet function and accepts the 'sec' parameter
  4. Check network exposure of web interface
    Determine if the router's web management interface (port 80/443) is exposed to untrusted networks. Check router WAN interface accessibility and any port forwarding rules.
    Affected if The management interface is reachable from WAN or untrusted networks (not only from LAN)
  5. Check for remote administration settings
    In the router's web UI, look for Remote Management or Remote Administration settings under Advanced or Security settings. Verify if remote access is enabled.
    Affected if Remote administration/management is enabled, allowing external access to the web interface

A user is affected if they are running Tenda W12 firmware version 3.0.0.7(4763) with the httpd web interface accessible, particularly if remote administration is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware update if available; otherwise, restrict network access to the device's web interface or implement input validation filters at an upstream network device to block malicious requests targeting the cgiSysTimeInfoSet endpoint.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10189 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-10189 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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