CVE Intelligence
CISA KEV Critical

CVE-2016-4171 — Adobe Flash Player Remote Code Execution Vulnerability

Unspecified vulnerability in Adobe Flash Player 21.0.0.242 and earlier allows remote attackers to execute arbitrary code via unknown vectors, as exploited in the wild in June 2016.

Published Jun 16, 2016 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: adobe

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 20.1% (30-day exploitation probability)+15
  • Technical severity (critical)+10

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Confirmed
CISA KEV, listed Mar 25, 2022
EPSS FIRST
20.06%
ahead of 97% of scored CVEs · Oct 14, 2026
Affects
Adobe
Flash Player and 6 more
CVSS base
9.8
Critical · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

CISA required action CISA

The impacted product is end-of-life and should be disconnected if still in use.

US federal deadline: Apr 15, 2022 — passed 1644 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Adobe Flash Player, Opensuse Opensuse, Red Hat Enterprise Linux Desktop…).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  4. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  5. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes, errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Adobe Flash Player ≤ 21.0.0.242≤ 18.0.0.352≤ 11.2.202.621 Vulnerable NIST National Vulnerability Database
Opensuse Opensuse version 13.2version 13.1 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Desktop version 6.0version 5.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Server version 6.0version 5.0 Vulnerable NIST National Vulnerability Database
Red Hat Enterprise Linux Workstation version 5.0version 6.0 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Desktop version 12-sp1version 12 Vulnerable NIST National Vulnerability Database
SUSE Linux Enterprise Workstation Extension version 12version 12-sp1 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.8 CVSS 3.1 Critical 3.9 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
10.0 CVSS 2.0 High 10.0 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.8 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

CISA KEV details CISA

CISA lists a CVE once it has evidence of exploitation against real targets.

Listed
Mar 25, 2022
Federal deadline
Apr 15, 2022
passed 1644 day(s) ago
Ransomware use
Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 20.06%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Hunt retroactively in logs from before Mar 25, 2022 (KEV listing): exploitation may have started earlier.
web/proxy/WAF logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Affected products added · adobe/flash player, redhat/enterprise linux desktop, redhat/enterprise linux server, redhat/enterprise linux workstation
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 9.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • 2022
  • Added to CISA KEV catalog
    Mar 24, 2022 · CISA
  • 2016
  • CVE published
    Jun 16, 2016 · adobe

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

12 on the record

Elsewhere on this site

Adobe
every CVE for this vendor
2022-03
what else CISA listed that month

Related CVEs (same products)

  • High CVE-2026-31431 Linux Kernel Incorrect Resource Transfer Between Spheres Vulnerability KEV Apr 22, 2026
  • High CVE-2025-32463 Sudo Inclusion of Functionality from Untrusted Control Sphere Vulnerability KEV Jun 30, 2025
  • High CVE-2025-6021 Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2 Jun 12, 2025
  • High CVE-2024-12085 Rsync: info leak via uninitialized stack contents Jan 14, 2025
  • High CVE-2024-1086 Linux Kernel Use-After-Free Vulnerability KEV Jan 31, 2024
  • High CVE-2019-8720 WebKitGTK Memory Corruption Vulnerability KEV Mar 6, 2023

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No CWE classification.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2016-4171 is "Adobe Flash Player Remote Code Execution Vulnerability", rated Critical. It affects Flash Player (Adobe); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 9.8 describes technical severity. EPSS 20.06% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.