CVE-2016-8762

MEDIUMNVD 5.05.0
EchelonGraph scoreMEDIUM confidence

Score 5.0 from GitHub Security Advisory published 2022-05-17. NVD baseline CVSS 5.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The TrustZone driver in Huawei P9 phones with software Versions earlier than EVA-AL10C00B352 and P9 Lite with software VNS-L21C185B130 and earlier versions and P8 Lite with software ALE-L02C636B150 and earlier versions has an input validation vulnerability, which allows attackers to cause the system to restart.

CVSS v3
5.0
EG Score
5.0(medium)
EPSS
10.4%
KEV
Not listed

Published

April 2, 2017

Last Modified

May 13, 2026

Frequently asked(5)

What is CVE-2016-8762?
CVE-2016-8762 is a medium vulnerability published on April 2, 2017. The TrustZone driver in Huawei P9 phones with software Versions earlier than EVA-AL10C00B352 and P9 Lite with software VNS-L21C185B130 and earlier versions and P8 Lite with software ALE-L02C636B150 and earlier versions has an input validation vulnerability, which allows attackers to cause the…
When was CVE-2016-8762 disclosed?
CVE-2016-8762 was first published in the National Vulnerability Database on April 2, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-8762 actively exploited?
CVE-2016-8762 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 10.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2016-8762?
CVE-2016-8762 has a CVSS v3 base score of 5.0 (NVD).
How do I remediate CVE-2016-8762?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-8762, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-8762

Explore →

Is Your Infrastructure Affected by CVE-2016-8762?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.