Adobe Reader and Acrobat 9.x before 9.5.4, 10.x before 10.1.6, and 11.x before 11.0.02 allow remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted PDF document, as exploited in the wild in February 2013.
CVE-2013-0640
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-03-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0(high)
- EPSS
- 99.7%
- KEV
- ⚠ Exploited
Published
February 14, 2013
Last Modified
April 21, 2026
Advisory Details (4)
Auto-updated May 19, 2026VU#422807 - Adobe Reader and Acrobat memory corruption vulnerabilities
http://www.kb.cert.org/vuls/id/422807Adobe - Security Advisories: APSA13-02 - Security Advisory for Adobe Reader and Acrobat
http://www.adobe.com/support/security/advisories/apsa13-02.htmlAdobe Reader: Multiple vulnerabilities (GLSA 201308-03) — Gentoo security
http://security.gentoo.org/glsa/glsa-201308-03.xmlPatch Availability(1)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | acroread-0:9.5.4-1.el6 | 2013-02-21 | redhat |
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 132× in last 7d / 574× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.
Showing the most recent 100 of 768 total refreshes for this CVE.
- 2026-07-07 20:47 UTCEG score recompute
- 2026-07-07 20:47 UTCVendor advisory
- 2026-07-07 20:47 UTCGHSA enrichment
- 2026-07-07 19:01 UTCCISA KEV update
- 2026-07-07 17:16 UTCCISA KEV update
- 2026-07-07 16:53 UTCEG score recompute
- 2026-07-07 16:53 UTCVendor advisory
- 2026-07-07 16:53 UTCGHSA enrichment
- 2026-07-07 12:59 UTCEG score recompute
- 2026-07-07 12:59 UTCVendor advisory
- 2026-07-07 12:59 UTCGHSA enrichment
- 2026-07-07 09:04 UTCEG score recompute
- 2026-07-07 09:04 UTCVendor advisory
- 2026-07-07 09:04 UTCGHSA enrichment
- 2026-07-07 05:11 UTCEG score recompute
- 2026-07-07 05:11 UTCVendor advisory
- 2026-07-07 05:10 UTCGHSA enrichment
- 2026-07-07 01:15 UTCEG score recompute
- 2026-07-07 01:15 UTCVendor advisory
- 2026-07-07 01:15 UTCGHSA enrichment
- 2026-07-06 21:21 UTCEG score recompute
- 2026-07-06 21:21 UTCVendor advisory
- 2026-07-06 21:21 UTCGHSA enrichment
- 2026-07-06 17:26 UTCEG score recompute
- 2026-07-06 17:26 UTCVendor advisory
Show 75 moreShow fewer
- 2026-07-06 17:26 UTCGHSA enrichment
- 2026-07-06 13:30 UTCEG score recompute
- 2026-07-06 13:30 UTCVendor advisory
- 2026-07-06 13:30 UTCGHSA enrichment
- 2026-07-06 09:35 UTCEG score recompute
- 2026-07-06 09:35 UTCVendor advisory
- 2026-07-06 09:35 UTCGHSA enrichment
- 2026-07-06 05:40 UTCEG score recompute
- 2026-07-06 05:40 UTCVendor advisory
- 2026-07-06 05:40 UTCGHSA enrichment
- 2026-07-06 01:44 UTCEG score recompute
- 2026-07-06 01:44 UTCVendor advisory
- 2026-07-06 01:44 UTCGHSA enrichment
- 2026-07-05 21:50 UTCEG score recompute
- 2026-07-05 21:50 UTCVendor advisory
- 2026-07-05 21:50 UTCGHSA enrichment
- 2026-07-05 17:56 UTCEG score recompute
- 2026-07-05 17:56 UTCVendor advisory
- 2026-07-05 17:56 UTCGHSA enrichment
- 2026-07-05 14:02 UTCEG score recompute
- 2026-07-05 14:02 UTCVendor advisory
- 2026-07-05 14:02 UTCGHSA enrichment
- 2026-07-05 10:06 UTCEG score recompute
- 2026-07-05 10:06 UTCVendor advisory
- 2026-07-05 10:06 UTCGHSA enrichment
- 2026-07-05 06:12 UTCEG score recompute
- 2026-07-05 06:12 UTCVendor advisory
- 2026-07-05 06:11 UTCGHSA enrichment
- 2026-07-05 02:18 UTCEG score recompute
- 2026-07-05 02:18 UTCVendor advisory
- 2026-07-05 02:18 UTCGHSA enrichment
- 2026-07-04 22:24 UTCEG score recompute
- 2026-07-04 22:24 UTCVendor advisory
- 2026-07-04 22:24 UTCGHSA enrichment
- 2026-07-04 18:31 UTCEG score recompute
- 2026-07-04 18:31 UTCVendor advisory
- 2026-07-04 18:30 UTCGHSA enrichment
- 2026-07-04 14:36 UTCEG score recompute
- 2026-07-04 14:36 UTCVendor advisory
- 2026-07-04 14:36 UTCGHSA enrichment
- 2026-07-04 10:43 UTCEG score recompute
- 2026-07-04 10:43 UTCVendor advisory
- 2026-07-04 10:42 UTCGHSA enrichment
- 2026-07-04 06:41 UTCEG score recompute
- 2026-07-04 06:41 UTCVendor advisory
- 2026-07-04 06:41 UTCGHSA enrichment
- 2026-07-04 02:46 UTCEG score recompute
- 2026-07-04 02:46 UTCVendor advisory
- 2026-07-04 02:45 UTCGHSA enrichment
- 2026-07-03 22:51 UTCEG score recompute
- 2026-07-03 22:51 UTCVendor advisory
- 2026-07-03 22:51 UTCGHSA enrichment
- 2026-07-03 18:56 UTCEG score recompute
- 2026-07-03 18:56 UTCVendor advisory
- 2026-07-03 18:56 UTCGHSA enrichment
- 2026-07-03 15:02 UTCEG score recompute
- 2026-07-03 15:02 UTCVendor advisory
- 2026-07-03 15:01 UTCGHSA enrichment
- 2026-07-03 11:07 UTCEG score recompute
- 2026-07-03 11:07 UTCVendor advisory
- 2026-07-03 11:07 UTCGHSA enrichment
- 2026-07-03 07:11 UTCEG score recompute
- 2026-07-03 07:11 UTCVendor advisory
- 2026-07-03 07:11 UTCGHSA enrichment
- 2026-07-03 03:16 UTCEG score recompute
- 2026-07-03 03:16 UTCVendor advisory
- 2026-07-03 03:16 UTCGHSA enrichment
- 2026-07-02 23:21 UTCEG score recompute
- 2026-07-02 23:21 UTCVendor advisory
- 2026-07-02 23:21 UTCGHSA enrichment
- 2026-07-02 19:27 UTCEG score recompute
- 2026-07-02 19:27 UTCVendor advisory
- 2026-07-02 19:27 UTCGHSA enrichment
- 2026-07-02 15:34 UTCEG score recompute
- 2026-07-02 15:34 UTCVendor advisory
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- Exploit-DBEDB-29881✓ verifiedFirst seen Nov 28, 2013
Adobe Acrobat Reader - ASLR + DEP Bypass with Sandbox Bypass
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownredhat
Same CWE
10 shownCWE-787
- CVE-2007-0158EG 9.8CRITICAL
- CVE-2007-0899EG 9.8CRITICAL
- CVE-2011-2462EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2010-20115EG 9.3CRITICAL
- CVE-2010-4398NVD 7.8EG 9.0 KEVEPSS 94%HIGH
- CVE-2010-3333NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-2883NVD 7.3EG 9.0 KEVEPSS 100%HIGH
- CVE-2010-1297NVD 7.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3953NVD 8.8EG 9.0 KEVEPSS 100%HIGH
- CVE-2009-3129NVD 7.8EG 9.0 KEVEPSS 100%HIGH
Frequently asked(6)
What is CVE-2013-0640?
When was CVE-2013-0640 disclosed?
Is CVE-2013-0640 actively exploited?
What is the CVSS score of CVE-2013-0640?
Which products are affected by CVE-2013-0640?
How do I remediate CVE-2013-0640?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2013-0640
Is Your Infrastructure Affected by CVE-2013-0640?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.