HUAWEI P30 with versions earlier than 10.1.0.135(C00E135R2P11) have an improper signature verification vulnerability.

published 2020-07-06 6y ago modified 2026-06-17 4mo ago also EUVD-2020-30055

cvss: 5.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 28%
public exploits: 0; none known

HUAWEI P30 with versions earlier than 10.1.0.135(C00E135R2P11) have an improper signature verification vulnerability. The system does not improper check signature of specific software package, an attacker may exploit this vulnerability to load a crafted software package to the device.

Patch / fix

fixed in 1

huawei p30_firmware 10.1.0.135\(c00e135r2p11\)

Is CVE-2020-9226 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	5.5	CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected products

n/a HUAWEI P30

Classification

Weakness

CWE-347 Improper Verification of Cryptographic Signature

References

huawei.com /en/psirt/security-advisories/huawei-sa-20200701-02-smartphone-en
vendor-advisory

Sources

CVE List CVE-2020-9226
NVD CVE-2020-9226

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.