VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291913 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-7478 | suse_vex | SUSE CVE CVE-2017-7478 | known affected: 30 recommended: 41 | 2026-07-31T01:46:05+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-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-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 |
| CVE-2017-9746 | suse_vex | SUSE CVE CVE-2017-9746 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-31T01:45:25+00:00 | Vulnerability · Source |
| CVE-2017-9776 | suse_vex | SUSE CVE CVE-2017-9776 | known affected: 52 known not affected: 207 recommended: 165 | 2026-07-31T01:45:23+00:00 | Vulnerability · Source |
| CVE-2017-9985 | suse_vex | SUSE CVE CVE-2017-9985 | known not affected: 510 | 2026-07-31T01:45:22+00:00 | Vulnerability · Source |
| CVE-2017-10320 | suse_vex | SUSE CVE CVE-2017-10320 | known not affected: 237 recommended: 415 | 2026-07-31T01:45:20+00:00 | Vulnerability · Source |
| CVE-2017-10356 | suse_vex | SUSE CVE CVE-2017-10356 | known affected: 497 known not affected: 226 recommended: 758 | 2026-07-31T01:45:18+00:00 | Vulnerability · Source |
| CVE-2017-10664 | suse_vex | SUSE CVE CVE-2017-10664 | known affected: 394 known not affected: 65 recommended: 2005 | 2026-07-31T01:45:16+00:00 | Vulnerability · Source |
| CVE-2017-10684 | suse_vex | SUSE CVE CVE-2017-10684 | known affected: 1 recommended: 231 | 2026-07-31T01:45:15+00:00 | Vulnerability · Source |
| CVE-2017-10784 | suse_vex | SUSE CVE CVE-2017-10784 | known affected: 2 known not affected: 283 recommended: 98 | 2026-07-31T01:45:13+00:00 | Vulnerability · Source |
| CVE-2017-10915 | suse_vex | SUSE CVE CVE-2017-10915 | known affected: 12 known not affected: 104 recommended: 35 | 2026-07-31T01:45:08+00:00 | Vulnerability · Source |
| CVE-2017-10920 | suse_vex | SUSE CVE CVE-2017-10920 | known not affected: 6 recommended: 43 | 2026-07-31T01:45:06+00:00 | Vulnerability · Source |
| CVE-2017-11335 | suse_vex | SUSE CVE CVE-2017-11335 | known not affected: 123 recommended: 22 | 2026-07-31T01:45:04+00:00 | Vulnerability · Source |
| CVE-2017-11352 | suse_vex | SUSE CVE CVE-2017-11352 | known affected: 10 known not affected: 101 | 2026-07-31T01:45:03+00:00 | Vulnerability · Source |
| CVE-2017-11403 | suse_vex | SUSE CVE CVE-2017-11403 | known affected: 60 recommended: 186 | 2026-07-31T01:45:01+00:00 | Vulnerability · Source |
| CVE-2017-11407 | suse_vex | SUSE CVE CVE-2017-11407 | known affected: 86 known not affected: 115 recommended: 565 | 2026-07-31T01:45:00+00:00 | Vulnerability · Source |
| CVE-2017-11505 | suse_vex | SUSE CVE CVE-2017-11505 | known affected: 94 recommended: 186 | 2026-07-31T01:44:58+00:00 | Vulnerability · Source |
| CVE-2017-11534 | suse_vex | SUSE CVE CVE-2017-11534 | recommended: 186 | 2026-07-31T01:44:56+00:00 | Vulnerability · Source |
| CVE-2017-11714 | suse_vex | SUSE CVE CVE-2017-11714 | known affected: 1 recommended: 85 | 2026-07-31T01:44:55+00:00 | Vulnerability · Source |
| CVE-2017-12145 | suse_vex | SUSE CVE CVE-2017-12145 | known affected: 4 known not affected: 91 | 2026-07-31T01:44:53+00:00 | Vulnerability · Source |
| CVE-2017-12183 | suse_vex | SUSE CVE CVE-2017-12183 | known affected: 2 known not affected: 52 recommended: 61 | 2026-07-31T01:44:51+00:00 | Vulnerability · Source |
| CVE-2017-12194 | suse_vex | SUSE CVE CVE-2017-12194 | recommended: 77 | 2026-07-31T01:44:50+00:00 | Vulnerability · Source |
| CVE-2017-12429 | suse_vex | SUSE CVE CVE-2017-12429 | known affected: 95 recommended: 186 | 2026-07-31T01:44:48+00:00 | Vulnerability · Source |
| CVE-2017-12452 | suse_vex | SUSE CVE CVE-2017-12452 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:46+00:00 | Vulnerability · Source |
| CVE-2017-12454 | suse_vex | SUSE CVE CVE-2017-12454 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:45+00:00 | Vulnerability · Source |