This page was not yet optimized for use on mobile devices.
Adobe Acrobat 9.4.5
Configuration details
| CPE title | Adobe Acrobat 9.4.5 |
|---|---|
| URI | cpe:2.3:a:adobe:acrobat:9.4.5:-:*:*:*:*:*:* |
Linked CVEs
271 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2011-2107 | MEDIUM | 4.3 | 09.06.2011 | |
| CVE-2011-2431 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2432 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2433 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2434 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2435 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2436 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2437 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2438 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2439 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2440 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2441 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2442 | HIGH | 9.3 | 15.09.2011 | |
| CVE-2011-2462 | CRITICAL | 9.8 | 07.12.2011 | |
| CVE-2011-4369 | HIGH | 10.0 | 16.12.2011 | |
| CVE-2011-4370 | HIGH | 7.5 | 10.01.2012 | |
| CVE-2011-4371 | HIGH | 7.5 | 10.01.2012 | |
| CVE-2011-4372 | CRITICAL | 9.8 | 10.01.2012 | |
| CVE-2011-4373 | CRITICAL | 9.8 | 10.01.2012 | |
| CVE-2011-4374 | HIGH | 9.3 | 19.01.2012 | |
| CVE-2012-0774 | HIGH | 10.0 | 10.04.2012 | |
| CVE-2012-0775 | HIGH | 10.0 | 10.04.2012 | |
| CVE-2012-0776 | HIGH | 10.0 | 10.04.2012 | |
| CVE-2012-0777 | MEDIUM | 6.8 | 10.04.2012 | |
| CVE-2012-1525 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-1530 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2012-2049 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-2050 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-2051 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4147 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4148 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4149 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4150 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4151 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4152 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4153 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4154 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4155 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4156 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4157 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4158 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4159 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4160 | HIGH | 10.0 | 15.08.2012 | |
| CVE-2012-4161 | HIGH | 7.5 | 15.08.2012 | |
| CVE-2012-4162 | HIGH | 7.5 | 15.08.2012 | |
| CVE-2013-0601 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0602 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0603 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0604 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0605 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0606 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0607 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0608 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0609 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0610 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0611 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0612 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0613 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0614 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0615 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0616 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0617 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0618 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0619 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0620 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0621 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0622 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0623 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0624 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0626 | HIGH | 10.0 | 10.01.2013 | |
| CVE-2013-0627 | HIGH | 7.2 | 10.01.2013 | |
| CVE-2013-0640 | HIGH | 7.8 | 14.02.2013 | |
| CVE-2013-0641 | HIGH | 7.8 | 14.02.2013 | |
| CVE-2013-1376 | HIGH | 10.0 | 30.01.2014 | |
| CVE-2013-2718 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2719 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2720 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2721 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2722 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2723 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2724 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2725 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2726 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2727 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2729 | CRITICAL | 9.8 | 16.05.2013 | |
| CVE-2013-2730 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2731 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2732 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2733 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2734 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2735 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2736 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-2737 | MEDIUM | 5.0 | 16.05.2013 | |
| CVE-2013-3337 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3338 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3339 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3340 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3341 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3342 | HIGH | 10.0 | 16.05.2013 | |
| CVE-2013-3346 | CRITICAL | 9.8 | 30.08.2013 | |
| CVE-2014-5315 | MEDIUM | 4.3 | 26.09.2014 | |
| CVE-2014-9150 | MEDIUM | 6.4 | 30.11.2014 | |
| 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-2016-1111 | HIGH | 8.8 | 30.04.2016 | |
| CVE-2016-4095 | CRITICAL | 9.8 | 10.11.2016 | |
| CVE-2017-11293 | CRITICAL | 9.8 | 09.12.2017 | |
| 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-2017-2939 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2940 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2941 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2942 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2943 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2944 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2945 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2946 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2947 | MEDIUM | 5.5 | 11.01.2017 | |
| CVE-2017-2948 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2949 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2950 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2951 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2952 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2953 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2954 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2955 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2956 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2957 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2958 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2959 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2960 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2961 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2962 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2963 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2964 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2965 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2966 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2967 | HIGH | 7.8 | 11.01.2017 | |
| CVE-2017-2970 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-2971 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-2972 | HIGH | 7.8 | 24.01.2017 | |
| CVE-2017-3011 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3012 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3013 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3014 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3015 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3017 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3018 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3019 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3020 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3021 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3022 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3023 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3024 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3025 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3026 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3027 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3028 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3029 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3030 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3031 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3032 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3033 | LOW | 3.3 | 12.04.2017 | |
| CVE-2017-3034 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3035 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3036 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3037 | CRITICAL | 9.8 | 12.04.2017 | |
| CVE-2017-3038 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3039 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3040 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3041 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3042 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3043 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3044 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3045 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3046 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3047 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3048 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3049 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3050 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3051 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3052 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3053 | MEDIUM | 5.5 | 12.04.2017 | |
| CVE-2017-3054 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3055 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3056 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3057 | HIGH | 7.8 | 12.04.2017 | |
| CVE-2017-3065 | HIGH | 7.8 | 12.04.2017 | |
| 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 271.
Matched certificates
This CPE has no matched certificates.