Safeguard
Vulnerability Analysis•

CVE-2020-9080: High Local Privilege Escalation in Huawei Phones

CVE-2020-9080 is a high local privilege escalation flaw in Huawei Mate 20 Pro and nova 5i phones. Update to the builds named in Huawei's advisory.

Safeguard Security Team
3 min read

CVE-2020-9080 is a high severity (CVSS 7.8) improper privilege management flaw in some Huawei smartphones. A local, authenticated attacker could craft input to gain higher privileges. Huawei lists Mate 20 Pro builds before 10.1.0.163 and nova 5i builds before 10.0.0.125 as affected, and no temporary fix.

What's affected

  • HUAWEI Mate 20 Pro build 10.1.0.135 (C01E135R2P8), fixed in 10.1.0.163 (C01E160R2P8).
  • HUAWEI Mate 20 Pro (UD) build 10.1.0.135 (C00E135R3P8), fixed in 10.1.0.163 (C00E160R3P8).
  • HUAWEI nova 5i, earlier than 10.0.0.125 (C01E123R7P3), fixed in 10.0.0.125 (C01E123R7P3).
  • No temporary fix is listed by Huawei.

The record scores it 7.8 (High) with vector CVSS:3.1/AV:L/AC:L/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

Huawei devices show the build in Settings under About phone, in the system version field. Compare it with the fixed build in the advisory. Devices that support automatic updates should prompt you for the update.

What to do now

  1. List managed Huawei devices from your mobile device management tool.
  2. Check the system version on each against the fixed builds.
  3. Push or prompt the system update.
  4. Retire devices that no longer receive updates from work use.
  5. Treat any device that cannot be updated as untrusted for corporate data.

After you patch, record the new version for Huawei smartphones 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, improper privilege management. Software on the phone handles a specific input without checking whether the caller should get the resulting rights, so a local attacker can step up.

Because the attacker must already run code on the phone, the real risk is chaining: a malicious app that gains foothold, then uses a flaw like this to reach system level. Keeping firmware current closes that second step.

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

Can this be exploited remotely?

The record describes a local, authenticated attacker, and the CVSS vector uses local attack vector. A remote attacker would first need another way to run code on the device.

How do I find every place Huawei smartphones 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.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.