CVE-2020-9222 is a high severity (CVSS 7.0) privilege escalation flaw in Huawei FusionCompute. Insufficient checks on files that get deserialized let a local attacker raise permissions. Huawei lists versions 6.3.0 through 8.0.0 and offers the fix through its support team, with no temporary fix.
What's affected
- FusionCompute 6.3.0, 6.3.1, 6.5.0, 6.5.1 and 8.0.0, per Huawei's advisory.
- Fixed: 8.0.0.SPC1 is the only resolved version the advisory table names clearly. The pairing for older branches is not clear, so confirm your branch with Huawei.
- Customers get the fix by contacting Huawei TAC. No temporary fix exists.
The record scores it 7.0 (High) with vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. The record does not flag it as a CISA Known Exploited Vulnerability, and none of the pages I read report exploitation in the wild.
How to check if you're exposed
Read the FusionCompute version from the VRM management interface and compare it with the advisory. If you run 6.x, ask Huawei TAC which release closes this issue for your branch.
What to do now
- Inventory FusionCompute clusters and their VRM versions.
- Open a case with Huawei TAC for the fixed release for your branch.
- Restrict local and shell access on management nodes to named administrators.
- Apply the update during a maintenance window.
- Audit local accounts on the hypervisor hosts afterward.
After you patch, record the new version for Huawei FusionCompute in your asset inventory, and confirm it with the same check you used above. A fix that was never verified is easy to forget, and an inventory that shows versions is what lets you answer the next advisory in minutes instead of days.
Why it matters
The record maps the flaw to CWE-269. The product reads files that are turned back into objects without checking them enough, so a file placed by a local user can lead to actions with higher rights.
The impact sits on a virtualization layer, so a successful local escalation affects every guest the host runs. The attacker still needs local access first, which is the main constraint.
To check open source components in your own projects for known CVEs like this one, try the free in-browser dependency scan at gold.safeguard.sh/scan, or look the CVE up in the Gold directory.
Quick check
Is there a workaround?
Huawei states no temporary fix is available. Reducing who has local access to the management nodes lowers the risk until you can update.
How do I find every place Huawei FusionCompute is used?
Start with an inventory of installed software and versions, because you cannot patch what you have not found. Check servers, build hosts, test copies and anything a vendor bundles. For open source libraries, a dependency scan or SBOM gives the same list for your code.
Sources
Last reviewed: 19 October 2026.