VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283003 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5389 | suse_vex | SUSE CVE CVE-2017-5389 | known affected: 1 known not affected: 34 recommended: 249 | 2026-07-19T18:34:59+00:00 | Vulnerability · Source |
| CVE-2017-5400 | suse_vex | SUSE CVE CVE-2017-5400 | known affected: 1 recommended: 408 | 2026-07-19T18:34:58+00:00 | Vulnerability · Source |
| CVE-2017-5401 | suse_vex | SUSE CVE CVE-2017-5401 | known affected: 1 recommended: 408 | 2026-07-19T18:34:57+00:00 | Vulnerability · Source |
| CVE-2017-5403 | suse_vex | SUSE CVE CVE-2017-5403 | known affected: 1 recommended: 333 | 2026-07-19T18:34:56+00:00 | Vulnerability · Source |
| CVE-2017-5406 | suse_vex | SUSE CVE CVE-2017-5406 | known affected: 1 recommended: 333 | 2026-07-19T18:34:55+00:00 | Vulnerability · Source |
| CVE-2017-5415 | suse_vex | SUSE CVE CVE-2017-5415 | known affected: 1 recommended: 249 | 2026-07-19T18:34:53+00:00 | Vulnerability · Source |
| CVE-2017-5420 | suse_vex | SUSE CVE CVE-2017-5420 | known affected: 1 recommended: 249 | 2026-07-19T18:34:52+00:00 | Vulnerability · Source |
| CVE-2017-5427 | suse_vex | SUSE CVE CVE-2017-5427 | known affected: 1 recommended: 249 | 2026-07-19T18:34:51+00:00 | Vulnerability · Source |
| CVE-2017-5434 | suse_vex | SUSE CVE CVE-2017-5434 | known not affected: 42 recommended: 719 | 2026-07-19T18:34:50+00:00 | Vulnerability · Source |
| CVE-2017-5437 | suse_vex | SUSE CVE CVE-2017-5437 | known not affected: 42 recommended: 687 | 2026-07-19T18:34:48+00:00 | Vulnerability · Source |
| CVE-2017-5448 | suse_vex | SUSE CVE CVE-2017-5448 | known not affected: 42 recommended: 634 | 2026-07-19T18:34:47+00:00 | Vulnerability · Source |
| CVE-2017-5458 | suse_vex | SUSE CVE CVE-2017-5458 | known not affected: 42 recommended: 12 | 2026-07-19T18:34:46+00:00 | Vulnerability · Source |
| CVE-2017-5460 | suse_vex | SUSE CVE CVE-2017-5460 | known not affected: 42 recommended: 719 | 2026-07-19T18:34:45+00:00 | Vulnerability · Source |
| CVE-2017-5465 | suse_vex | SUSE CVE CVE-2017-5465 | known not affected: 42 recommended: 719 | 2026-07-19T18:34:43+00:00 | Vulnerability · Source |
| CVE-2017-5504 | suse_vex | SUSE CVE CVE-2017-5504 | known affected: 41 recommended: 146 | 2026-07-19T18:34:42+00:00 | Vulnerability · Source |
| CVE-2017-5526 | suse_vex | SUSE CVE CVE-2017-5526 | known affected: 407 known not affected: 204 recommended: 1888 | 2026-07-19T18:34:40+00:00 | Vulnerability · Source |
| CVE-2017-5552 | suse_vex | SUSE CVE CVE-2017-5552 | known affected: 407 known not affected: 154 recommended: 1703 | 2026-07-19T18:34:39+00:00 | Vulnerability · Source |
| CVE-2017-5735 | suse_vex | SUSE CVE CVE-2017-5735 | known affected: 29 recommended: 226 | 2026-07-19T18:34:37+00:00 | Vulnerability · Source |
| CVE-2017-5836 | suse_vex | SUSE CVE CVE-2017-5836 | known affected: 29 recommended: 353 | 2026-07-19T18:34:36+00:00 | Vulnerability · Source |
| CVE-2017-5838 | suse_vex | SUSE CVE CVE-2017-5838 | known affected: 69 recommended: 2392 | 2026-07-19T18:34:34+00:00 | Vulnerability · Source |
| CVE-2017-5839 | suse_vex | SUSE CVE CVE-2017-5839 | known affected: 217 recommended: 923 | 2026-07-19T18:34:33+00:00 | Vulnerability · Source |
| CVE-2017-5842 | suse_vex | SUSE CVE CVE-2017-5842 | known affected: 217 recommended: 933 | 2026-07-19T18:34:32+00:00 | Vulnerability · Source |
| CVE-2017-5843 | suse_vex | SUSE CVE CVE-2017-5843 | known affected: 13 known not affected: 41 recommended: 588 | 2026-07-19T18:34:30+00:00 | Vulnerability · Source |
| CVE-2017-5856 | suse_vex | SUSE CVE CVE-2017-5856 | known affected: 409 known not affected: 130 recommended: 1827 | 2026-07-19T18:34:29+00:00 | Vulnerability · Source |
| CVE-2017-5884 | suse_vex | SUSE CVE CVE-2017-5884 | known not affected: 408 recommended: 506 | 2026-07-19T18:34:27+00:00 | Vulnerability · Source |
| CVE-2017-5931 | suse_vex | SUSE CVE CVE-2017-5931 | known not affected: 225 recommended: 1606 | 2026-07-19T18:34:26+00:00 | Vulnerability · Source |
| CVE-2017-5950 | suse_vex | SUSE CVE CVE-2017-5950 | known affected: 320 known not affected: 63 recommended: 215 | 2026-07-19T18:34:25+00:00 | Vulnerability · Source |
| CVE-2017-5953 | suse_vex | SUSE CVE CVE-2017-5953 | known affected: 320 recommended: 460 | 2026-07-19T18:34:23+00:00 | Vulnerability · Source |
| CVE-2017-5993 | suse_vex | SUSE CVE CVE-2017-5993 | recommended: 131 | 2026-07-19T18:34:22+00:00 | Vulnerability · Source |
| CVE-2017-6004 | suse_vex | SUSE CVE CVE-2017-6004 | known affected: 346 known not affected: 521 recommended: 698 | 2026-07-19T18:34:21+00:00 | Vulnerability · Source |
| CVE-2017-6313 | suse_vex | SUSE CVE CVE-2017-6313 | known affected: 394 known not affected: 136 recommended: 654 | 2026-07-19T18:34:19+00:00 | Vulnerability · Source |
| CVE-2017-6349 | suse_vex | SUSE CVE CVE-2017-6349 | known affected: 320 known not affected: 10 recommended: 444 | 2026-07-19T18:34:18+00:00 | Vulnerability · Source |
| CVE-2017-6362 | suse_vex | SUSE CVE CVE-2017-6362 | known affected: 394 known not affected: 1257 recommended: 222 | 2026-07-19T18:34:16+00:00 | Vulnerability · Source |
| CVE-2017-6420 | suse_vex | SUSE CVE CVE-2017-6420 | known affected: 1 known not affected: 78 recommended: 277 | 2026-07-19T18:34:15+00:00 | Vulnerability · Source |
| CVE-2017-6435 | suse_vex | SUSE CVE CVE-2017-6435 | recommended: 335 | 2026-07-19T18:34:14+00:00 | Vulnerability · Source |
| CVE-2017-6437 | suse_vex | SUSE CVE CVE-2017-6437 | recommended: 335 | 2026-07-19T18:34:13+00:00 | Vulnerability · Source |
| CVE-2017-6440 | suse_vex | SUSE CVE CVE-2017-6440 | known affected: 29 recommended: 361 | 2026-07-19T18:34:12+00:00 | Vulnerability · Source |
| CVE-2017-6467 | suse_vex | SUSE CVE CVE-2017-6467 | known affected: 72 recommended: 444 | 2026-07-19T18:34:10+00:00 | Vulnerability · Source |
| CVE-2017-6471 | suse_vex | SUSE CVE CVE-2017-6471 | known affected: 61 recommended: 444 | 2026-07-19T18:34:09+00:00 | Vulnerability · Source |
| CVE-2017-6473 | suse_vex | SUSE CVE CVE-2017-6473 | known affected: 61 recommended: 444 | 2026-07-19T18:34:08+00:00 | Vulnerability · Source |
| CVE-2017-6508 | suse_vex | SUSE CVE CVE-2017-6508 | known affected: 335 known not affected: 24 recommended: 165 | 2026-07-19T18:34:07+00:00 | Vulnerability · Source |
| CVE-2017-6519 | suse_vex | SUSE CVE CVE-2017-6519 | known not affected: 300 recommended: 582 | 2026-07-19T18:34:06+00:00 | Vulnerability · Source |
| CVE-2017-6965 | suse_vex | SUSE CVE CVE-2017-6965 | known affected: 394 known not affected: 158 recommended: 336 | 2026-07-19T18:34:04+00:00 | Vulnerability · Source |
| CVE-2017-6966 | suse_vex | SUSE CVE CVE-2017-6966 | known affected: 394 known not affected: 21 recommended: 336 | 2026-07-19T18:34:03+00:00 | Vulnerability · Source |
| CVE-2017-7012 | suse_vex | SUSE CVE CVE-2017-7012 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-19T18:34:01+00:00 | Vulnerability · Source |
| CVE-2017-7034 | suse_vex | SUSE CVE CVE-2017-7034 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-19T18:34:00+00:00 | Vulnerability · Source |
| CVE-2017-7038 | suse_vex | SUSE CVE CVE-2017-7038 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-19T18:33:59+00:00 | Vulnerability · Source |
| CVE-2017-7052 | suse_vex | SUSE CVE CVE-2017-7052 | known affected: 6 known not affected: 321 recommended: 924 | 2026-07-19T18:33:57+00:00 | Vulnerability · Source |
| CVE-2017-7056 | suse_vex | SUSE CVE CVE-2017-7056 | known affected: 6 known not affected: 321 recommended: 924 | 2026-07-19T18:33:56+00:00 | Vulnerability · Source |
| CVE-2017-7059 | suse_vex | SUSE CVE CVE-2017-7059 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-19T18:33:55+00:00 | Vulnerability · Source |