reader is a software product developed by adobe, a major technology provider with a global presence in enterprise and consumer markets. This product is widely deployed in production environments, making vulnerability monitoring essential for organizations relying on it. Security vulnerabilities in products of this category can affect system availability, data confidentiality, and integrity across entire networks. The significant number of reported vulnerabilities indicates this product has received substantial security scrutiny and community focus over time. Regular assessment of known vulnerabilities and timely patching are fundamental components of responsible system administration for any deployment of this software.
SecUtils has identified 360 known vulnerabilities affecting adobe reader. This includes 195 critical-severity issues and 127 high-severity issues that warrant immediate attention. Vulnerabilities in this product have been disclosed spanning from 2009 to 2019, indicating a sustained research interest and ongoing security attention. 31 medium-severity issues and 7 low-severity issues complete the vulnerability landscape. Organizations should prioritize patching based on deployment context, asset criticality, and exploitation likelihood rather than severity alone.
| ID | Date Published | Last Modified | Severity (CVSSv3) | Severity (CVSSv2) | Exploit Available |
|---|---|---|---|---|---|
| CVE-2009-1062 | 2009-03-25 | 2025-04-09 | - | 9.3 | Likely |
| CVE-2009-1493 | 2009-04-30 | 2025-04-09 | - | 6.8 | Likely |
| CVE-2009-3459 | 2009-10-13 | 2025-04-09 | - | 9.3 | Likely |
| CVE-2010-1278 | 2010-04-22 | 2025-04-11 | - | 9.3 | Likely |
| CVE-2011-4370 | 2012-01-10 | 2025-04-11 | - | 7.5 | Likely |
| CVE-2011-4371 | 2012-01-10 | 2025-04-11 | - | 7.5 | Likely |
| CVE-2011-4372 | 2012-01-10 | 2025-04-11 | 9.8 | 7.5 | Likely |
| CVE-2011-4373 | 2012-01-10 | 2025-04-11 | 9.8 | 7.5 | Likely |
| CVE-2011-4374 | 2012-01-19 | 2025-04-11 | - | 9.3 | Likely |
| CVE-2016-1037 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1038 | 2016-05-11 | 2025-04-12 | 10.0 | 10.0 | Likely |
| CVE-2016-1039 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1040 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1041 | 2016-05-11 | 2025-04-12 | 10.0 | 10.0 | Likely |
| CVE-2016-1042 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1043 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1044 | 2016-05-11 | 2025-04-12 | 10.0 | 10.0 | Likely |
| CVE-2016-1045 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1046 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1047 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1048 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1049 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1050 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1051 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1052 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1053 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1054 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1055 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1056 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1057 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1058 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1059 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1060 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1061 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1062 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1063 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1064 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1065 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1066 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1067 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1068 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1069 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1070 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1071 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1072 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1073 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1074 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1076 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1077 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1078 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1079 | 2016-05-11 | 2025-04-12 | 7.5 | 5.0 | Likely |
| CVE-2016-1080 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1081 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1082 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1083 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1084 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1085 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1086 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1087 | 2016-05-11 | 2025-04-12 | 7.8 | 7.2 | Unknown |
| CVE-2016-1088 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1090 | 2016-05-11 | 2025-04-12 | 7.8 | 7.2 | Unknown |
| CVE-2016-1092 | 2016-05-11 | 2025-04-12 | 7.5 | 5.0 | Likely |
| CVE-2016-1093 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1095 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1112 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1116 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1117 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1118 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1119 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1120 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1122 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1123 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1124 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1125 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1126 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1127 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1128 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1129 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1130 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4088 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4089 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4090 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4091 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4092 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4093 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4094 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4096 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4097 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4098 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4099 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4100 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4101 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4102 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4103 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4104 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4105 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4106 | 2016-05-11 | 2025-04-12 | 7.8 | 7.2 | Unknown |
| CVE-2016-4107 | 2016-05-11 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4191 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4192 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4193 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4194 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4195 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4196 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4197 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4198 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4199 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4200 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4201 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4202 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4203 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4204 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4205 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4206 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4207 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4208 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4209 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4210 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4211 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4212 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4213 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4214 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4215 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4250 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4251 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4252 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4254 | 2016-07-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4255 | 2016-07-13 | 2025-04-12 | 8.8 | 6.8 | Likely |
| CVE-2016-4119 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4265 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4266 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4267 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4268 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4269 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4270 | 2016-08-26 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6937 | 2016-09-17 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6938 | 2016-09-17 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1089 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-1091 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6939 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6940 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6941 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6942 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6943 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6944 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6945 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6946 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6947 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6948 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6949 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6950 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6951 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6952 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6953 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6954 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6955 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6956 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6957 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6958 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6959 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6960 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6961 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6962 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6963 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6964 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6965 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6966 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6967 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6968 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6969 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6970 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6971 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6972 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6973 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6974 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6975 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6976 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6977 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6978 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6979 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6988 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6993 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6994 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6995 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6996 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6997 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6998 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-6999 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7000 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7001 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7002 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7003 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7004 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7005 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7006 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7007 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7008 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7009 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7010 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7011 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7012 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7013 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7014 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7015 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7016 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7017 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7018 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7019 | 2016-10-13 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7852 | 2016-10-21 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7853 | 2016-10-21 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-7854 | 2016-10-21 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2016-4095 | 2016-11-10 | 2025-04-12 | 9.8 | 10.0 | Likely |
| CVE-2017-2939 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2940 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2941 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2942 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2943 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2944 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2945 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2946 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2947 | 2017-01-11 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-2948 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2949 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2950 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2951 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2952 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2953 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2954 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2955 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2956 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2957 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2958 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2959 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2960 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2961 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2962 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2963 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2964 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2965 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2966 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2967 | 2017-01-11 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2970 | 2017-01-24 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2971 | 2017-01-24 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-2972 | 2017-01-24 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3009 | 2017-03-31 | 2025-04-20 | 7.5 | 5.0 | Likely |
| CVE-2017-3010 | 2017-03-31 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-3011 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3012 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3013 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3014 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3015 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3017 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3018 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3019 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3020 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3021 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3022 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3023 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3024 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3025 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3026 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3027 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3028 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3029 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3030 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3031 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3032 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3033 | 2017-04-12 | 2025-04-20 | 3.3 | 4.3 | Likely |
| CVE-2017-3034 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3035 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3036 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3037 | 2017-04-12 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2017-3038 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3039 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3040 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3041 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3042 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3043 | 2017-04-12 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-3044 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3045 | 2017-04-12 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-3046 | 2017-04-12 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-3047 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3048 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3049 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3050 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3051 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3052 | 2017-04-12 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-3053 | 2017-04-12 | 2025-04-20 | 5.5 | 4.3 | Likely |
| CVE-2017-3054 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3055 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3056 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3057 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-3065 | 2017-04-12 | 2025-04-20 | 7.8 | 9.3 | Likely |
| CVE-2017-11209 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11210 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11211 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11212 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11214 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11216 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11217 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11218 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11219 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11220 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11221 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11222 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11223 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11224 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11226 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11227 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11228 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11229 | 2017-08-11 | 2025-04-20 | 8.8 | 6.8 | Likely |
| CVE-2017-11230 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11231 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11232 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11233 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11234 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11235 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11236 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11237 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11238 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11239 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11241 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11242 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11243 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11244 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11245 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11246 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11248 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11249 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11251 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11252 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11254 | 2017-08-11 | 2025-04-20 | 8.8 | 6.8 | Likely |
| CVE-2017-11255 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11256 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11257 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11258 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11259 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11260 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11261 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11262 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11263 | 2017-08-11 | 2025-04-20 | 8.8 | 6.8 | Likely |
| CVE-2017-11265 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-11267 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11268 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11269 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11270 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-11271 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3016 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3113 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3115 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-3116 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3117 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3118 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-3119 | 2017-08-11 | 2025-04-20 | 8.8 | 6.8 | Likely |
| CVE-2017-3120 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3121 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3122 | 2017-08-11 | 2025-04-20 | 6.5 | 4.3 | Likely |
| CVE-2017-3123 | 2017-08-11 | 2025-04-20 | 8.8 | 9.3 | Likely |
| CVE-2017-3124 | 2017-08-11 | 2025-04-20 | 9.8 | 10.0 | Likely |
| CVE-2018-16042 | 2019-01-18 | 2024-11-21 | 6.5 | 6.4 | Likely |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records for adobe reader by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and structuring the data for rapid analysis and asset correlation. For every vulnerability listed, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference information to enable organizations to prioritize patching and risk assessment efficiently. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for vulnerability management and security operations.