Skip to main content
Mallory
CriticalExploited in the wildCISA KEVVulnerability

CVE-2016-1019: Remote code execution and denial of service in Adobe Flash Player

Published Apr 7, 2016 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS22.3%98th percentile
CISA KEVYesAdded Mar 3, 2022
In the wildActivePer CISA KEV
Vendor
Adobe
IdentifiersCVE-2016-1019CWE-119

CVE-2016-1019 affects Adobe Flash Player 21.0.0.197 and earlier, allowing remote attackers to cause an application crash or potentially execute arbitrary code. The vulnerable function and underlying defect are unspecified. Exploit code was present in the wild by March 31, 2016, and successful exploitation was observed through the Magnitude exploit kit in April 2016. Other delivery mechanisms included malicious advertisements, watering-hole websites, and crafted Word documents containing embedded Flash objects.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation can crash the Flash application or potentially execute attacker-controlled code on the affected endpoint. Successful attacks have delivered ransomware, including Cerber and Locky, and other malware. These payload effects are consequences of particular attack campaigns rather than independently established properties of the vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Remove Adobe Flash Player where it is not required. Updated endpoint protection and exploit-kit network detection can provide supplementary defenses. A mitigation incorporated into Flash Player 21.0.0.182 appeared to prevent the observed degraded exploit from succeeding, but it was not established as a complete fix for the underlying vulnerability.

Remediation

Patch, then assume compromise.

Apply Adobe's emergency security update released on April 7, 2016, for CVE-2016-1019. The exact fixed version is not specified. Verify that updates install successfully, including in environments where proxy or connectivity problems can prevent the updater from reaching its download service.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AdobeAir Desktop Runtimeapplication
AdobeAir Sdkapplication
AdobeAir Sdk & Compilerapplication
AdobeFlash Playerapplication
AdobeFlash Player Desktop Runtimeapplication
FAQ

Frequently asked questions

Is CVE-2016-1019 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
Is there a public exploit for CVE-2016-1019?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2016-1019.
Is there a patch for CVE-2016-1019?
Apply Adobe's emergency security update released on April 7, 2016, for CVE-2016-1019. The exact fixed version is not specified.
What products are affected by CVE-2016-1019?
Adobe Flash Player, Adobe Air Desktop Runtime, Adobe Air Sdk, Adobe Air Sdk & Compiler, and Adobe Flash Player Desktop Runtime.
How severe is CVE-2016-1019?
CVE-2016-1019 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 22.3% (98th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence11Every report linking this CVE to a named adversary.
Associated malware22Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.