dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2026-6581

HIGH · 8.8 CVSS v3.1 Published 2026-04-19
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

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 detected in H3C Magic B1 up to 100R004. Affected by this vulnerability is the function SetMobileAPInfoById of the file /goform/aspForm. Performing a manipulation of the argument param results in buffer overflow. Remote exploitation of the attack is possible. The exploit is now public 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 · high confidence

Buffer overflow vulnerability in H3C Magic B1 router's web interface function SetMobileAPInfoById in /goform/aspForm allows remote attackers to execute arbitrary code via crafted parameter manipulation. The vulnerability is confirmed public with working exploit.

MitigationReplace affected H3C Magic B1 devices or implement strict network segmentation/firewalling to block unauthorized access to the device's web management interface (port 80/443) since the vendor has not responded to disclosure.

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. Confirm device model is H3C Magic B1
    Access the device's web interface or check the device label/metadata. The web interface typically displays device information at login or in status pages. Alternatively, check DHCP lease tables or network scans for device identification.
    Affected if The device is an H3C Magic B1 router model.
  2. Verify web management interface is exposed
    Attempt to access http://<device-ip>/ or https://<device-ip>/ from the network. Check if ports 80 and 443 are open on the device IP using nmap -p 80,443 <device-ip> or netcat.
    Affected if The device web interface (port 80/443) is reachable from an untrusted network or the internet.
  3. Confirm the aspForm endpoint exists
    Send an HTTP GET or POST request to http://<device-ip>/goform/aspForm and check for a valid HTTP response (not 404 or connection error). Use curl -v http://<device-ip>/goform/aspForm.
    Affected if The /goform/aspForm endpoint responds, indicating the vulnerable function is present.
  4. Check if remote management is enabled
    In the router web interface, navigate to Administration or Management settings. Look for options like 'Remote Management', 'Web Management from WAN', or 'Enable Remote Web Access'. Check configuration via http://<device-ip>/goform/formWanHttp or similar endpoints.
    Affected if Remote management/WAN access to the web interface is enabled, exposing the vulnerability to external attackers.
  5. Identify firmware version
    In the router web interface, look for a Firmware Version, Software Version, or System Version field (typically under Status, System Info, or Administration > Firmware Upgrade pages). Note: The H3C Magic B1 web interface may not expose version info publicly.
    Affected if The firmware version cannot be determined but the device model is confirmed as H3C Magic B1.

The environment is affected if an H3C Magic B1 router has its web interface accessible (especially from WAN), as CVE-2026-6581 is a buffer overflow in the SetMobileAPInfoById function reachable via /goform/aspForm.

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

Replace affected H3C Magic B1 devices or implement strict network segmentation/firewalling to block unauthorized access to the device's web management interface (port 80/443) since the vendor has not responded to disclosure.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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