VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-0659 | suse_vex | SUSE CVE CVE-2016-0659 | known not affected: 121 | 2026-08-01T23:39:07+00:00 | Vulnerability · Source |
| CVE-2016-0799 | suse_vex | SUSE CVE CVE-2016-0799 | known affected: 1 known not affected: 136 recommended: 281 | 2026-08-01T23:39:05+00:00 | Vulnerability · Source |
| CVE-2016-1255 | suse_vex | SUSE CVE CVE-2016-1255 | known affected: 18 known not affected: 11 | 2026-08-01T23:39:04+00:00 | Vulnerability · Source |
| CVE-2016-1405 | suse_vex | SUSE CVE CVE-2016-1405 | known not affected: 9 | 2026-08-01T23:39:02+00:00 | Vulnerability · Source |
| CVE-2016-1621 | suse_vex | SUSE CVE CVE-2016-1621 | known not affected: 45 recommended: 146 | 2026-08-01T23:39:01+00:00 | Vulnerability · Source |
| CVE-2016-1836 | suse_vex | SUSE CVE CVE-2016-1836 | known not affected: 207 recommended: 420 | 2026-08-01T23:39:00+00:00 | Vulnerability · Source |
| CVE-2016-1935 | suse_vex | SUSE CVE CVE-2016-1935 | known affected: 1 recommended: 644 | 2026-08-01T23:38:58+00:00 | Vulnerability · Source |
| CVE-2016-2113 | suse_vex | SUSE CVE CVE-2016-2113 | known affected: 321 known not affected: 90 recommended: 4427 | 2026-08-01T23:38:55+00:00 | Vulnerability · Source |
| CVE-2016-2143 | suse_vex | SUSE CVE CVE-2016-2143 | known affected: 24 known not affected: 186 recommended: 383 | 2026-08-01T23:38:53+00:00 | Vulnerability · Source |
| CVE-2016-2180 | suse_vex | SUSE CVE CVE-2016-2180 | known affected: 320 known not affected: 598 recommended: 958 | 2026-08-01T23:38:52+00:00 | Vulnerability · Source |
| CVE-2016-2572 | suse_vex | SUSE CVE CVE-2016-2572 | known affected: 3 known not affected: 33 recommended: 49 | 2026-08-01T23:38:50+00:00 | Vulnerability · Source |
| CVE-2016-2812 | suse_vex | SUSE CVE CVE-2016-2812 | known affected: 1 known not affected: 42 recommended: 246 | 2026-08-01T23:38:48+00:00 | Vulnerability · Source |
| CVE-2016-2832 | suse_vex | SUSE CVE CVE-2016-2832 | known affected: 1 known not affected: 41 recommended: 250 | 2026-08-01T23:38:47+00:00 | Vulnerability · Source |
| CVE-2016-3990 | suse_vex | SUSE CVE CVE-2016-3990 | known affected: 394 known not affected: 291 recommended: 285 | 2026-08-01T23:38:45+00:00 | Vulnerability · Source |
| CVE-2016-4486 | suse_vex | SUSE CVE CVE-2016-4486 | known affected: 24 known not affected: 188 recommended: 529 | 2026-08-01T23:38:43+00:00 | Vulnerability · Source |
| CVE-2016-4564 | suse_vex | SUSE CVE CVE-2016-4564 | known affected: 97 recommended: 202 | 2026-08-01T23:38:42+00:00 | Vulnerability · Source |
| CVE-2016-4692 | suse_vex | SUSE CVE CVE-2016-4692 | known not affected: 87 recommended: 939 | 2026-08-01T23:38:40+00:00 | Vulnerability · Source |
| CVE-2016-4962 | suse_vex | SUSE CVE CVE-2016-4962 | known affected: 1 known not affected: 3 recommended: 63 | 2026-08-01T23:38:39+00:00 | Vulnerability · Source |
| CVE-2016-5131 | suse_vex | SUSE CVE CVE-2016-5131 | known affected: 394 recommended: 164 | 2026-08-01T23:38:37+00:00 | Vulnerability · Source |
| CVE-2016-5241 | suse_vex | SUSE CVE CVE-2016-5241 | known affected: 3 known not affected: 46 recommended: 14 | 2026-08-01T23:38:36+00:00 | Vulnerability · Source |
| CVE-2016-5283 | suse_vex | SUSE CVE CVE-2016-5283 | known affected: 5 recommended: 250 | 2026-08-01T23:38:34+00:00 | Vulnerability · Source |
| CVE-2016-5403 | suse_vex | SUSE CVE CVE-2016-5403 | known affected: 396 known not affected: 163 recommended: 1906 | 2026-08-01T23:38:33+00:00 | Vulnerability · Source |
| CVE-2016-5440 | suse_vex | SUSE CVE CVE-2016-5440 | known affected: 1 known not affected: 44 recommended: 681 | 2026-08-01T23:38:31+00:00 | Vulnerability · Source |
| CVE-2016-5824 | suse_vex | SUSE CVE CVE-2016-5824 | known affected: 1 recommended: 335 | 2026-08-01T23:38:30+00:00 | Vulnerability · Source |
| CVE-2016-6198 | suse_vex | SUSE CVE CVE-2016-6198 | known affected: 3 known not affected: 488 recommended: 12 | 2026-08-01T23:38:28+00:00 | Vulnerability · Source |
| CVE-2016-6223 | suse_vex | SUSE CVE CVE-2016-6223 | known affected: 457 recommended: 263 | 2026-08-01T23:38:27+00:00 | Vulnerability · Source |
| CVE-2016-6263 | suse_vex | SUSE CVE CVE-2016-6263 | known affected: 321 recommended: 796 | 2026-08-01T23:38:26+00:00 | Vulnerability · Source |
| CVE-2016-6328 | suse_vex | SUSE CVE CVE-2016-6328 | known affected: 27 known not affected: 14 recommended: 223 | 2026-08-01T23:38:24+00:00 | Vulnerability · Source |
| CVE-2016-6663 | suse_vex | SUSE CVE CVE-2016-6663 | recommended: 610 | 2026-08-01T23:38:23+00:00 | Vulnerability · Source |
| CVE-2016-7032 | suse_vex | SUSE CVE CVE-2016-7032 | known affected: 320 known not affected: 112 recommended: 319 | 2026-08-01T23:38:21+00:00 | Vulnerability · Source |
| CVE-2016-7166 | suse_vex | SUSE CVE CVE-2016-7166 | known affected: 30 known not affected: 108 recommended: 4 | 2026-08-01T23:38:19+00:00 | Vulnerability · Source |
| CVE-2016-7175 | suse_vex | SUSE CVE CVE-2016-7175 | known affected: 1 recommended: 586 | 2026-08-01T23:38:18+00:00 | Vulnerability · Source |
| CVE-2016-7422 | suse_vex | SUSE CVE CVE-2016-7422 | known affected: 420 known not affected: 178 recommended: 1754 | 2026-08-01T23:38:16+00:00 | Vulnerability · Source |
| CVE-2016-7520 | suse_vex | SUSE CVE CVE-2016-7520 | known affected: 94 known not affected: 51 recommended: 132 | 2026-08-01T23:38:15+00:00 | Vulnerability · Source |
| CVE-2016-7568 | suse_vex | SUSE CVE CVE-2016-7568 | known affected: 550 known not affected: 139 recommended: 1130 | 2026-08-01T23:38:14+00:00 | Vulnerability · Source |
| CVE-2016-7586 | suse_vex | SUSE CVE CVE-2016-7586 | known not affected: 87 recommended: 927 | 2026-08-01T23:38:12+00:00 | Vulnerability · Source |
| CVE-2016-7599 | suse_vex | SUSE CVE CVE-2016-7599 | known not affected: 87 recommended: 927 | 2026-08-01T23:38:11+00:00 | Vulnerability · Source |
| CVE-2016-7915 | suse_vex | SUSE CVE CVE-2016-7915 | known not affected: 234 recommended: 203 | 2026-08-01T23:38:09+00:00 | Vulnerability · Source |
| CVE-2016-7940 | suse_vex | SUSE CVE CVE-2016-7940 | known affected: 320 recommended: 186 | 2026-08-01T23:38:08+00:00 | Vulnerability · Source |
| CVE-2016-7944 | suse_vex | SUSE CVE CVE-2016-7944 | known affected: 36 recommended: 270 | 2026-08-01T23:38:07+00:00 | Vulnerability · Source |
| CVE-2016-7948 | suse_vex | SUSE CVE CVE-2016-7948 | known not affected: 62 recommended: 463 | 2026-08-01T23:38:05+00:00 | Vulnerability · Source |
| CVE-2016-8678 | suse_vex | SUSE CVE CVE-2016-8678 | known not affected: 119 | 2026-08-01T23:38:02+00:00 | Vulnerability · Source |
| CVE-2016-8858 | suse_vex | SUSE CVE CVE-2016-8858 | known affected: 339 recommended: 512 | 2026-08-01T23:38:01+00:00 | Vulnerability · Source |
| CVE-2016-9075 | suse_vex | SUSE CVE CVE-2016-9075 | known affected: 1 known not affected: 60 recommended: 321 | 2026-08-01T23:37:59+00:00 | Vulnerability · Source |
| CVE-2016-9112 | suse_vex | SUSE CVE CVE-2016-9112 | recommended: 20 | 2026-08-01T23:37:58+00:00 | Vulnerability · Source |
| CVE-2016-9380 | suse_vex | SUSE CVE CVE-2016-9380 | known affected: 14 known not affected: 6 recommended: 474 | 2026-08-01T23:37:56+00:00 | Vulnerability · Source |
| CVE-2016-9386 | suse_vex | SUSE CVE CVE-2016-9386 | known affected: 334 known not affected: 6 recommended: 556 | 2026-08-01T23:37:55+00:00 | Vulnerability · Source |
| CVE-2016-9401 | suse_vex | SUSE CVE CVE-2016-9401 | known affected: 320 recommended: 686 | 2026-08-01T23:37:54+00:00 | Vulnerability · Source |
| CVE-2016-9430 | suse_vex | SUSE CVE CVE-2016-9430 | known not affected: 15 | 2026-08-01T23:37:53+00:00 | Vulnerability · Source |
| CVE-2016-9778 | suse_vex | SUSE CVE CVE-2016-9778 | known affected: 320 known not affected: 261 recommended: 719 | 2026-08-01T23:37:51+00:00 | Vulnerability · Source |