CVE-2026-8764
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 vulnerability has been detected in H3C Magic B3 up to 100R002. This affects the function UpdateWanParams of the file /goform/aspForm. Such manipulation of the argument param leads to buffer overflow. The attack may be performed from remote. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceBuffer overflow vulnerability in H3C Magic B3 routers (firmware 100R002 and earlier) in the UpdateWanParams function of /goform/aspForm web interface. Remote attackers can exploit this by manipulating the 'param' argument to overflow a buffer, potentially leading to code execution or denial of service.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 an H3C Magic B3 router. Alternatively, check the DHCP client list or network scan results for the device manufacturer and model identifier.Affected if The device is not an H3C Magic B3 router, then this specific CVE does not apply.
-
Check the firmware versionLog into the router web interface and navigate to the status or system settings page to view the firmware version. Alternatively, check the administrative GUI for a version display or use the router's diagnostic page if available.Affected if The firmware version is 100R002 or any version earlier than 100R002.
-
Verify the web management interface is exposedConfirm that the router web interface at /goform/aspForm is accessible from the network. Attempt to access the URL or use a tool to check if the endpoint responds. The vulnerability exists in the UpdateWanParams function within this web interface.Affected if The /goform/aspForm web interface is accessible from the network and responds to requests.
-
Check for WAN parameter configuration accessLocate the WAN settings or internet connection configuration section in the router web interface. The vulnerable UpdateWanParams function processes the 'param' argument related to WAN parameters.Affected if WAN parameter configuration is available and can be modified through the web interface.
A user is affected if they are running an H3C Magic B3 router with firmware version 100R002 or earlier and the web management interface is accessible on their 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 dataSince the vendor has not responded to the disclosure, implement network segmentation to isolate the affected device, restrict access to the web management interface via firewall rules, and monitor for indicators of compromise until a vendor patch becomes available.
- Consultation8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8764 — 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-8764 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