Skip to content

CVE-2015-5122

Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13.x through 13.0.0.302 on Windows and OS X, 14.x through 18.0.0.203 on Windows and OS X, 11.x through 11.2.202.481 on Linux, and 12.x through 18.0.0.204 on Linux Chrome installations allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via crafted Flash content that leverages improper handling of the opaqueBackground property, as exploited in the wild in July 2015.

CVSS
9.8Critical
Exploited in the wild
Yes, in CISA KEV since 13 Apr 2022CISA deadline for US federal agencies: 4 May 2022public exploit code
EPSS
87.0%chance of exploitation in the next 30 daystop 0.3% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
14 Jul 2015analysed here 12 Nov 2026

Do first. The impacted product is end-of-life and should be disconnected if still in use. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • adobe:flash_player
  • adobe:flash_player_desktop_runtime
  • redhat:enterprise_linux_desktop
  • redhat:enterprise_linux_server
  • redhat:enterprise_linux_server_eus
  • redhat:enterprise_linux_workstation
  • opensuse:evergreen
  • suse:linux_enterprise_desktop
  • suse:linux_enterprise_workstation_extension

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. This is a use-after-free memory bug. Generic WAF rules do not recognise the input that triggers it; only a rule written for this specific CVE can, and only if the triggering request has a recognisable shape.

Also consider: patch

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 13 Apr 2022.
CISA due date
4 May 2022, the remediation deadline for US federal agencies
CISA required action
The impacted product is end-of-life and should be disconnected if still in use.
Public exploit code
Yes: 1 on Exploit-DB · 1 Metasploit module
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 17 Nov 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Exploit-DB

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 13 Jul 2015First public exploit or proof of concept
  2. 14 Jul 2015Published1 day later
  3. 13 Apr 2022Added to CISA KEV (exploited in the wild)2,465 days (about 7 years) later
  4. 4 May 2022CISA remediation due date (US federal agencies)21 days later
  5. 17 Nov 2025CISA SSVC assessment: exploitation active1,294 days (about 4 years) later
  6. 17 Nov 2025CVE record last updatedsame day later
  7. 12 Nov 2026Analysed by vulneraibility.com360 days (about 12 months) later

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionNoneNo victim action needed.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2015-5122 being exploited?

Yes. CVE-2015-5122 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2015-5122?

CVE-2015-5122 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2015-5122?

Yes. A fix has been recorded for CVE-2015-5122. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2015-5122 affect?

CVE-2015-5122 affects adobe:flash_player, adobe:flash_player_desktop_runtime, redhat:enterprise_linux_desktop, redhat:enterprise_linux_server, and 5 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

22 references in the CVE record, grouped by the tags the record gives them.

Advisories (9)

Show 3 more

Exploits (1)

Other links (12)

Show 6 more

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com