dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-15543

HIGH · 8.8 CVSS v3.1 Published 2026-07-13
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 5 weeks old

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 found in Tenda CH22 1.0.0.1. This impacts the function formCertListInfo of the file /goform/CertListInfo. The manipulation of the argument Name results in buffer overflow. The attack can be launched remotely. The exploit has been made public and could 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 confidence

Buffer overflow vulnerability in Tenda CH22 router firmware 1.0.0.1 in the /goform/CertListInfo handler. The 'Name' parameter passed to the formCertListInfo function is not properly bounds-checked, allowing an attacker to overflow a buffer and potentially execute arbitrary code remotely.

MitigationUpdate router firmware if vendor releases a patch; otherwise, disable remote web management access, implement network segmentation, and use WAF/IPS rules to block malformed requests to /goform/CertListInfo.

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
    Access the router admin panel or check the device label to confirm it is a Tenda CH22 router
    Affected if The device is not a Tenda CH22 router
  2. Check firmware version
    Log into the router admin interface (typically at 192.168.0.1) and navigate to System Settings or Firmware Upgrade to view the installed firmware version. Compare against the affected version 1.0.0.1
    Affected if Firmware version is 1.0.0.1 or falls within an unpatched version range
  3. Verify web management interface is accessible
    Attempt to access the router web interface on common ports 80 or 443, or test connectivity to the /goform/CertListInfo endpoint via HTTP request
    Affected if The web management interface is reachable from the network
  4. Confirm remote management is enabled
    In the router admin panel, check under Advanced Settings or Security Settings for 'Remote Management' or 'Remote Web Management' status
    Affected if Remote web management is enabled and the router is directly accessible from the internet

The device is affected if it is a Tenda CH22 router running firmware 1.0.0.1 with the web management interface accessible, especially if remote management 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

Update router firmware if vendor releases a patch; otherwise, disable remote web management access, implement network segmentation, and use WAF/IPS rules to block malformed requests to /goform/CertListInfo.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-15543 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