Is CVE-2010-0188 (Adobe Reader and Acrobat Arbitrary Code Execution) being exploited in the wild?

By NHI Mgmt Group Editorial Team Updated October 19, 2026 Domain: Threats, Abuse & Incident Response

Yes. CISA added CVE-2010-0188 to its Known Exploited Vulnerabilities catalogue on 3 March 2022, which it does only when there is reliable evidence of active exploitation. CISA lists it as known to be used in ransomware campaigns. Unspecified vulnerability in Adobe Reader and Acrobat allows attackers to cause a denial of service or possibly execute arbitrary code.

What “exploited in the wild” means for this CVE

For this vulnerability, “exploited in the wild” is not a theoretical label. It means there is credible evidence that attackers have used the flaw against real systems, so the question is really about operational exposure: whether Adobe Reader or Acrobat instances are still present, how quickly they can be reached, and whether the organisation can absorb an emergency response without waiting for a routine patch cycle.

That distinction matters because KEV inclusion shifts the issue from general hygiene to active response. A vulnerability with confirmed exploitation should be treated as an immediate prioritisation problem, not simply as another item in the next maintenance window.

What to do first if you still have exposure

Start by confirming whether any supported or unsupported Adobe Reader or Acrobat installations remain in scope, including desktops, VDI images, shared workstations, and any endpoints that may open untrusted PDFs. Then determine whether the vulnerable software is internet-facing, reachable through email workflows, or present on high-value systems where document handling is common.

If the product is still deployed, follow the vendor advisory and the CISA Known Exploited Vulnerabilities Catalog for authoritative remediation timing and action guidance. For broader triage, use the Zero-Day and Exploited Vulnerabilities Guide to align KEV status with emergency mitigation, verification, and post-patch hunting.

When patching is delayed, reduce exposure by removing the software from systems that do not need it, restricting PDF handling to lower-risk paths, and tightening email and browser controls around suspicious documents. Where business constraints require temporary deferral, the priority is to shrink the number of systems that can be used as an initial access point.

What evidence to check for compromise and why it matters

Because this CVE was actively exploited, you should assume there may already have been an attempt to deliver a malicious document to users before remediation was completed. That makes endpoint telemetry, email security logs, browser download history, and process creation records useful for checking whether a PDF opened by Adobe Reader or Acrobat was followed by unexpected child processes, script execution, or payload staging.

Search for suspicious document names, unusual PDF attachments, repeated opens of the same file, and endpoint alerts tied to document viewers. If you find signs of execution around the exposure window, treat the case as a possible compromise investigation rather than a simple patching event.

CVE Program records help anchor the vulnerability identifier, while NIST National Vulnerability Database is useful for cross-checking the record and related metadata. For prioritisation discipline beyond this single CVE, the FIRST EPSS model is often used alongside KEV when deciding which exposures need immediate attention.

Risk and Threat Considerations

This CVE is high risk because exploited document-viewer flaws often sit on the path from ordinary user interaction to code execution. Attackers favour PDF readers because they are widely deployed, commonly trusted, and regularly exposed through email and web download workflows.

Failure mechanism: The flaw can be triggered when a crafted document is opened, allowing the attacker to move from a file-processing weakness to arbitrary code execution on the endpoint.

Impact: Successful exploitation can lead to endpoint compromise, follow-on credential theft, malware deployment, and broader intrusion activity, especially if the affected system has access to sensitive data or internal resources.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

MITRE ATT&CK addresses the attack and risk surface, while CIS Controls v8, NIST CSF 2.0, NIST SP 800-53 Rev 5 and OWASP ASVS set the governance and control requirements practitioners need to meet.

Framework	Control / Reference	Relevance
CIS Controls v8	CIS-7 — Continuous Vulnerability Management	KEV-listed flaws require rapid exposure discovery and remediation prioritisation.
Recommendation — Prioritise and remediate KEV-listed Adobe Reader and Acrobat exposure immediately.
NIST CSF 2.0	GV.RM-01 — Risk Management Strategy	KEV exploitation changes this from routine patching to urgent risk handling.
Recommendation — Escalate exploited vulnerabilities into your formal risk prioritisation process.
NIST SP 800-53 Rev 5	SI-2 — Flaw Remediation	Actively exploited software flaws require timely remediation and tracking.
Recommendation — Track and remediate the Adobe Reader and Acrobat flaw under flaw-remediation controls.
MITRE ATT&CK	T1203 — Exploitation for Client Execution	This CVE is an exploited client-side document flaw that can execute attacker code.
Recommendation — Map endpoint detections and hunting to client-execution exploitation patterns.
OWASP ASVS	V16 — Security Logging and Error Handling	Post-exploitation review depends on reliable logging around document handling and execution.
Recommendation — Retain logs needed to investigate suspicious PDF-driven execution chains.

Practitioner Guidance

What to prioritise: Treat KEV-listed document-reader flaws as exposure-management issues, not just patch tickets. Systems that routinely open external PDFs, process customer documents, or run with elevated user access should be first in line for remediation and hunting.

What to verify: Confirm whether the vulnerable software is actually installed, whether the affected endpoints are still in use, and whether any suspicious document activity occurred before the fix. If patching happened after user exposure, preserve the relevant endpoint and email evidence before cleaning up.

Practitioner takeaway: The operational question is not whether the vulnerability is “important”, it is whether any reachable endpoint still gives an attacker a practical document-based path to code execution.

Deepen Your Knowledge

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 19, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org