VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286864 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9782 | suse_vex | SUSE CVE CVE-2017-9782 | known affected: 46 known not affected: 16 recommended: 150 | 2026-08-01T23:36:37+00:00 | Vulnerability · Source |
| CVE-2017-9832 | suse_vex | SUSE CVE CVE-2017-9832 | known affected: 14 known not affected: 129 | 2026-08-01T23:36:36+00:00 | Vulnerability · Source |
| CVE-2017-10309 | suse_vex | SUSE CVE CVE-2017-10309 | known affected: 20 known not affected: 93 recommended: 232 | 2026-08-01T23:36:34+00:00 | Vulnerability · Source |
| CVE-2017-10384 | suse_vex | SUSE CVE CVE-2017-10384 | known affected: 1 known not affected: 223 recommended: 439 | 2026-08-01T23:36:33+00:00 | Vulnerability · Source |
| CVE-2017-10981 | suse_vex | SUSE CVE CVE-2017-10981 | known affected: 24 known not affected: 111 recommended: 26 | 2026-08-01T23:36:31+00:00 | Vulnerability · Source |
| CVE-2017-10988 | suse_vex | SUSE CVE CVE-2017-10988 | known affected: 24 known not affected: 111 recommended: 613 | 2026-08-01T23:36:30+00:00 | Vulnerability · Source |
| CVE-2017-11089 | suse_vex | SUSE CVE CVE-2017-11089 | known not affected: 55 recommended: 80 | 2026-08-01T23:36:28+00:00 | Vulnerability · Source |
| CVE-2017-11337 | suse_vex | SUSE CVE CVE-2017-11337 | known affected: 96 known not affected: 41 recommended: 157 | 2026-08-01T23:36:27+00:00 | Vulnerability · Source |
| CVE-2017-11409 | suse_vex | SUSE CVE CVE-2017-11409 | known affected: 86 known not affected: 115 | 2026-08-01T23:36:26+00:00 | Vulnerability · Source |
| CVE-2017-11472 | suse_vex | SUSE CVE CVE-2017-11472 | known not affected: 326 recommended: 114 | 2026-08-01T23:36:24+00:00 | Vulnerability · Source |
| CVE-2017-11473 | suse_vex | SUSE CVE CVE-2017-11473 | known affected: 26 known not affected: 404 recommended: 577 | 2026-08-01T23:36:23+00:00 | Vulnerability · Source |
| CVE-2017-11624 | suse_vex | SUSE CVE CVE-2017-11624 | known affected: 4 known not affected: 33 recommended: 326 | 2026-08-01T23:36:21+00:00 | Vulnerability · Source |
| CVE-2017-12459 | suse_vex | SUSE CVE CVE-2017-12459 | known not affected: 137 | 2026-08-01T23:36:19+00:00 | Vulnerability · Source |
| CVE-2017-12642 | suse_vex | SUSE CVE CVE-2017-12642 | known affected: 94 recommended: 186 | 2026-08-01T23:36:17+00:00 | Vulnerability · Source |
| CVE-2017-12762 | suse_vex | SUSE CVE CVE-2017-12762 | known affected: 84 recommended: 217 | 2026-08-01T23:36:16+00:00 | Vulnerability · Source |
| CVE-2017-13027 | suse_vex | SUSE CVE CVE-2017-13027 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:15+00:00 | Vulnerability · Source |
| CVE-2017-13035 | suse_vex | SUSE CVE CVE-2017-13035 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:13+00:00 | Vulnerability · Source |
| CVE-2017-13052 | suse_vex | SUSE CVE CVE-2017-13052 | known affected: 336 known not affected: 24 recommended: 147 | 2026-08-01T23:36:12+00:00 | Vulnerability · Source |
| CVE-2017-13140 | suse_vex | SUSE CVE CVE-2017-13140 | known affected: 10 known not affected: 77 | 2026-08-01T23:36:11+00:00 | Vulnerability · Source |
| CVE-2017-13221 | suse_vex | SUSE CVE CVE-2017-13221 | known not affected: 48 | 2026-08-01T23:36:10+00:00 | Vulnerability · Source |
| CVE-2017-13689 | suse_vex | SUSE CVE CVE-2017-13689 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T23:36:09+00:00 | Vulnerability · Source |
| CVE-2017-13798 | suse_vex | SUSE CVE CVE-2017-13798 | known not affected: 87 recommended: 939 | 2026-08-01T23:36:07+00:00 | Vulnerability · Source |
| CVE-2017-14160 | suse_vex | SUSE CVE CVE-2017-14160 | known affected: 516 known not affected: 120 recommended: 367 | 2026-08-01T23:36:06+00:00 | Vulnerability · Source |
| CVE-2017-14341 | suse_vex | SUSE CVE CVE-2017-14341 | known affected: 94 recommended: 186 | 2026-08-01T23:36:04+00:00 | Vulnerability · Source |
| CVE-2017-14342 | suse_vex | SUSE CVE CVE-2017-14342 | known affected: 94 recommended: 186 | 2026-08-01T23:36:03+00:00 | Vulnerability · Source |
| CVE-2017-14859 | suse_vex | SUSE CVE CVE-2017-14859 | known affected: 13 known not affected: 149 recommended: 186 | 2026-08-01T23:36:02+00:00 | Vulnerability · Source |
| CVE-2017-14861 | suse_vex | SUSE CVE CVE-2017-14861 | known affected: 4 known not affected: 53 | 2026-08-01T23:36:01+00:00 | Vulnerability · Source |
| CVE-2017-14954 | suse_vex | SUSE CVE CVE-2017-14954 | known not affected: 28 | 2026-08-01T23:36:00+00:00 | Vulnerability · Source |
| CVE-2017-15085 | suse_vex | SUSE CVE CVE-2017-15085 | known affected: 534 known not affected: 263 | 2026-08-01T23:35:59+00:00 | Vulnerability · Source |
| CVE-2017-15086 | suse_vex | SUSE CVE CVE-2017-15086 | known affected: 533 known not affected: 355 | 2026-08-01T23:35:57+00:00 | Vulnerability · Source |
| CVE-2017-15130 | suse_vex | SUSE CVE CVE-2017-15130 | known affected: 62 known not affected: 37 recommended: 473 | 2026-08-01T23:35:56+00:00 | Vulnerability · Source |
| CVE-2017-15306 | suse_vex | SUSE CVE CVE-2017-15306 | known not affected: 14 | 2026-08-01T23:35:55+00:00 | Vulnerability · Source |
| CVE-2017-15631 | suse_vex | SUSE CVE CVE-2017-15631 | known not affected: 15 recommended: 62 | 2026-08-01T23:35:54+00:00 | Vulnerability · Source |
| CVE-2017-15868 | suse_vex | SUSE CVE CVE-2017-15868 | known affected: 16 known not affected: 374 recommended: 260 | 2026-08-01T23:35:52+00:00 | Vulnerability · Source |
| CVE-2017-15930 | suse_vex | SUSE CVE CVE-2017-15930 | known affected: 94 recommended: 186 | 2026-08-01T23:35:51+00:00 | Vulnerability · Source |
| CVE-2017-16528 | suse_vex | SUSE CVE CVE-2017-16528 | known affected: 36 known not affected: 559 recommended: 407 | 2026-08-01T23:35:50+00:00 | Vulnerability · Source |
| CVE-2017-16644 | suse_vex | SUSE CVE CVE-2017-16644 | known affected: 36 known not affected: 358 recommended: 609 | 2026-08-01T23:35:48+00:00 | Vulnerability · Source |
| CVE-2017-16650 | suse_vex | SUSE CVE CVE-2017-16650 | known affected: 21 known not affected: 304 recommended: 373 | 2026-08-01T23:35:47+00:00 | Vulnerability · Source |
| CVE-2017-17083 | suse_vex | SUSE CVE CVE-2017-17083 | known not affected: 115 recommended: 606 | 2026-08-01T23:35:45+00:00 | Vulnerability · Source |
| CVE-2017-17558 | suse_vex | SUSE CVE CVE-2017-17558 | known affected: 23 known not affected: 569 recommended: 514 | 2026-08-01T23:35:44+00:00 | Vulnerability · Source |
| CVE-2017-17669 | suse_vex | SUSE CVE CVE-2017-17669 | known not affected: 22 recommended: 23 | 2026-08-01T23:35:43+00:00 | Vulnerability · Source |
| CVE-2017-18184 | suse_vex | SUSE CVE CVE-2017-18184 | known not affected: 157 | 2026-08-01T23:35:42+00:00 | Vulnerability · Source |
| CVE-2017-18233 | suse_vex | SUSE CVE CVE-2017-18233 | known affected: 4 known not affected: 17 recommended: 26 | 2026-08-01T23:35:40+00:00 | Vulnerability · Source |
| CVE-2017-18870 | suse_vex | SUSE CVE CVE-2017-18870 | No product status | 2026-08-01T23:35:39+00:00 | Vulnerability · Source |
| CVE-2017-18871 | suse_vex | SUSE CVE CVE-2017-18871 | No product status | 2026-08-01T23:35:38+00:00 | Vulnerability · Source |
| CVE-2017-18872 | suse_vex | SUSE CVE CVE-2017-18872 | recommended: 1 | 2026-08-01T23:35:37+00:00 | Vulnerability · Source |
| CVE-2017-18883 | suse_vex | SUSE CVE CVE-2017-18883 | No product status | 2026-08-01T23:35:35+00:00 | Vulnerability · Source |
| CVE-2017-18884 | suse_vex | SUSE CVE CVE-2017-18884 | No product status | 2026-08-01T23:35:34+00:00 | Vulnerability · Source |
| CVE-2017-18885 | suse_vex | SUSE CVE CVE-2017-18885 | No product status | 2026-08-01T23:35:33+00:00 | Vulnerability · Source |
| CVE-2017-18886 | suse_vex | SUSE CVE CVE-2017-18886 | No product status | 2026-08-01T23:35:32+00:00 | Vulnerability · Source |