No exploitation reportedFix available

CVE-2017-8160

Q: Is CVE-2017-8160 actively exploited?

Active exploitation of CVE-2017-8160 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2017-8160?

CVE-2017-8160 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

No exploitation reported by the sources we read.

Published2017-11-22
WeaknessCWE-416

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

The Madapt Driver of some Huawei smart phones with software Earlier than Vicky-AL00AC00B172 versions,Vicky-AL00CC768B122,Vicky-TL00AC01B167,Earlier than Victoria-AL00AC00B172 versions,Victoria-TL00AC00B123,Victoria-TL00AC01B167 has a use after free (UAF) vulnerability. An attacker can trick a user to install a malicious application which has a high privilege to exploit this vulnerability, Successful exploitation may cause arbitrary code execution.

Timeline

dates in UTC

2017-11-2219:29CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2017-8160?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2017-8160?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Huawei victoria-tl00a firmwareversion to verify

Branch	Affected	Fixed in	Source
—	= victoria-tl00ac00b123	no fix published	NVD
—	= victoria-tl00ac01b167	no fix published	NVD

Huawei vicky-al00a firmwareversion to verify

Branch	Affected	Fixed in	Source
—	< vicky-al00ac00b172	vicky-al00ac00b172	NVD

Huawei vicky-al00c firmwareversion to verify

Branch	Affected	Fixed in	Source
—	= vicky-al00cc768b122	no fix published	NVD

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

www.huawei.comVendor Advisory

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.07.8read 2026-10-23
NVDCVSS 2.09.3read 2026-10-23
NVDweakness (CWE)CWE-416read 2026-10-23
FIRST EPSSEPSS score1.1 %2026-10-23

Technical details

CVSS v3 Vector: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Published: 2017-11-22
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2017-8160?

Is CVE-2017-8160 actively exploited?

Active exploitation of CVE-2017-8160 has not been confirmed. Its EPSS score was 1.1% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2017-8160?

CVE-2017-8160 has a CVSS v3 base score of 7.8 (HIGH severity), with vector string CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database