CVE-2016-1010

Integer overflow in Adobe Flash Player before 18.0.0.333 and 19.x through 21.x before 21.0.0.182 on Windows and OS X and before 11.2.202.577 on Linux, Adobe AIR before 21.0.0.176, Adobe AIR SDK before 21.0.0.176, and Adobe AIR SDK & Compiler before 21.0.0.176 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2016-0963 and CVE-2016-0993.

CVSS: 8.8Highscored by CISA
Exploited in the wild: Yes, in CISA KEV since 25 May 2022CISA deadline for US federal agencies: 15 Jun 2022
EPSS: 19.3%chance of exploitation in the next 30 daystop 3% of scored CVEsFIRST score of 11 Nov 2026
Fix: Patch availablesee the advisories in the references
Published: 12 Mar 2016analysed here 12 Nov 2026

Do first. The impacted products are 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: CWE-190 Integer Overflow
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:air
adobe:air_sdk
samsung:x14j_firmware
adobe:flash_player_desktop_runtime
adobe:air_desktop_runtime
adobe:air_sdk_\&_compiler

Fix and mitigation

WAF and other mitigations

Can a WAF block it? No. This is an integer overflow, usually triggered by an ordinary-looking number or size. Generic WAF rules do not recognise it; only a rule written for this specific CVE can.

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 25 May 2022.
CISA due date: 15 Jun 2022, the remediation deadline for US federal agencies
CISA required action: The impacted products are end-of-life and should be disconnected if still in use.
Public exploit code: None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC: exploitation active, automatable no, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

12 Mar 2016Published
25 May 2022Added to CISA KEV (exploited in the wild)2,264 days (about 6 years) later
15 Jun 2022CISA remediation due date (US federal agencies)21 days later
4 Feb 2025CISA SSVC assessment: exploitation active966 days (about 3 years) later
21 Oct 2025CVE record last updated259 days (about 9 months) later
12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

Metric	Value	What it means
Attack vector	NetworkReachable over the internet or any routable network.	Reachable over the internet or any routable network.
Attack complexity	LowRepeatable attack, no special conditions.	Repeatable attack, no special conditions.
Privileges required	NoneThe attacker needs no prior access.	The attacker needs no prior access.
User interaction	RequiredA victim must click, open or otherwise cooperate.	A victim must click, open or otherwise cooperate.
Scope	UnchangedImpact stays within the vulnerable component.	Impact stays within the vulnerable component.
Confidentiality	HighTotal data disclosure possible.	Total data disclosure possible.
Integrity	HighComplete modification possible.	Complete modification possible.
Availability	HighFull outage possible.	Full outage possible.

Common questions

Is CVE-2016-1010 being exploited?

Yes. CVE-2016-1010 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-2016-1010?

CVE-2016-1010 is rated High with a CVSS score of 8.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-2016-1010?

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

What does CVE-2016-1010 affect?

CVE-2016-1010 affects adobe:flash_player, adobe:air, adobe:air_sdk, samsung:x14j_firmware, and 3 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

NVD CVE.org CVE Details Source

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

Advisories (5)

lists.opensuse.org /opensuse-security-announce/2016-03/msg00032.html
lists.opensuse.org /opensuse-security-announce/2016-03/msg00024.html
security.gentoo.org /glsa/201603-07
lists.opensuse.org /opensuse-security-announce/2016-03/msg00022.html
lists.opensuse.org /opensuse-security-announce/2016-03/msg00023.html

Where the data on this page comes from

CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
NVD: CVSS and CPE data
CISA KEV catalog: exploitation, date added, due date
CISA Vulnrichment (ADP): SSVC decision points
FIRST EPSS: exploit probability and percentile

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.