VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286392 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-6490 | suse_vex | SUSE CVE CVE-2016-6490 | known affected: 395 known not affected: 240 recommended: 1818 | 2026-07-26T23:45:52+00:00 | Vulnerability · Source |
| CVE-2016-7098 | suse_vex | SUSE CVE CVE-2016-7098 | known affected: 17 recommended: 30 | 2026-07-26T23:45:50+00:00 | Vulnerability · Source |
| CVE-2016-8645 | suse_vex | SUSE CVE CVE-2016-8645 | known not affected: 496 recommended: 222 | 2026-07-26T23:45:48+00:00 | Vulnerability · Source |
| CVE-2016-9624 | suse_vex | SUSE CVE CVE-2016-9624 | known affected: 1 recommended: 87 | 2026-07-26T23:45:45+00:00 | Vulnerability · Source |
| CVE-2016-9808 | suse_vex | SUSE CVE CVE-2016-9808 | known affected: 32 recommended: 86 | 2026-07-26T23:45:44+00:00 | Vulnerability · Source |
| CVE-2016-10028 | suse_vex | SUSE CVE CVE-2016-10028 | known affected: 394 known not affected: 230 recommended: 1754 | 2026-07-26T23:45:42+00:00 | Vulnerability · Source |
| CVE-2016-10057 | suse_vex | SUSE CVE CVE-2016-10057 | known affected: 10 known not affected: 113 | 2026-07-26T23:45:40+00:00 | Vulnerability · Source |
| CVE-2016-10165 | suse_vex | SUSE CVE CVE-2016-10165 | known affected: 26 known not affected: 473 recommended: 717 | 2026-07-26T23:45:38+00:00 | Vulnerability · Source |
| CVE-2017-0564 | suse_vex | SUSE CVE CVE-2017-0564 | known not affected: 64 | 2026-07-26T23:45:35+00:00 | Vulnerability · Source |
| CVE-2017-3514 | suse_vex | SUSE CVE CVE-2017-3514 | known affected: 1 known not affected: 109 recommended: 614 | 2026-07-26T23:45:33+00:00 | Vulnerability · Source |
| CVE-2017-5394 | suse_vex | SUSE CVE CVE-2017-5394 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T23:45:31+00:00 | Vulnerability · Source |
| CVE-2017-5401 | suse_vex | SUSE CVE CVE-2017-5401 | known affected: 1 recommended: 416 | 2026-07-26T23:45:29+00:00 | Vulnerability · Source |
| CVE-2017-5417 | suse_vex | SUSE CVE CVE-2017-5417 | known affected: 1 recommended: 249 | 2026-07-26T23:45:28+00:00 | Vulnerability · Source |
| CVE-2017-5430 | suse_vex | SUSE CVE CVE-2017-5430 | known affected: 2 known not affected: 42 recommended: 473 | 2026-07-26T23:45:26+00:00 | Vulnerability · Source |
| CVE-2017-5499 | suse_vex | SUSE CVE CVE-2017-5499 | known affected: 46 known not affected: 16 recommended: 154 | 2026-07-26T23:45:25+00:00 | Vulnerability · Source |
| CVE-2017-6350 | suse_vex | SUSE CVE CVE-2017-6350 | known affected: 320 known not affected: 10 recommended: 469 | 2026-07-26T23:45:22+00:00 | Vulnerability · Source |
| CVE-2017-6831 | suse_vex | SUSE CVE CVE-2017-6831 | known affected: 45 recommended: 196 | 2026-07-26T23:45:21+00:00 | Vulnerability · Source |
| CVE-2017-7495 | suse_vex | SUSE CVE CVE-2017-7495 | known not affected: 443 | 2026-07-26T23:45:18+00:00 | Vulnerability · Source |
| CVE-2017-7508 | suse_vex | SUSE CVE CVE-2017-7508 | known affected: 31 known not affected: 60 recommended: 51 | 2026-07-26T23:45:17+00:00 | Vulnerability · Source |
| CVE-2017-7599 | suse_vex | SUSE CVE CVE-2017-7599 | known affected: 439 known not affected: 80 recommended: 286 | 2026-07-26T23:45:15+00:00 | Vulnerability · Source |
| CVE-2017-7845 | suse_vex | SUSE CVE CVE-2017-7845 | known not affected: 198 recommended: 79 | 2026-07-26T23:45:13+00:00 | Vulnerability · Source |
| CVE-2017-7889 | suse_vex | SUSE CVE CVE-2017-7889 | known affected: 14 known not affected: 371 recommended: 92 | 2026-07-26T23:45:12+00:00 | Vulnerability · Source |
| CVE-2017-8067 | suse_vex | SUSE CVE CVE-2017-8067 | known not affected: 34 | 2026-07-26T23:45:10+00:00 | Vulnerability · Source |
| CVE-2017-9224 | suse_vex | SUSE CVE CVE-2017-9224 | known affected: 40 known not affected: 3 recommended: 1295 | 2026-07-26T23:45:08+00:00 | Vulnerability · Source |
| CVE-2017-9287 | suse_vex | SUSE CVE CVE-2017-9287 | known not affected: 16 recommended: 163 | 2026-07-26T23:45:06+00:00 | Vulnerability · Source |
| CVE-2017-9617 | suse_vex | SUSE CVE CVE-2017-9617 | known affected: 86 recommended: 162 | 2026-07-26T23:45:05+00:00 | Vulnerability · Source |
| CVE-2017-9750 | suse_vex | SUSE CVE CVE-2017-9750 | known affected: 394 known not affected: 364 recommended: 340 | 2026-07-26T23:45:03+00:00 | Vulnerability · Source |
| CVE-2017-9815 | suse_vex | SUSE CVE CVE-2017-9815 | known not affected: 144 | 2026-07-26T23:45:02+00:00 | Vulnerability · Source |
| CVE-2017-9831 | suse_vex | SUSE CVE CVE-2017-9831 | known affected: 19 known not affected: 165 | 2026-07-26T23:45:00+00:00 | Vulnerability · Source |
| CVE-2017-10089 | suse_vex | SUSE CVE CVE-2017-10089 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T23:44:59+00:00 | Vulnerability · Source |
| CVE-2017-10663 | suse_vex | SUSE CVE CVE-2017-10663 | known not affected: 28 | 2026-07-26T23:44:57+00:00 | Vulnerability · Source |
| CVE-2017-11473 | suse_vex | SUSE CVE CVE-2017-11473 | known affected: 26 known not affected: 404 recommended: 577 | 2026-07-26T23:44:55+00:00 | Vulnerability · Source |
| CVE-2017-11525 | suse_vex | SUSE CVE CVE-2017-11525 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T23:44:54+00:00 | Vulnerability · Source |
| CVE-2017-12654 | suse_vex | SUSE CVE CVE-2017-12654 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T23:44:52+00:00 | Vulnerability · Source |
| CVE-2017-13021 | suse_vex | SUSE CVE CVE-2017-13021 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T23:44:50+00:00 | Vulnerability · Source |
| CVE-2017-13087 | suse_vex | SUSE CVE CVE-2017-13087 | known affected: 6 known not affected: 354 recommended: 120 | 2026-07-26T23:44:48+00:00 | Vulnerability · Source |
| CVE-2017-13089 | suse_vex | SUSE CVE CVE-2017-13089 | known affected: 320 known not affected: 29 recommended: 164 | 2026-07-26T23:44:47+00:00 | Vulnerability · Source |
| CVE-2017-13726 | suse_vex | SUSE CVE CVE-2017-13726 | known not affected: 45 recommended: 18 | 2026-07-26T23:44:45+00:00 | Vulnerability · Source |
| CVE-2017-14132 | suse_vex | SUSE CVE CVE-2017-14132 | known affected: 46 recommended: 154 | 2026-07-26T23:44:43+00:00 | Vulnerability · Source |
| CVE-2017-14333 | suse_vex | SUSE CVE CVE-2017-14333 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-26T23:44:42+00:00 | Vulnerability · Source |
| CVE-2017-14633 | suse_vex | SUSE CVE CVE-2017-14633 | known affected: 509 known not affected: 120 recommended: 409 | 2026-07-26T23:44:40+00:00 | Vulnerability · Source |
| CVE-2017-15108 | suse_vex | SUSE CVE CVE-2017-15108 | known not affected: 15 recommended: 77 | 2026-07-26T23:44:38+00:00 | Vulnerability · Source |
| CVE-2017-15591 | suse_vex | SUSE CVE CVE-2017-15591 | known affected: 31 known not affected: 125 recommended: 86 | 2026-07-26T23:44:37+00:00 | Vulnerability · Source |
| CVE-2017-16353 | suse_vex | SUSE CVE CVE-2017-16353 | known affected: 94 recommended: 186 | 2026-07-26T23:44:35+00:00 | Vulnerability · Source |
| CVE-2017-17045 | suse_vex | SUSE CVE CVE-2017-17045 | known affected: 32 known not affected: 42 | 2026-07-26T23:44:33+00:00 | Vulnerability · Source |
| CVE-2017-18027 | suse_vex | SUSE CVE CVE-2017-18027 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T23:44:31+00:00 | Vulnerability · Source |
| CVE-2017-18219 | suse_vex | SUSE CVE CVE-2017-18219 | known not affected: 94 recommended: 50 | 2026-07-26T23:44:29+00:00 | Vulnerability · Source |
| CVE-2017-18235 | suse_vex | SUSE CVE CVE-2017-18235 | known not affected: 178 | 2026-07-26T23:44:28+00:00 | Vulnerability · Source |
| CVE-2017-1000121 | suse_vex | SUSE CVE CVE-2017-1000121 | known affected: 8 known not affected: 212 recommended: 830 | 2026-07-26T23:44:26+00:00 | Vulnerability · Source |
| CVE-2017-1000126 | suse_vex | SUSE CVE CVE-2017-1000126 | recommended: 149 | 2026-07-26T23:44:25+00:00 | Vulnerability · Source |