CVE-2016-6699: n/a vulnerability

CVE-2016-6699: A remote code execution vulnerability in libstagefright in Mediaserver in Android 7.0 before 2016-11-01 cou...

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.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 01:36 UTC (UTC+00:00)

Security readout for executives and security teams

CVE-2016-6699 is a critical Android media-processing flaw. A malicious media file could corrupt memory and potentially run code inside Android's Mediaserver process. The issue was fixed in Android security bulletin 2016-11-01 for Android 7.0 before that patch level. Unsupported or unpatched devices are the main concern. Exposure is most likely on Android 7.0 devices that did not receive the 2016-11-01 Android security update or a vendor firmware containing the fix. The provided affected-product metadata is incomplete, so validate against device patch levels rather than CPEs. Treat this as high-priority legacy mobile risk. The issue is old and patched, but unpatched Android 7.0 devices can remain exposed to critical media-processing RCE risk. Business urgency depends on whether such devices still access company data or networks. Mitigation focus: Apply the Android 2016-11-01 security update or later vendor firmware.; Prioritize unsupported Android 7.0 devices for replacement or isolation.; Confirm vendor builds include Android ID A-31373622 remediation..

Prepared: Jun 13, 2026, 13:16 UTC (UTC+00:00)

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup

cve · low confidence lookup

CVE-2016-6699 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup

Vulnerability profileCVE Program record

Severity: Unknown
CVSS: Not scored
Known Exploited: No
Published: Dec 13, 2016, 19:00 UTC (UTC+00:00)

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors

0Timeline events

0ADP providers

3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

CVE List V5 sourceCVE List V5
https://android.googlesource.com/platform/frameworks/av/+/3b1c9f692c4d4b7a683c2b358fc89e831a641b88CVE reference · x_refsource_CONFIRM
https://source.android.com/security/bulletin/2016-11-01.htmlCVE reference · x_refsource_CONFIRM

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus

n/an/an/aListed

Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.