Ac8 FirmwareOperating system · Tenda

CVE-2026-3044

HIGH · 8.8 CVSS v3.1 Published 2026-02-24
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 AC8 16.03.34.06. This affects the function webCgiGetUploadFile of the file /cgi-bin/UploadCfg of the component Httpd Service. The manipulation of the argument boundary 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

A stack-based buffer overflow vulnerability exists in the Tenda AC8 router firmware (v16.03.34.06) within the Httpd service's webCgiGetUploadFile function in /cgi-bin/UploadCfg. The boundary parameter in the file upload functionality can be manipulated to overflow a stack buffer, potentially allowing remote attackers to execute arbitrary code.

MitigationApply vendor firmware updates when available; until then, restrict external access to the router's web interface and disable the file upload CGI functionality if not 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
Ac8 FirmwareOperating system
Affected:= 16.03.34.06

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 the router model
    Access the router's web interface or check the device label to confirm it is a Tenda AC8 router
    Affected if The device is not a Tenda AC8 model
  2. Check the installed firmware version
    Log into the router web interface (typically at 192.168.0.1) and navigate to System Settings > Firmware Update, or use the command 'cat /proc/version' via telnet/SSH if available, to determine the exact firmware version
    Affected if The firmware version is exactly 16.03.34.06
  3. Verify the Httpd service is running
    Access the router via telnet/SSH (if enabled) and run 'ps | grep httpd' to confirm the Httpd web server process is active
    Affected if The Httpd service is running and the firmware is version 16.03.34.06
  4. Confirm the UploadCfg CGI endpoint exists
    Attempt to access the URL 'http://<router_ip>/cgi-bin/UploadCfg' via HTTP request to verify the endpoint is present on the device
    Affected if The /cgi-bin/UploadCfg endpoint responds and the firmware is version 16.03.34.06

The environment is affected if the device is a Tenda AC8 router running firmware version 16.03.34.06 with the Httpd service active and the /cgi-bin/UploadCfg endpoint accessible.

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 updates when available; until then, restrict external access to the router's web interface and disable the file upload CGI functionality if not required.

Fix this in Ac8 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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