VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-15705 | suse_vex | SUSE CVE CVE-2017-15705 | known affected: 1 known not affected: 118 recommended: 193 | 2026-07-26T00:30:25+00:00 | Vulnerability · Source |
| CVE-2017-15874 | suse_vex | SUSE CVE CVE-2017-15874 | known affected: 1 known not affected: 16 recommended: 136 | 2026-07-26T00:30:23+00:00 | Vulnerability · Source |
| CVE-2017-16231 | suse_vex | SUSE CVE CVE-2017-16231 | known affected: 14 | 2026-07-26T00:30:17+00:00 | Vulnerability · Source |
| CVE-2017-16532 | suse_vex | SUSE CVE CVE-2017-16532 | known not affected: 368 | 2026-07-26T00:30:15+00:00 | Vulnerability · Source |
| CVE-2017-16537 | suse_vex | SUSE CVE CVE-2017-16537 | known affected: 323 known not affected: 255 recommended: 1354 | 2026-07-26T00:30:13+00:00 | Vulnerability · Source |
| CVE-2017-16643 | suse_vex | SUSE CVE CVE-2017-16643 | known not affected: 341 | 2026-07-26T00:30:07+00:00 | Vulnerability · Source |
| CVE-2017-16645 | suse_vex | SUSE CVE CVE-2017-16645 | known not affected: 291 recommended: 413 | 2026-07-26T00:30:05+00:00 | Vulnerability · Source |
| CVE-2017-16646 | suse_vex | SUSE CVE CVE-2017-16646 | known affected: 320 known not affected: 180 recommended: 1162 | 2026-07-26T00:30:03+00:00 | Vulnerability · Source |
| CVE-2017-16648 | suse_vex | SUSE CVE CVE-2017-16648 | known affected: 341 known not affected: 243 recommended: 787 | 2026-07-26T00:30:01+00:00 | Vulnerability · Source |
| CVE-2017-16828 | suse_vex | SUSE CVE CVE-2017-16828 | known affected: 452 known not affected: 76 recommended: 343 | 2026-07-26T00:29:57+00:00 | Vulnerability · Source |
| CVE-2017-16932 | suse_vex | SUSE CVE CVE-2017-16932 | known affected: 395 known not affected: 39 recommended: 129 | 2026-07-26T00:29:47+00:00 | Vulnerability · Source |
| CVE-2017-16942 | suse_vex | SUSE CVE CVE-2017-16942 | recommended: 58 | 2026-07-26T00:29:45+00:00 | Vulnerability · Source |
| CVE-2017-16994 | suse_vex | SUSE CVE CVE-2017-16994 | known not affected: 188 recommended: 407 | 2026-07-26T00:29:43+00:00 | Vulnerability · Source |
| CVE-2017-17046 | suse_vex | SUSE CVE CVE-2017-17046 | known not affected: 94 | 2026-07-26T00:29:41+00:00 | Vulnerability · Source |
| CVE-2017-17053 | suse_vex | SUSE CVE CVE-2017-17053 | known not affected: 283 recommended: 3 | 2026-07-26T00:29:40+00:00 | Vulnerability · Source |
| CVE-2017-17121 | suse_vex | SUSE CVE CVE-2017-17121 | known affected: 3 known not affected: 219 | 2026-07-26T00:29:37+00:00 | Vulnerability · Source |
| CVE-2017-17126 | suse_vex | SUSE CVE CVE-2017-17126 | known affected: 8 known not affected: 54 | 2026-07-26T00:29:36+00:00 | Vulnerability · Source |
| CVE-2017-17405 | suse_vex | SUSE CVE CVE-2017-17405 | known affected: 1 known not affected: 77 recommended: 98 | 2026-07-26T00:29:34+00:00 | Vulnerability · Source |
| CVE-2017-17426 | suse_vex | SUSE CVE CVE-2017-17426 | known affected: 320 known not affected: 464 recommended: 1007 | 2026-07-26T00:29:32+00:00 | Vulnerability · Source |
| CVE-2017-17448 | suse_vex | SUSE CVE CVE-2017-17448 | known not affected: 182 recommended: 503 | 2026-07-26T00:29:30+00:00 | Vulnerability · Source |
| CVE-2017-17449 | suse_vex | SUSE CVE CVE-2017-17449 | known affected: 36 known not affected: 108 recommended: 503 | 2026-07-26T00:29:28+00:00 | Vulnerability · Source |
| CVE-2017-17480 | suse_vex | SUSE CVE CVE-2017-17480 | recommended: 10 | 2026-07-26T00:29:24+00:00 | Vulnerability · Source |
| 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-17503 | suse_vex | SUSE CVE CVE-2017-17503 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:29:21+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-17712 | suse_vex | SUSE CVE CVE-2017-17712 | known not affected: 174 recommended: 438 | 2026-07-26T00:29:11+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-17790 | suse_vex | SUSE CVE CVE-2017-17790 | known affected: 1 known not affected: 107 recommended: 98 | 2026-07-26T00:29:01+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-17856 | suse_vex | SUSE CVE CVE-2017-17856 | known not affected: 182 recommended: 299 | 2026-07-26T00:28:57+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-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 |