CVE-2026-15691
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 · uneditedA security flaw has been discovered in Tenda BE12 Pro 16.03.66.23. This affects the function fromSafeClientFilter of the file /goform/SafeClientFilter. Performing a manipulation of the argument page results in stack-based buffer overflow. The attack is possible to be carried out remotely. The exploit has been released to the public and may be used for attacks.
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 confidenceA stack-based buffer overflow vulnerability exists in Tenda BE12 Pro firmware version 16.03.66.23 within the /goform/SafeClientFilter web interface. The fromSafeClientFilter function fails to properly validate the 'page' parameter, allowing an attacker to overflow the stack and potentially execute arbitrary code remotely.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm device model is Tenda BE12 ProAccess the router web interface or check the device label/marketing materials to verify the exact model number. Alternatively, check the DHCP vendor string or SNMP sysDescr if available remotely.Affected if The device is not a Tenda BE12 Pro router.
-
Identify installed firmware versionLog into the Tenda BE12 Pro web interface and navigate to System Settings > Firmware Update or similar. The version is typically displayed on the main status page or in the Administration section. Check for version 16.03.66.23 or earlier.Affected if The firmware version is 16.03.66.23 or an earlier version that shares the same vulnerable code base.
-
Verify web interface is network accessibleAttempt to access http(s)://<router-ip>/ on the local network. The router web interface typically listens on port 80 or 443.Affected if The web interface responds and is reachable from an untrusted network segment.
-
Confirm vulnerable endpoint existsSend an HTTP request to /goform/SafeClientFilter endpoint: curl -X POST http://<router-ip>/goform/SafeClientFilter -d 'page=test'Affected if The endpoint returns a response (rather than 404) indicating it exists on the device.
-
Check if page parameter triggers processingSend a crafted request with an oversized page parameter to observe behavior: curl -X POST http://<router-ip>/goform/SafeClientFilter -d 'page=$(python3 -c "print("A"*1000)")' and observe if the device hangs, reboots, or returns an error.Affected if The device accepts the oversized parameter without proper validation, which may manifest as a crash, unexpected response, or observable buffer handling.
You are affected if you are running Tenda BE12 Pro firmware version 16.03.66.23 (or earlier) and the /goform/SafeClientFilter web interface is accessible from your network.
Generated from the published advisory. Verify against your own configuration.
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 dataApply available vendor firmware updates; if no patch exists, disable or restrict access to the /goform/SafeClientFilter web interface and consider network segmentation to limit exposure to trusted users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-15691 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-15691 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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