VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285037 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-1908 | suse_vex | SUSE CVE CVE-2016-1908 | known affected: 2 recommended: 107 | 2026-07-26T17:01:19+00:00 | Vulnerability · Source |
| CVE-2016-1930 | suse_vex | SUSE CVE CVE-2016-1930 | known affected: 1 recommended: 644 | 2026-07-26T17:01:17+00:00 | Vulnerability · Source |
| CVE-2016-1942 | suse_vex | SUSE CVE CVE-2016-1942 | known affected: 21 recommended: 250 | 2026-07-26T17:01:16+00:00 | Vulnerability · Source |
| CVE-2016-1960 | suse_vex | SUSE CVE CVE-2016-1960 | known affected: 2 recommended: 648 | 2026-07-26T17:01:14+00:00 | Vulnerability · Source |
| CVE-2016-1962 | suse_vex | SUSE CVE CVE-2016-1962 | known affected: 2 recommended: 642 | 2026-07-26T17:01:12+00:00 | Vulnerability · Source |
| CVE-2016-2807 | suse_vex | SUSE CVE CVE-2016-2807 | known affected: 2 recommended: 500 | 2026-07-26T17:01:09+00:00 | Vulnerability · Source |
| CVE-2016-3426 | suse_vex | SUSE CVE CVE-2016-3426 | known affected: 112 known not affected: 93 recommended: 692 | 2026-07-26T17:01:07+00:00 | Vulnerability · Source |
| CVE-2016-4052 | suse_vex | SUSE CVE CVE-2016-4052 | known affected: 394 known not affected: 55 recommended: 49 | 2026-07-26T17:01:05+00:00 | Vulnerability · Source |
| CVE-2016-4470 | suse_vex | SUSE CVE CVE-2016-4470 | known affected: 50 known not affected: 493 recommended: 548 | 2026-07-26T17:01:02+00:00 | Vulnerability · Source |
| CVE-2016-4797 | suse_vex | SUSE CVE CVE-2016-4797 | known not affected: 143 recommended: 20 | 2026-07-26T17:01:00+00:00 | Vulnerability · Source |
| CVE-2016-4956 | suse_vex | SUSE CVE CVE-2016-4956 | known affected: 31 recommended: 109 | 2026-07-26T17:00:59+00:00 | Vulnerability · Source |
| CVE-2016-5104 | suse_vex | SUSE CVE CVE-2016-5104 | known not affected: 88 recommended: 383 | 2026-07-26T17:00:57+00:00 | Vulnerability · Source |
| CVE-2016-5276 | suse_vex | SUSE CVE CVE-2016-5276 | known affected: 5 recommended: 332 | 2026-07-26T17:00:55+00:00 | Vulnerability · Source |
| CVE-2016-5299 | suse_vex | SUSE CVE CVE-2016-5299 | known affected: 1 known not affected: 38 recommended: 250 | 2026-07-26T17:00:54+00:00 | Vulnerability · Source |
| CVE-2016-5652 | suse_vex | SUSE CVE CVE-2016-5652 | known affected: 394 recommended: 302 | 2026-07-26T17:00:51+00:00 | Vulnerability · Source |
| CVE-2016-5728 | suse_vex | SUSE CVE CVE-2016-5728 | known not affected: 22 | 2026-07-26T17:00:50+00:00 | Vulnerability · Source |
| CVE-2016-6128 | suse_vex | SUSE CVE CVE-2016-6128 | known affected: 1476 known not affected: 1295 recommended: 1329 | 2026-07-26T17:00:48+00:00 | Vulnerability · Source |
| CVE-2016-6509 | suse_vex | SUSE CVE CVE-2016-6509 | known affected: 75 recommended: 533 | 2026-07-26T17:00:46+00:00 | Vulnerability · Source |
| CVE-2016-7154 | suse_vex | SUSE CVE CVE-2016-7154 | known affected: 1 known not affected: 27 recommended: 34 | 2026-07-26T17:00:43+00:00 | Vulnerability · Source |
| CVE-2016-7180 | suse_vex | SUSE CVE CVE-2016-7180 | known affected: 1 recommended: 586 | 2026-07-26T17:00:42+00:00 | Vulnerability · Source |
| CVE-2016-7445 | suse_vex | SUSE CVE CVE-2016-7445 | recommended: 137 | 2026-07-26T17:00:40+00:00 | Vulnerability · Source |
| CVE-2016-7534 | suse_vex | SUSE CVE CVE-2016-7534 | known affected: 94 known not affected: 39 recommended: 132 | 2026-07-26T17:00:38+00:00 | Vulnerability · Source |
| CVE-2016-7932 | suse_vex | SUSE CVE CVE-2016-7932 | known affected: 320 recommended: 182 | 2026-07-26T17:00:36+00:00 | Vulnerability · Source |
| CVE-2016-7937 | suse_vex | SUSE CVE CVE-2016-7937 | known affected: 320 recommended: 186 | 2026-07-26T17:00:35+00:00 | Vulnerability · Source |
| CVE-2016-7945 | suse_vex | SUSE CVE CVE-2016-7945 | known affected: 36 recommended: 270 | 2026-07-26T17:00:33+00:00 | Vulnerability · Source |
| CVE-2016-7993 | suse_vex | SUSE CVE CVE-2016-7993 | known affected: 320 recommended: 186 | 2026-07-26T17:00:32+00:00 | Vulnerability · Source |
| CVE-2016-7997 | suse_vex | SUSE CVE CVE-2016-7997 | known affected: 97 recommended: 190 | 2026-07-26T17:00:30+00:00 | Vulnerability · Source |
| CVE-2016-8617 | suse_vex | SUSE CVE CVE-2016-8617 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T17:00:28+00:00 | Vulnerability · Source |
| CVE-2016-8635 | suse_vex | SUSE CVE CVE-2016-8635 | known affected: 1 recommended: 519 | 2026-07-26T17:00:27+00:00 | Vulnerability · Source |
| CVE-2016-8885 | suse_vex | SUSE CVE CVE-2016-8885 | known affected: 1 recommended: 204 | 2026-07-26T17:00:25+00:00 | Vulnerability · Source |
| CVE-2016-9440 | suse_vex | SUSE CVE CVE-2016-9440 | known affected: 1 recommended: 87 | 2026-07-26T17:00:22+00:00 | Vulnerability · Source |
| CVE-2016-9579 | suse_vex | SUSE CVE CVE-2016-9579 | known not affected: 20 recommended: 42 | 2026-07-26T17:00:21+00:00 | Vulnerability · Source |
| CVE-2016-9754 | suse_vex | SUSE CVE CVE-2016-9754 | known not affected: 34 | 2026-07-26T17:00:19+00:00 | Vulnerability · Source |
| CVE-2016-9803 | suse_vex | SUSE CVE CVE-2016-9803 | known affected: 1 known not affected: 140 recommended: 36 | 2026-07-26T17:00:18+00:00 | Vulnerability · Source |
| CVE-2016-9923 | suse_vex | SUSE CVE CVE-2016-9923 | known not affected: 136 recommended: 1641 | 2026-07-26T17:00:15+00:00 | Vulnerability · Source |
| CVE-2016-10169 | suse_vex | SUSE CVE CVE-2016-10169 | known affected: 30 recommended: 57 | 2026-07-26T17:00:13+00:00 | Vulnerability · Source |
| CVE-2016-10251 | suse_vex | SUSE CVE CVE-2016-10251 | known affected: 37 known not affected: 113 recommended: 204 | 2026-07-26T17:00:11+00:00 | Vulnerability · Source |
| CVE-2016-10268 | suse_vex | SUSE CVE CVE-2016-10268 | known affected: 441 known not affected: 80 recommended: 298 | 2026-07-26T17:00:09+00:00 | Vulnerability · Source |
| CVE-2016-10371 | suse_vex | SUSE CVE CVE-2016-10371 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T17:00:07+00:00 | Vulnerability · Source |
| CVE-2017-2354 | suse_vex | SUSE CVE CVE-2017-2354 | known not affected: 248 recommended: 927 | 2026-07-26T17:00:05+00:00 | Vulnerability · Source |
| CVE-2017-2587 | suse_vex | SUSE CVE CVE-2017-2587 | known affected: 16 recommended: 56 | 2026-07-26T17:00:04+00:00 | Vulnerability · Source |
| CVE-2017-3231 | suse_vex | SUSE CVE CVE-2017-3231 | known affected: 124 known not affected: 166 recommended: 584 | 2026-07-26T17:00:02+00:00 | Vulnerability · Source |
| CVE-2017-3289 | suse_vex | SUSE CVE CVE-2017-3289 | known affected: 114 known not affected: 166 recommended: 584 | 2026-07-26T17:00:00+00:00 | Vulnerability · Source |
| CVE-2017-3639 | suse_vex | SUSE CVE CVE-2017-3639 | known affected: 1 known not affected: 64 | 2026-07-26T16:59:58+00:00 | Vulnerability · Source |
| CVE-2017-5465 | suse_vex | SUSE CVE CVE-2017-5465 | known not affected: 42 recommended: 770 | 2026-07-26T16:59:56+00:00 | Vulnerability · Source |
| CVE-2017-5563 | suse_vex | SUSE CVE CVE-2017-5563 | known not affected: 47 | 2026-07-26T16:59:54+00:00 | Vulnerability · Source |
| CVE-2017-5898 | suse_vex | SUSE CVE CVE-2017-5898 | known affected: 394 known not affected: 156 recommended: 1923 | 2026-07-26T16:59:52+00:00 | Vulnerability · Source |
| CVE-2017-6004 | suse_vex | SUSE CVE CVE-2017-6004 | known affected: 349 known not affected: 521 recommended: 731 | 2026-07-26T16:59:50+00:00 | Vulnerability · Source |
| CVE-2017-6210 | suse_vex | SUSE CVE CVE-2017-6210 | recommended: 29 | 2026-07-26T16:59:48+00:00 | Vulnerability · Source |
| CVE-2017-6505 | suse_vex | SUSE CVE CVE-2017-6505 | known affected: 320 known not affected: 212 recommended: 2310 | 2026-07-26T16:59:46+00:00 | Vulnerability · Source |