Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-10191

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 was determined in Tenda W12 3.0.0.7(4763). Impacted is the function cgiWifiMacFilterSet of the file /bin/httpd. This manipulation of the argument wifiMacFilterSet.macList.mac causes stack-based buffer overflow. The attack can be initiated remotely. The exploit has been publicly disclosed and may be utilized.

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 cgiWifiMacFilterSet function within /bin/httpd. The vulnerability is triggered via the wifiMacFilterSet.macList.mac parameter, allowing remote attackers to potentially execute arbitrary code via overflowing a stack buffer.

MitigationApply vendor firmware patch if available; otherwise, disable the WiFi MAC filter feature and implement network-level access controls to limit exposure to the router's web interface.

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. Confirm Tenda W12 router model
    Check router model via web admin panel (typically at 192.168.0.1), SSH/Telnet login, or physical device label
    Affected if Device is not a Tenda W12 router, then not affected
  2. Check firmware version
    In web admin panel look under System/Firmware or Status page, or via SSH run: cat /proc/version or cat /etc/firmware_version
    Affected if Firmware version is 3.0.0.7 (exact match to affected version)
  3. Verify vulnerable binary exists
    Access router via SSH/Telnet and check for /bin/httpd: ls -la /bin/httpd
    Affected if /bin/httpd exists and corresponds to unpatched firmware v3.0.0.7
  4. Check web interface accessibility
    Attempt to reach router web admin panel from network; verify port 80/443 is listening: curl -I http://router_ip/
    Affected if Web management interface is exposed and reachable (required for exploitation)
  5. Identify if MAC filter feature is accessible
    Check router web UI for WiFi MAC filtering settings, or probe for cgiWifiMacFilterSet endpoint if known
    Affected if MAC filtering feature is enabled or accessible on the device

Device is affected only if it is a Tenda W12 router running firmware v3.0.0.7 with the vulnerable /bin/httpd binary and web interface accessible to an attacker.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor firmware patch if available; otherwise, disable the WiFi MAC filter feature and implement network-level access controls to limit exposure to the router's web interface.

Recommended fix Moderate confidence

Tenda W12 firmware version newer than 3.0.0.7(4763) - obtain latest version from tenda.com.cn

  1. 1. Visit the official Tenda support page at www.tenda.com.cn and navigate to the downloads/support section for the W12 router.
  2. 2. Look for firmware updates that address security vulnerabilities, specifically checking release notes for CVE-2026-10191 or stack-based buffer overflow fixes in the cgiWifiMacFilterSet function.
  3. 3. Download the latest firmware version newer than 3.0.0.7(4763) from Tenda's official website.
  4. 4. Access the Tenda W12 router's web administration interface (typically at 192.168.0.1).
  5. 5. Navigate to System Settings > Firmware Upgrade or similar option.
  6. 6. Upload and apply the downloaded firmware update.
  7. 7. After the router reboots, verify the firmware version has been updated and confirm the vulnerability is resolved.
Caveat Firmware updates may reset router configuration to defaults; back up current settings before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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