CVE-2016-6699

Name: CVE-2016-6699
Creator: NVD / NIST
Published: 2016-12-13T19:59:00.2+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.32%

Last modified Jun 17, 2026

CVE-2016-6699 is a vulnerability of currently unknown severity. A remote code execution vulnerability in libstagefright in Mediaserver in Android 7.0 before 2016-11-01 could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. EPSS estimates a 1.32% chance of exploitation in the next 30 days.

Description

A remote code execution vulnerability in libstagefright in Mediaserver in Android 7.0 before 2016-11-01 could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. Android ID: A-31373622.

Metrics

EPSS Probability

1.32%

67.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-119

Affected Software

Vendor	Product	Versions
Google	Android	<= 7.0

References

http://www.securityfocus.com/bid/94157
https://android.googlesource.com/platform/frameworks/av/+/3b1c9f692c4d4b7a683c2b358fc89e831a641b88Issue Tracking, Patch
https://source.android.com/security/bulletin/2016-11-01.htmlVendor Advisory
http://www.securityfocus.com/bid/94157
https://android.googlesource.com/platform/frameworks/av/+/3b1c9f692c4d4b7a683c2b358fc89e831a641b88Issue Tracking, Patch
https://source.android.com/security/bulletin/2016-11-01.htmlVendor Advisory

Timeline

Published: Dec 13, 2016
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-6699?

How severe is CVE-2016-6699?

Severity scoring for CVE-2016-6699 is pending analysis. The EPSS model estimates a 1.32% probability of exploitation in the next 30 days.

How do I fix CVE-2016-6699?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-6699?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST