CVE-2006-6027 in the critical feed json
Adobe Reader (Adobe Acrobat Reader) 7.0 through 7.0.8 allows remote attackers to cause a denial of service and possibly execute arbitrary c…
published 2006-11-21 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-6010
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 44.7%
- EPSS 44.7% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
Adobe Reader (Adobe Acrobat Reader) 7.0 through 7.0.8 allows remote attackers to cause a denial of service and possibly execute arbitrary code via a long argument string to the LoadFile method in an AcroPDF ActiveX control.
Timeline
- First public exploit (EDB-29076)
- Published
Exploit prediction
44.70% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-29076 Adobe Reader 7.0.x - Multiple Vulnerabilities dos, 2006-11-17
- downloads.securityfocus.com http://downloads.securityfocus.com/vulnerabilities/exploits/21155-AcroPDF_DoS.html referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/21155 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
References
-
downloads.securityfocus.com
/vulnerabilities/exploits/21155-AcroPDF_DoS.html
exploit
-
securityfocus.com
/bid/21155
vdb-entry, exploit
- research.eeye.com /html/alerts/zeroday/20061128.html
-
vupen.com
/english/advisories/2006/4751
vdb-entry
-
secunia.com
/advisories/23138
third-party-advisory
-
kb.cert.org
/vuls/id/198908
third-party-advisory, us-government-resource
- adobe.com /support/security/advisories/apsa06-02.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/30574
vdb-entry
-
securitytracker.com
/id?1017297
vdb-entry
-
securityfocus.com
/archive/1/453579/100/0/threaded
mailing-list
Sources
- CVE List CVE-2006-6027
- NVD CVE-2006-6027
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.