This page was not yet optimized for use on mobile devices.
Adobe Acrobat Reader 11.0.12
Configuration details
| CPE title | Adobe Acrobat Reader 11.0.12 |
|---|---|
| URI | cpe:2.3:a:adobe:acrobat_reader:11.0.12:*:*:*:*:*:*:* |
Linked CVEs
154 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2015-5583 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-5586 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-6683 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-6684 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-6685 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6686 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6687 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-6688 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6689 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6690 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6691 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-6692 | MEDIUM | 5.0 | 14.10.2015 | |
| CVE-2015-6693 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6694 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6695 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6696 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6697 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6698 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6699 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-6700 | MEDIUM | 5.0 | 14.10.2015 | |
| CVE-2015-6701 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-6702 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-6703 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-6704 | MEDIUM | 4.3 | 14.10.2015 | |
| CVE-2015-6705 | MEDIUM | 5.0 | 14.10.2015 | |
| CVE-2015-6706 | MEDIUM | 5.0 | 14.10.2015 | |
| CVE-2015-6707 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6708 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6709 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6710 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6711 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6712 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6713 | HIGH | 7.5 | 14.10.2015 | |
| CVE-2015-6714 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6715 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6716 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6717 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6718 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6719 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6720 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6721 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6722 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6723 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6724 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-6725 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7614 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7615 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7616 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7617 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7618 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7619 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7620 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7621 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7622 | HIGH | 10.0 | 14.10.2015 | |
| CVE-2015-7623 | MEDIUM | 6.8 | 14.10.2015 | |
| CVE-2015-7624 | MEDIUM | 5.0 | 14.10.2015 | |
| CVE-2015-7650 | MEDIUM | 6.8 | 04.11.2015 | |
| CVE-2015-7829 | LOW | 1.9 | 15.10.2015 | |
| CVE-2015-8458 | MEDIUM | 6.8 | 21.12.2015 | |
| CVE-2016-0931 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0932 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0933 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0934 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0935 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0936 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0937 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0938 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0939 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0940 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0941 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0942 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0943 | HIGH | 8.8 | 14.01.2016 | |
| CVE-2016-0944 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0945 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0946 | CRITICAL | 9.8 | 14.01.2016 | |
| CVE-2016-0947 | HIGH | 7.8 | 14.01.2016 | |
| CVE-2016-1007 | CRITICAL | 9.8 | 09.03.2016 | |
| CVE-2016-1008 | HIGH | 8.4 | 09.03.2016 | |
| CVE-2016-1009 | CRITICAL | 9.8 | 09.03.2016 | |
| CVE-2017-11240 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-11250 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-11253 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-11293 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-11306 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-11307 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-11308 | CRITICAL | 9.8 | 19.05.2018 | |
| CVE-2017-16360 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16361 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16362 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16363 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16364 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16365 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16366 | HIGH | 7.5 | 09.12.2017 | |
| CVE-2017-16367 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16368 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16369 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16370 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16371 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16372 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16373 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16374 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16375 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16376 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16377 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16378 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16379 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16380 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16381 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16382 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16383 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16384 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16385 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16386 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16387 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16388 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16389 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16390 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16391 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16392 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16393 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16394 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16395 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16396 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16397 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16398 | CRITICAL | 9.8 | 09.12.2017 | |
| CVE-2017-16399 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16400 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16401 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16402 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16403 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16404 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16405 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16406 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16407 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16408 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16409 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16410 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16411 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16412 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16413 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16414 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16415 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16416 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16417 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16418 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2017-16419 | MEDIUM | 6.5 | 09.12.2017 | |
| CVE-2017-16420 | HIGH | 8.8 | 09.12.2017 | |
| CVE-2021-40724 | HIGH | 7.8 | 15.10.2021 | |
| CVE-2026-47911 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47912 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47913 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47914 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47959 | HIGH | 7.8 | 09.06.2026 | |
| CVE-2026-47961 | MEDIUM | 5.5 | 09.06.2026 |
Showing 5 out of 154.
Matched certificates
This CPE has no matched certificates.