VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-17502 | suse_vex | SUSE CVE CVE-2017-17502 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:29:23+00:00 | Vulnerability · Source |
| CVE-2017-17504 | suse_vex | SUSE CVE CVE-2017-17504 | known affected: 94 known not affected: 20 recommended: 186 | 2026-07-26T00:29:19+00:00 | Vulnerability · Source |
| CVE-2017-17564 | suse_vex | SUSE CVE CVE-2017-17564 | known affected: 32 known not affected: 42 recommended: 166 | 2026-07-26T00:29:17+00:00 | Vulnerability · Source |
| CVE-2017-17566 | suse_vex | SUSE CVE CVE-2017-17566 | known affected: 32 known not affected: 42 recommended: 166 | 2026-07-26T00:29:16+00:00 | Vulnerability · Source |
| CVE-2017-17689 | suse_vex | SUSE CVE CVE-2017-17689 | known not affected: 247 recommended: 23 | 2026-07-26T00:29:14+00:00 | Vulnerability · Source |
| CVE-2017-17723 | suse_vex | SUSE CVE CVE-2017-17723 | known affected: 4 | 2026-07-26T00:29:10+00:00 | Vulnerability · Source |
| CVE-2017-17725 | suse_vex | SUSE CVE CVE-2017-17725 | known affected: 1 known not affected: 85 recommended: 10 | 2026-07-26T00:29:08+00:00 | Vulnerability · Source |
| CVE-2017-17740 | suse_vex | SUSE CVE CVE-2017-17740 | known affected: 373 known not affected: 23 recommended: 756 | 2026-07-26T00:29:06+00:00 | Vulnerability · Source |
| CVE-2017-17852 | suse_vex | SUSE CVE CVE-2017-17852 | known not affected: 182 recommended: 299 | 2026-07-26T00:28:59+00:00 | Vulnerability · Source |
| CVE-2017-17863 | suse_vex | SUSE CVE CVE-2017-17863 | known not affected: 182 | 2026-07-26T00:28:54+00:00 | Vulnerability · Source |
| 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-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-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-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-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-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-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-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-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-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-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-1000376 | suse_vex | SUSE CVE CVE-2017-1000376 | known not affected: 65 recommended: 89 | 2026-07-26T00:26:48+00:00 | Vulnerability · Source |
| CVE-2017-1000422 | suse_vex | SUSE CVE CVE-2017-1000422 | recommended: 75 | 2026-07-26T00:26:37+00:00 | Vulnerability · Source |
| CVE-2017-1000445 | suse_vex | SUSE CVE CVE-2017-1000445 | known affected: 94 known not affected: 1 recommended: 172 | 2026-07-26T00:26:35+00:00 | Vulnerability · Source |
| CVE-2017-1000476 | suse_vex | SUSE CVE CVE-2017-1000476 | known affected: 94 recommended: 206 | 2026-07-26T00:26:33+00:00 | Vulnerability · Source |
| CVE-2018-0494 | suse_vex | SUSE CVE CVE-2018-0494 | known affected: 336 known not affected: 24 recommended: 162 | 2026-07-26T00:26:28+00:00 | Vulnerability · Source |
| CVE-2018-0733 | suse_vex | SUSE CVE CVE-2018-0733 | known not affected: 68 | 2026-07-26T00:26:21+00:00 | Vulnerability · Source |
| CVE-2018-1058 | suse_vex | SUSE CVE CVE-2018-1058 | known affected: 56 known not affected: 185 recommended: 437 | 2026-07-26T00:26:13+00:00 | Vulnerability · Source |
| CVE-2018-1083 | suse_vex | SUSE CVE CVE-2018-1083 | known affected: 412 known not affected: 45 recommended: 81 | 2026-07-26T00:26:05+00:00 | Vulnerability · Source |
| CVE-2018-1094 | suse_vex | SUSE CVE CVE-2018-1094 | known affected: 7 known not affected: 232 recommended: 493 | 2026-07-26T00:26:01+00:00 | Vulnerability · Source |
| CVE-2018-1095 | suse_vex | SUSE CVE CVE-2018-1095 | known not affected: 393 | 2026-07-26T00:25:59+00:00 | Vulnerability · Source |
| CVE-2018-1106 | suse_vex | SUSE CVE CVE-2018-1106 | known affected: 10 known not affected: 57 recommended: 554 | 2026-07-26T00:25:57+00:00 | Vulnerability · Source |
| CVE-2018-1115 | suse_vex | SUSE CVE CVE-2018-1115 | known affected: 54 known not affected: 255 recommended: 395 | 2026-07-26T00:25:55+00:00 | Vulnerability · Source |