This page was not yet optimized for use on mobile devices.
Adobe Acrobat 11.0.22
Configuration details
| CPE title | Adobe Acrobat 11.0.22 |
|---|---|
| URI | cpe:2.3:a:adobe:acrobat:11.0.22:*:*:*:*:*:*:* |
Linked CVEs
74 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| 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-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 74.
Matched certificates
This CPE has no matched certificates.