VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-17880 | suse_vex | SUSE CVE CVE-2017-17880 | known affected: 10 known not affected: 130 | 2026-07-26T00:28:52+00:00 | Vulnerability · Source |
| CVE-2017-17881 | suse_vex | SUSE CVE CVE-2017-17881 | recommended: 172 | 2026-07-26T00:28:50+00:00 | Vulnerability · Source |
| CVE-2017-17882 | suse_vex | SUSE CVE CVE-2017-17882 | known affected: 94 recommended: 172 | 2026-07-26T00:28:48+00:00 | Vulnerability · Source |
| CVE-2017-17883 | suse_vex | SUSE CVE CVE-2017-17883 | known affected: 1060 known not affected: 1243 | 2026-07-26T00:28:45+00:00 | Vulnerability · Source |
| CVE-2017-17885 | suse_vex | SUSE CVE CVE-2017-17885 | known affected: 95 recommended: 172 | 2026-07-26T00:28:43+00:00 | Vulnerability · Source |
| CVE-2017-17886 | suse_vex | SUSE CVE CVE-2017-17886 | known not affected: 94 | 2026-07-26T00:28:40+00:00 | Vulnerability · Source |
| CVE-2017-17914 | suse_vex | SUSE CVE CVE-2017-17914 | known affected: 94 recommended: 172 | 2026-07-26T00:28:38+00:00 | Vulnerability · Source |
| CVE-2017-17934 | suse_vex | SUSE CVE CVE-2017-17934 | known affected: 95 recommended: 172 | 2026-07-26T00:28:35+00:00 | Vulnerability · Source |
| CVE-2017-17973 | suse_vex | SUSE CVE CVE-2017-17973 | known affected: 47 known not affected: 1 recommended: 61 | 2026-07-26T00:28:33+00:00 | Vulnerability · Source |
| CVE-2017-17975 | suse_vex | SUSE CVE CVE-2017-17975 | known not affected: 387 recommended: 406 | 2026-07-26T00:28:30+00:00 | Vulnerability · Source |
| CVE-2017-18005 | suse_vex | SUSE CVE CVE-2017-18005 | recommended: 8 | 2026-07-26T00:28:28+00:00 | Vulnerability · Source |
| CVE-2017-18008 | suse_vex | SUSE CVE CVE-2017-18008 | known affected: 94 recommended: 136 | 2026-07-26T00:28:26+00:00 | Vulnerability · Source |
| CVE-2017-18028 | suse_vex | SUSE CVE CVE-2017-18028 | known affected: 95 known not affected: 21 recommended: 186 | 2026-07-26T00:28:24+00:00 | Vulnerability · Source |
| CVE-2017-18075 | suse_vex | SUSE CVE CVE-2017-18075 | known affected: 97 known not affected: 342 recommended: 313 | 2026-07-26T00:28:22+00:00 | Vulnerability · Source |
| CVE-2017-18078 | suse_vex | SUSE CVE CVE-2017-18078 | known affected: 451 known not affected: 240 recommended: 1131 | 2026-07-26T00:28:19+00:00 | Vulnerability · Source |
| CVE-2017-18079 | suse_vex | SUSE CVE CVE-2017-18079 | known not affected: 147 recommended: 242 | 2026-07-26T00:28:17+00:00 | Vulnerability · Source |
| CVE-2017-18183 | suse_vex | SUSE CVE CVE-2017-18183 | known not affected: 157 | 2026-07-26T00:28:15+00:00 | Vulnerability · Source |
| CVE-2017-18190 | suse_vex | SUSE CVE CVE-2017-18190 | known not affected: 18 recommended: 112 | 2026-07-26T00:28:12+00:00 | Vulnerability · Source |
| CVE-2017-18199 | suse_vex | SUSE CVE CVE-2017-18199 | known affected: 51 recommended: 421 | 2026-07-26T00:28:08+00:00 | Vulnerability · Source |
| CVE-2017-18200 | suse_vex | SUSE CVE CVE-2017-18200 | known not affected: 14 | 2026-07-26T00:28:06+00:00 | Vulnerability · Source |
| CVE-2017-18201 | suse_vex | SUSE CVE CVE-2017-18201 | known affected: 48 known not affected: 108 recommended: 480 | 2026-07-26T00:28:05+00:00 | Vulnerability · Source |
| CVE-2017-18205 | suse_vex | SUSE CVE CVE-2017-18205 | known affected: 17 known not affected: 50 recommended: 16 | 2026-07-26T00:28:03+00:00 | Vulnerability · Source |
| CVE-2017-18207 | suse_vex | SUSE CVE CVE-2017-18207 | known affected: 456 known not affected: 4 recommended: 1540 | 2026-07-26T00:28:01+00:00 | Vulnerability · Source |
| CVE-2017-18209 | suse_vex | SUSE CVE CVE-2017-18209 | known affected: 94 known not affected: 50 recommended: 136 | 2026-07-26T00:28:00+00:00 | Vulnerability · Source |
| CVE-2017-18211 | suse_vex | SUSE CVE CVE-2017-18211 | known affected: 94 known not affected: 50 recommended: 136 | 2026-07-26T00:27:58+00:00 | Vulnerability · Source |
| CVE-2017-18218 | suse_vex | SUSE CVE CVE-2017-18218 | known not affected: 212 | 2026-07-26T00:27:57+00:00 | Vulnerability · Source |
| CVE-2017-18221 | suse_vex | SUSE CVE CVE-2017-18221 | known not affected: 135 recommended: 80 | 2026-07-26T00:27:55+00:00 | Vulnerability · Source |
| CVE-2017-18224 | suse_vex | SUSE CVE CVE-2017-18224 | known affected: 57 known not affected: 334 recommended: 412 | 2026-07-26T00:27:53+00:00 | Vulnerability · Source |
| CVE-2017-18229 | suse_vex | SUSE CVE CVE-2017-18229 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:27:52+00:00 | Vulnerability · Source |
| CVE-2017-18232 | suse_vex | SUSE CVE CVE-2017-18232 | known not affected: 55 recommended: 13 | 2026-07-26T00:27:50+00:00 | Vulnerability · Source |
| CVE-2017-18234 | suse_vex | SUSE CVE CVE-2017-18234 | known affected: 5 recommended: 34 | 2026-07-26T00:27:49+00:00 | Vulnerability · Source |
| CVE-2017-18236 | suse_vex | SUSE CVE CVE-2017-18236 | known affected: 4 known not affected: 14 recommended: 26 | 2026-07-26T00:27:47+00:00 | Vulnerability · Source |
| CVE-2017-18241 | suse_vex | SUSE CVE CVE-2017-18241 | known affected: 40 known not affected: 220 recommended: 124 | 2026-07-26T00:27:46+00:00 | Vulnerability · Source |
| CVE-2017-18248 | suse_vex | SUSE CVE CVE-2017-18248 | known affected: 368 known not affected: 259 recommended: 820 | 2026-07-26T00:27:44+00:00 | Vulnerability · Source |
| CVE-2017-18249 | suse_vex | SUSE CVE CVE-2017-18249 | known not affected: 299 recommended: 142 | 2026-07-26T00:27:42+00:00 | Vulnerability · Source |
| CVE-2017-18250 | suse_vex | SUSE CVE CVE-2017-18250 | known affected: 97 known not affected: 50 recommended: 100 | 2026-07-26T00:27:40+00:00 | Vulnerability · Source |
| CVE-2017-18253 | suse_vex | SUSE CVE CVE-2017-18253 | known affected: 10 known not affected: 190 | 2026-07-26T00:27:38+00:00 | Vulnerability · Source |
| CVE-2017-18255 | suse_vex | SUSE CVE CVE-2017-18255 | known affected: 38 known not affected: 302 recommended: 160 | 2026-07-26T00:27:36+00:00 | Vulnerability · Source |
| CVE-2017-18257 | suse_vex | SUSE CVE CVE-2017-18257 | known not affected: 297 recommended: 124 | 2026-07-26T00:27:34+00:00 | Vulnerability · Source |
| CVE-2017-18261 | suse_vex | SUSE CVE CVE-2017-18261 | known not affected: 291 | 2026-07-26T00:27:32+00:00 | Vulnerability · Source |
| CVE-2017-18360 | suse_vex | SUSE CVE CVE-2017-18360 | known not affected: 355 recommended: 74 | 2026-07-26T00:27:22+00:00 | Vulnerability · Source |
| CVE-2017-18550 | suse_vex | SUSE CVE CVE-2017-18550 | known not affected: 210 | 2026-07-26T00:27:20+00:00 | Vulnerability · Source |
| CVE-2017-18595 | suse_vex | SUSE CVE CVE-2017-18595 | known affected: 132 known not affected: 61 recommended: 885 | 2026-07-26T00:27:18+00:00 | Vulnerability · Source |
| CVE-2017-1000101 | suse_vex | SUSE CVE CVE-2017-1000101 | known affected: 338 known not affected: 80 recommended: 429 | 2026-07-26T00:27:13+00:00 | Vulnerability · Source |
| CVE-2017-1000199 | suse_vex | SUSE CVE CVE-2017-1000199 | known affected: 2 recommended: 8 | 2026-07-26T00:27:06+00:00 | Vulnerability · Source |
| CVE-2017-1000201 | suse_vex | SUSE CVE CVE-2017-1000201 | known not affected: 9 | 2026-07-26T00:27:04+00:00 | Vulnerability · Source |
| CVE-2017-1000232 | suse_vex | SUSE CVE CVE-2017-1000232 | recommended: 176 | 2026-07-26T00:27:02+00:00 | Vulnerability · Source |
| CVE-2017-1000252 | suse_vex | SUSE CVE CVE-2017-1000252 | known affected: 3 known not affected: 149 recommended: 419 | 2026-07-26T00:27:00+00:00 | Vulnerability · Source |
| CVE-2017-1000254 | suse_vex | SUSE CVE CVE-2017-1000254 | known affected: 337 known not affected: 64 recommended: 428 | 2026-07-26T00:26:57+00:00 | Vulnerability · Source |
| CVE-2017-1000257 | suse_vex | SUSE CVE CVE-2017-1000257 | known affected: 338 known not affected: 80 recommended: 402 | 2026-07-26T00:26:55+00:00 | Vulnerability · Source |