CVE-2011-2110

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 86% exploitation probability in the next 30 days; it does not lift the v2 base. EPSS sets EG Risk's exploitation input. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized
10.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 86%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 86%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is available — apply it.

Adobe Flash Player before 10.3.181.26 on Windows, Mac OS X, Linux, and Solaris, and 10.3.185.23 and earlier on Android, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, as exploited in the wild in June 2011.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
80
EG Risk 80/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation86% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
86%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 16, 2011

Last Modified

April 29, 2026

References (13)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatflash-plugin-0:10.3.181.26-1.el52011-06-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 9× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 20 repeat rows among the latest 71 are merged into the row they repeat.

  1. 2026-10-12 01:43 UTCEG score recompute
  2. 2026-10-08 16:34 UTCEPSS rescoreEPSS 86% · 99th percentile
  3. 2026-10-06 15:10 UTCEPSS rescoreEPSS 86% · 99th percentile
  4. 2026-09-30 14:58 UTCEPSS rescoreEPSS 86% · 99th percentile
  5. 2026-09-29 08:17 UTCEG score recompute
  6. 2026-09-27 13:39 UTCEPSS rescoreEPSS 86% · 99th percentile
  7. 2026-09-26 15:52 UTCEPSS rescoreEPSS 86% · 99th percentile
  8. 2026-09-24 13:57 UTCEPSS rescoreEPSS 86% · 99th percentile
  9. 2026-09-15 03:04 UTCEPSS rescoreEPSS 86% · 99th percentile
  10. 2026-09-06 13:41 UTCEPSS rescoreEPSS 86% · 99th percentile
  11. 2026-09-05 15:22 UTCEPSS rescoreEPSS 86% · 99th percentile
  12. 2026-08-19 16:58 UTCEPSS rescoreEPSS 86% · 99th percentile
  13. 2026-08-15 01:25 UTCEPSS rescoreEPSS 86% · 99th percentile
  14. 2026-08-05 19:12 UTCEPSS rescoreEPSS 86% · 99th percentile
  15. 2026-07-26 13:43 UTCEG score recomputeAssessed again: 10.0 HIGH
  16. 2026-07-23 01:06 UTCVendor advisory
  17. 2026-07-23 01:06 UTCGHSA enrichmentGHSA-3p7j-r8qq-j3mf · GitHub severity HIGH
  18. 2026-07-23 01:05 UTCVendor advisory
  19. 2026-07-23 01:05 UTCGHSA enrichmentGHSA-3p7j-r8qq-j3mf · GitHub severity HIGH
  20. 2026-07-23 01:05 UTCEG score recompute▼ 9.00
  21. 2026-07-23 00:08 UTCEG score recompute
  22. 2026-07-22 21:47 UTCEG score recompute
  23. 2026-07-22 14:03 UTCEPSS rescoreEPSS 86% · 99th percentile
  24. 2026-07-20 17:03 UTCEPSS rescoreEPSS 86% · 99th percentile
  25. 2026-07-16 16:58 UTCEPSS rescoreEPSS 86% · 99th percentile
Show 26 more
  1. 2026-07-13 22:25 UTCEPSS rescoreEPSS 86% · 99th percentile
  2. 2026-07-13 06:08 UTCEPSS rescoreEPSS 86% · 99th percentile
  3. 2026-07-11 08:22 UTCEPSS rescoreEPSS 86% · 99th percentile
  4. 2026-07-02 14:01 UTCEPSS rescoreEPSS 86% · 99th percentile
  5. 2026-06-27 03:05 UTCEPSS rescoreEPSS 86% · 99th percentile
  6. 2026-06-24 14:02 UTCEPSS rescoreEPSS 86% · 99th percentile
  7. 2026-06-23 21:30 UTCEPSS rescoreEPSS 86% · 99th percentile
  8. 2026-06-17 17:49 UTCEPSS rescoreEPSS 86% · 99th percentile
  9. 2026-06-15 17:44 UTCEPSS rescoreEPSS 86% · 99th percentile
  10. 2026-06-12 23:08 UTCEPSS rescoreEPSS 91% · 99th percentile
  11. 2026-06-10 22:14 UTCEPSS rescoreEPSS 91% · 99th percentile
  12. 2026-06-08 14:14 UTCEPSS rescoreEPSS 91% · 99th percentile
  13. 2026-06-07 15:22 UTCEPSS rescoreEPSS 91% · 99th percentile
  14. 2026-06-06 13:44 UTCEPSS rescoreEPSS 91% · 99th percentile
  15. 2026-06-05 22:44 UTCEPSS rescoreEPSS 91% · 99th percentile
  16. 2026-06-02 20:10 UTCEPSS rescoreEPSS 91% · 99th percentile
  17. 2026-05-31 22:28 UTCEPSS rescoreEPSS 91% · 99th percentile
  18. 2026-05-29 07:44 UTCEG score recompute
  19. 2026-05-29 07:44 UTCVendor advisory
  20. 2026-05-29 07:44 UTCGHSA enrichmentGHSA-3p7j-r8qq-j3mf · GitHub severity HIGH
  21. 2026-05-27 13:38 UTCEPSS rescoreEPSS 91% · 99th percentile
  22. 2026-05-26 13:41 UTCEPSS rescoreEPSS 91% · 99th percentile
  23. 2026-05-26 07:16 UTCEPSS rescoreEPSS 91% · 99th percentile
  24. 2026-05-22 21:15 UTCEPSS rescoreEPSS 91% · 99th percentile
  25. 2026-05-20 22:37 UTCEPSS rescoreEPSS 91% · 99th percentile
  26. 2026-05-18 21:29 UTCEPSS rescoreEPSS 91% · 99th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-19295✓ verified
    Published Jun 20, 2012

    Adobe Flash Player - AVM Verification Logic Array Indexing Code Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/browser/adobe_flashplayer_arrayindexing✓ verified
    Published Jun 20, 2012

    Adobe Flash Player AVM Verification Logic Array Indexing Code Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2011-2110?
CVE-2011-2110 is a high-severity vulnerability; its CVE record was published on June 16, 2011. Adobe Flash Player before 10.3.181.26 on Windows, Mac OS X, Linux, and Solaris, and 10.3.185.23 and earlier on Android, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, as exploited in the wild in June 2011.
When was CVE-2011-2110 made public?
CVE-2011-2110 was made public on June 14, 2011: that is the date its CVE record's CNA, Adobe Systems Incorporated, gives for when the vulnerability was made public. The CVE record itself was published on June 16, 2011. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2011-2110 actively exploited?
CVE-2011-2110 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 86% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2011-2110?
A fix for CVE-2011-2110 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-2110

Explore →

Is Your Infrastructure Affected by CVE-2011-2110?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs