VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287961 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-11069 | suse_vex | SUSE CVE CVE-2016-11069 | recommended: 1 | 2026-07-31T01:46:58+00:00 | Vulnerability · Source |
| CVE-2017-0641 | suse_vex | SUSE CVE CVE-2017-0641 | known not affected: 159 recommended: 146 | 2026-07-31T01:46:56+00:00 | Vulnerability · Source |
| CVE-2017-0750 | suse_vex | SUSE CVE CVE-2017-0750 | known not affected: 48 | 2026-07-31T01:46:55+00:00 | Vulnerability · Source |
| CVE-2017-0900 | suse_vex | SUSE CVE CVE-2017-0900 | known not affected: 54 recommended: 98 | 2026-07-31T01:46:53+00:00 | Vulnerability · Source |
| CVE-2017-2350 | suse_vex | SUSE CVE CVE-2017-2350 | known not affected: 248 recommended: 939 | 2026-07-31T01:46:51+00:00 | Vulnerability · Source |
| CVE-2017-2583 | suse_vex | SUSE CVE CVE-2017-2583 | known affected: 12 known not affected: 290 recommended: 234 | 2026-07-31T01:46:50+00:00 | Vulnerability · Source |
| CVE-2017-2624 | suse_vex | SUSE CVE CVE-2017-2624 | known affected: 394 known not affected: 180 recommended: 276 | 2026-07-31T01:46:48+00:00 | Vulnerability · Source |
| CVE-2017-2814 | suse_vex | SUSE CVE CVE-2017-2814 | known not affected: 93 | 2026-07-31T01:46:46+00:00 | Vulnerability · Source |
| CVE-2017-3258 | suse_vex | SUSE CVE CVE-2017-3258 | known affected: 1 known not affected: 93 recommended: 667 | 2026-07-31T01:46:44+00:00 | Vulnerability · Source |
| CVE-2017-3329 | suse_vex | SUSE CVE CVE-2017-3329 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-31T01:46:42+00:00 | Vulnerability · Source |
| CVE-2017-3733 | suse_vex | SUSE CVE CVE-2017-3733 | known not affected: 69 recommended: 9 | 2026-07-31T01:46:40+00:00 | Vulnerability · Source |
| CVE-2017-3736 | suse_vex | SUSE CVE CVE-2017-3736 | known affected: 356 known not affected: 368 recommended: 1258 | 2026-07-31T01:46:38+00:00 | Vulnerability · Source |
| CVE-2017-5204 | suse_vex | SUSE CVE CVE-2017-5204 | known affected: 320 recommended: 186 | 2026-07-31T01:46:36+00:00 | Vulnerability · Source |
| CVE-2017-5379 | suse_vex | SUSE CVE CVE-2017-5379 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-31T01:46:34+00:00 | Vulnerability · Source |
| CVE-2017-5433 | suse_vex | SUSE CVE CVE-2017-5433 | known not affected: 42 recommended: 770 | 2026-07-31T01:46:32+00:00 | Vulnerability · Source |
| CVE-2017-5495 | suse_vex | SUSE CVE CVE-2017-5495 | known affected: 1 known not affected: 125 recommended: 350 | 2026-07-31T01:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5550 | suse_vex | SUSE CVE CVE-2017-5550 | known not affected: 48 | 2026-07-31T01:46:29+00:00 | Vulnerability · Source |
| CVE-2017-5651 | suse_vex | SUSE CVE CVE-2017-5651 | known not affected: 54 | 2026-07-31T01:46:27+00:00 | Vulnerability · Source |
| CVE-2017-5953 | suse_vex | SUSE CVE CVE-2017-5953 | known affected: 320 recommended: 485 | 2026-07-31T01:46:25+00:00 | Vulnerability · Source |
| CVE-2017-5970 | suse_vex | SUSE CVE CVE-2017-5970 | known affected: 63 known not affected: 720 recommended: 483 | 2026-07-31T01:46:23+00:00 | Vulnerability · Source |
| CVE-2017-6314 | suse_vex | SUSE CVE CVE-2017-6314 | known not affected: 540 recommended: 129 | 2026-07-31T01:46:21+00:00 | Vulnerability · Source |
| CVE-2017-6464 | suse_vex | SUSE CVE CVE-2017-6464 | known affected: 31 recommended: 103 | 2026-07-31T01:46:20+00:00 | Vulnerability · Source |
| CVE-2017-6474 | suse_vex | SUSE CVE CVE-2017-6474 | known affected: 73 recommended: 444 | 2026-07-31T01:46:18+00:00 | Vulnerability · Source |
| CVE-2017-6888 | suse_vex | SUSE CVE CVE-2017-6888 | known affected: 394 known not affected: 219 recommended: 242 | 2026-07-31T01:46:16+00:00 | Vulnerability · Source |
| CVE-2017-7207 | suse_vex | SUSE CVE CVE-2017-7207 | known affected: 37 known not affected: 60 recommended: 285 | 2026-07-31T01:46:14+00:00 | Vulnerability · Source |
| CVE-2017-7303 | suse_vex | SUSE CVE CVE-2017-7303 | known affected: 442 known not affected: 54 recommended: 340 | 2026-07-31T01:46:12+00:00 | Vulnerability · Source |
| CVE-2017-7396 | suse_vex | SUSE CVE CVE-2017-7396 | recommended: 34 | 2026-07-31T01:46:08+00:00 | Vulnerability · Source |
| CVE-2017-7436 | suse_vex | SUSE CVE CVE-2017-7436 | known affected: 354 known not affected: 30 recommended: 504 | 2026-07-31T01:46:07+00:00 | Vulnerability · Source |
| CVE-2017-7478 | suse_vex | SUSE CVE CVE-2017-7478 | known affected: 30 recommended: 41 | 2026-07-31T01:46:05+00:00 | Vulnerability · Source |
| CVE-2017-7493 | suse_vex | SUSE CVE CVE-2017-7493 | known affected: 394 known not affected: 220 recommended: 1812 | 2026-07-31T01:46:03+00:00 | Vulnerability · Source |
| CVE-2017-7500 | suse_vex | SUSE CVE CVE-2017-7500 | known affected: 448 known not affected: 147 recommended: 416 | 2026-07-31T01:46:01+00:00 | Vulnerability · Source |
| CVE-2017-7562 | suse_vex | SUSE CVE CVE-2017-7562 | known not affected: 220 recommended: 39 | 2026-07-31T01:46:00+00:00 | Vulnerability · Source |
| CVE-2017-7593 | suse_vex | SUSE CVE CVE-2017-7593 | known affected: 439 known not affected: 80 recommended: 286 | 2026-07-31T01:45:58+00:00 | Vulnerability · Source |
| CVE-2017-7596 | suse_vex | SUSE CVE CVE-2017-7596 | known affected: 439 known not affected: 80 recommended: 286 | 2026-07-31T01:45:56+00:00 | Vulnerability · Source |
| CVE-2017-7606 | suse_vex | SUSE CVE CVE-2017-7606 | recommended: 184 | 2026-07-31T01:45:55+00:00 | Vulnerability · Source |
| CVE-2017-7697 | suse_vex | SUSE CVE CVE-2017-7697 | known affected: 6 known not affected: 100 recommended: 14 | 2026-07-31T01:45:53+00:00 | Vulnerability · Source |
| CVE-2017-7750 | suse_vex | SUSE CVE CVE-2017-7750 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-31T01:45:51+00:00 | Vulnerability · Source |
| CVE-2017-7758 | suse_vex | SUSE CVE CVE-2017-7758 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-31T01:45:50+00:00 | Vulnerability · Source |
| CVE-2017-7786 | suse_vex | SUSE CVE CVE-2017-7786 | known affected: 1 known not affected: 42 recommended: 417 | 2026-07-31T01:45:48+00:00 | Vulnerability · Source |
| CVE-2017-7810 | suse_vex | SUSE CVE CVE-2017-7810 | known not affected: 42 recommended: 650 | 2026-07-31T01:45:46+00:00 | Vulnerability · Source |
| CVE-2017-7858 | suse_vex | SUSE CVE CVE-2017-7858 | known affected: 6 known not affected: 52 | 2026-07-31T01:45:44+00:00 | Vulnerability · Source |
| CVE-2017-8344 | suse_vex | SUSE CVE CVE-2017-8344 | recommended: 184 | 2026-07-31T01:45:43+00:00 | Vulnerability · Source |
| CVE-2017-8346 | suse_vex | SUSE CVE CVE-2017-8346 | recommended: 184 | 2026-07-31T01:45:41+00:00 | Vulnerability · Source |
| CVE-2017-8349 | suse_vex | SUSE CVE CVE-2017-8349 | recommended: 184 | 2026-07-31T01:45:39+00:00 | Vulnerability · Source |
| CVE-2017-8394 | suse_vex | SUSE CVE CVE-2017-8394 | known affected: 394 known not affected: 23 recommended: 340 | 2026-07-31T01:45:38+00:00 | Vulnerability · Source |
| CVE-2017-9122 | suse_vex | SUSE CVE CVE-2017-9122 | known affected: 30 recommended: 208 | 2026-07-31T01:45:34+00:00 | Vulnerability · Source |
| CVE-2017-9128 | suse_vex | SUSE CVE CVE-2017-9128 | known affected: 30 recommended: 208 | 2026-07-31T01:45:32+00:00 | Vulnerability · Source |
| CVE-2017-9208 | suse_vex | SUSE CVE CVE-2017-9208 | known affected: 4 known not affected: 33 recommended: 326 | 2026-07-31T01:45:31+00:00 | Vulnerability · Source |
| CVE-2017-9353 | suse_vex | SUSE CVE CVE-2017-9353 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-31T01:45:29+00:00 | Vulnerability · Source |
| CVE-2017-9433 | suse_vex | SUSE CVE CVE-2017-9433 | known not affected: 8 recommended: 2376 | 2026-07-31T01:45:27+00:00 | Vulnerability · Source |