CVE-2026-11553
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 vulnerability was found in Tenda HG7HG9 and HG10 300001138_en_xpon. This affects the function formPPPEdit of the file /boaform/formPPPEdit. The manipulation of the argument encodename results in stack-based 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 confidenceStack-based buffer overflow in Tenda HG7/HG9/HG10 routers allows remote attackers to corrupt stack memory via the encodename parameter in the formPPPEdit web form handler (/boaform/formPPPEdit). The overflow occurs because the encodename input is not properly bounds-checked before being copied to a fixed-size stack buffer, potentially enabling remote code execution.
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.
-
Identify the device modelAccess the router web interface or check the device label to confirm it is a Tenda HG7, HG9, or HG10 modelAffected if The device is a Tenda HG7, HG9, or HG10 router
-
Check firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the installed firmware version, or check via telnet/SSH if availableAffected if The firmware version matches or falls within the affected HG7/HG9/HG10 version range
-
Verify web interface accessibilityAttempt to access the router web interface on the default IP address (typically 192.168.0.1 or 192.168.1.1) via HTTP on port 80Affected if The web management interface is accessible and responds to requests
-
Confirm PPP configuration feature is enabledIn the router web interface, navigate to WAN settings or PPP settings section (typically under Advanced or Network Settings) to check if PPPoE, PPPoA, or similar PPP connections are configured or enabledAffected if PPP-related features (PPPoE, PPPoA, or similar) are enabled or configured on the device
-
Test formPPPEdit endpoint accessibilitySend an HTTP GET or POST request to /boaform/formPPPEdit endpoint (e.g., http://router_ip/boaform/formPPPEdit) and observe if the endpoint respondsAffected if The /boaform/formPPPEdit endpoint is accessible and accepts parameters including encodename
A user is affected if they have a Tenda HG7, HG9, or HG10 router with the vulnerable firmware where the web interface is accessible and PPP configuration features are enabled, allowing access to the vulnerable formPPPEdit endpoint with the encodename parameter.
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 vendor firmware update when available; otherwise, disable remote web management and restrict access to the device's HTTP interface to trusted IPs via firewall rules.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-11553 — 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-11553 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