Classic Buffer OverflowWeakness · CWE-120

CVE-2026-36799

HIGH · 7.5 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Shenzhen Tenda Technology Co., Ltd Tenda G0 v15.11.0.5 was discovered to contain a buffer overflow in the portalAuth parameter of the formPortalAuth function. This vulnerability allows attackers to cause a Denial of Service (DoS) via a crafted HTTP request.

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 buffer overflow vulnerability exists in the formPortalAuth function of Tenda G0 router firmware v15.11.0.5. The portalAuth HTTP parameter fails to properly validate input length before copying data into a fixed-size buffer, allowing an attacker to trigger a denial of service by sending a specially crafted HTTP request with an oversized payload.

MitigationApply the vendor-supplied firmware patch for CVE-2026-36799 to upgrade from v15.11.0.5. If no patch is available, consider network segmentation to limit exposure of the router management interface or disable the portalAuth functionality until a fix is released.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 G0 router model
    Access the router's web interface or physically inspect the device label to verify the exact model is Tenda G0.
    Affected if The device is not a Tenda G0 router.
  2. Identify installed firmware version
    Log into the router web management interface and navigate to the System or Firmware settings to view the running firmware version. Compare this version to v15.11.0.5.
    Affected if The installed firmware version is 15.11.0.5 or falls within an unpatched version range.
  3. Verify HTTP management interface is enabled
    Attempt to access the router's web interface via HTTP on common ports (80, 8080, or the configured management port). Confirm the interface responds to requests.
    Affected if The router's web management interface is accessible on the network.
  4. Check if portal authentication feature is active
    Review the router's configuration to determine if the portal authentication or captive portal feature is enabled, which exposes the formPortalAuth function.
    Affected if The portal authentication feature is enabled and the formPortalAuth endpoint is reachable.

If the device is a Tenda G0 router running firmware v15.11.0.5 with the web management interface and portal authentication feature exposed, the environment is likely affected by this buffer overflow vulnerability.

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 the vendor-supplied firmware patch for CVE-2026-36799 to upgrade from v15.11.0.5. If no patch is available, consider network segmentation to limit exposure of the router management interface or disable the portalAuth functionality until a fix is released.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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