VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293833 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5507 | suse_vex | SUSE CVE CVE-2017-5507 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-29T00:05:33+00:00 | Vulnerability · Source |
| CVE-2017-5650 | suse_vex | SUSE CVE CVE-2017-5650 | known not affected: 54 | 2026-07-29T00:05:32+00:00 | Vulnerability · Source |
| CVE-2017-5932 | suse_vex | SUSE CVE CVE-2017-5932 | known not affected: 461 | 2026-07-29T00:05:28+00:00 | Vulnerability · Source |
| CVE-2017-5967 | suse_vex | SUSE CVE CVE-2017-5967 | known not affected: 351 | 2026-07-29T00:05:27+00:00 | Vulnerability · Source |
| CVE-2017-6355 | suse_vex | SUSE CVE CVE-2017-6355 | recommended: 29 | 2026-07-29T00:05:22+00:00 | Vulnerability · Source |
| CVE-2017-6451 | suse_vex | SUSE CVE CVE-2017-6451 | known affected: 31 recommended: 98 | 2026-07-29T00:05:21+00:00 | Vulnerability · Source |
| CVE-2017-6460 | suse_vex | SUSE CVE CVE-2017-6460 | known affected: 31 recommended: 98 | 2026-07-29T00:05:19+00:00 | Vulnerability · Source |
| CVE-2017-6472 | suse_vex | SUSE CVE CVE-2017-6472 | known affected: 73 recommended: 444 | 2026-07-29T00:05:16+00:00 | Vulnerability · Source |
| CVE-2017-6499 | suse_vex | SUSE CVE CVE-2017-6499 | known affected: 10 known not affected: 113 | 2026-07-29T00:05:15+00:00 | Vulnerability · Source |
| CVE-2017-6836 | suse_vex | SUSE CVE CVE-2017-6836 | known affected: 45 recommended: 196 | 2026-07-29T00:05:12+00:00 | Vulnerability · Source |
| CVE-2017-6891 | suse_vex | SUSE CVE CVE-2017-6891 | known not affected: 321 recommended: 89 | 2026-07-29T00:05:10+00:00 | Vulnerability · Source |
| CVE-2017-7286 | suse_vex | SUSE CVE CVE-2017-7286 | known not affected: 64 | 2026-07-29T00:05:02+00:00 | Vulnerability · Source |
| CVE-2017-7794 | suse_vex | SUSE CVE CVE-2017-7794 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:55+00:00 | Vulnerability · Source |
| CVE-2017-7797 | suse_vex | SUSE CVE CVE-2017-7797 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:54+00:00 | Vulnerability · Source |
| CVE-2017-7837 | suse_vex | SUSE CVE CVE-2017-7837 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:53+00:00 | Vulnerability · Source |
| CVE-2017-7895 | suse_vex | SUSE CVE CVE-2017-7895 | known not affected: 36 recommended: 12 | 2026-07-29T00:04:51+00:00 | Vulnerability · Source |
| CVE-2017-7942 | suse_vex | SUSE CVE CVE-2017-7942 | known not affected: 25 recommended: 170 | 2026-07-29T00:04:50+00:00 | Vulnerability · Source |
| CVE-2017-8065 | suse_vex | SUSE CVE CVE-2017-8065 | known not affected: 34 | 2026-07-29T00:04:48+00:00 | Vulnerability · Source |
| CVE-2017-8106 | suse_vex | SUSE CVE CVE-2017-8106 | known not affected: 472 recommended: 98 | 2026-07-29T00:04:47+00:00 | Vulnerability · Source |
| CVE-2017-8284 | suse_vex | SUSE CVE CVE-2017-8284 | known not affected: 793 | 2026-07-29T00:04:46+00:00 | Vulnerability · Source |
| CVE-2017-8354 | suse_vex | SUSE CVE CVE-2017-8354 | known not affected: 14 recommended: 170 | 2026-07-29T00:04:44+00:00 | Vulnerability · Source |
| CVE-2017-8813 | suse_vex | SUSE CVE CVE-2017-8813 | known affected: 26 known not affected: 261 | 2026-07-29T00:04:41+00:00 | Vulnerability · Source |
| CVE-2017-9109 | suse_vex | SUSE CVE CVE-2017-9109 | known affected: 18 recommended: 44 | 2026-07-29T00:04:38+00:00 | Vulnerability · Source |
| CVE-2017-9117 | suse_vex | SUSE CVE CVE-2017-9117 | known not affected: 135 recommended: 22 | 2026-07-29T00:04:35+00:00 | Vulnerability · Source |
| CVE-2017-9141 | suse_vex | SUSE CVE CVE-2017-9141 | known not affected: 14 recommended: 170 | 2026-07-29T00:04:34+00:00 | Vulnerability · Source |
| CVE-2017-9263 | suse_vex | SUSE CVE CVE-2017-9263 | known affected: 4 known not affected: 27 recommended: 21 | 2026-07-29T00:04:32+00:00 | Vulnerability · Source |
| CVE-2017-9265 | suse_vex | SUSE CVE CVE-2017-9265 | known affected: 4 known not affected: 28 recommended: 21 | 2026-07-29T00:04:31+00:00 | Vulnerability · Source |
| CVE-2017-10105 | suse_vex | SUSE CVE CVE-2017-10105 | known affected: 15 known not affected: 109 recommended: 667 | 2026-07-29T00:04:24+00:00 | Vulnerability · Source |
| CVE-2017-10293 | suse_vex | SUSE CVE CVE-2017-10293 | known not affected: 169 recommended: 400 | 2026-07-29T00:04:21+00:00 | Vulnerability · Source |
| CVE-2017-10700 | suse_vex | SUSE CVE CVE-2017-10700 | known not affected: 106 | 2026-07-29T00:04:17+00:00 | Vulnerability · Source |
| CVE-2017-10912 | suse_vex | SUSE CVE CVE-2017-10912 | known not affected: 6 recommended: 43 | 2026-07-29T00:04:15+00:00 | Vulnerability · Source |
| CVE-2017-10986 | suse_vex | SUSE CVE CVE-2017-10986 | known affected: 24 known not affected: 111 recommended: 577 | 2026-07-29T00:04:14+00:00 | Vulnerability · Source |
| CVE-2017-11640 | suse_vex | SUSE CVE CVE-2017-11640 | known affected: 94 recommended: 186 | 2026-07-29T00:04:06+00:00 | Vulnerability · Source |
| CVE-2017-12181 | suse_vex | SUSE CVE CVE-2017-12181 | known affected: 2 known not affected: 38 recommended: 42 | 2026-07-29T00:03:59+00:00 | Vulnerability · Source |
| CVE-2017-12587 | suse_vex | SUSE CVE CVE-2017-12587 | known affected: 94 recommended: 186 | 2026-07-29T00:03:54+00:00 | Vulnerability · Source |
| CVE-2017-12668 | suse_vex | SUSE CVE CVE-2017-12668 | known affected: 95 known not affected: 21 recommended: 186 | 2026-07-29T00:03:53+00:00 | Vulnerability · Source |
| CVE-2017-12671 | suse_vex | SUSE CVE CVE-2017-12671 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-29T00:03:51+00:00 | Vulnerability · Source |
| CVE-2017-12836 | suse_vex | SUSE CVE CVE-2017-12836 | known affected: 31 known not affected: 24 recommended: 94 | 2026-07-29T00:03:48+00:00 | Vulnerability · Source |
| CVE-2017-12938 | suse_vex | SUSE CVE CVE-2017-12938 | known affected: 5 recommended: 28 | 2026-07-29T00:03:44+00:00 | Vulnerability · Source |
| CVE-2017-12983 | suse_vex | SUSE CVE CVE-2017-12983 | known affected: 94 recommended: 186 | 2026-07-29T00:03:42+00:00 | Vulnerability · Source |
| CVE-2017-13014 | suse_vex | SUSE CVE CVE-2017-13014 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-29T00:03:35+00:00 | Vulnerability · Source |
| CVE-2017-13168 | suse_vex | SUSE CVE CVE-2017-13168 | known not affected: 174 | 2026-07-29T00:03:26+00:00 | Vulnerability · Source |
| CVE-2017-13776 | suse_vex | SUSE CVE CVE-2017-13776 | known affected: 3 known not affected: 130 recommended: 14 | 2026-07-29T00:03:22+00:00 | Vulnerability · Source |
| CVE-2017-14060 | suse_vex | SUSE CVE CVE-2017-14060 | known affected: 94 known not affected: 50 recommended: 136 | 2026-07-29T00:03:16+00:00 | Vulnerability · Source |
| CVE-2017-14229 | suse_vex | SUSE CVE CVE-2017-14229 | known not affected: 60 | 2026-07-29T00:03:13+00:00 | Vulnerability · Source |
| CVE-2017-14230 | suse_vex | SUSE CVE CVE-2017-14230 | known affected: 12 recommended: 6 | 2026-07-29T00:03:12+00:00 | Vulnerability · Source |
| CVE-2017-14326 | suse_vex | SUSE CVE CVE-2017-14326 | recommended: 172 | 2026-07-29T00:03:10+00:00 | Vulnerability · Source |
| CVE-2017-14531 | suse_vex | SUSE CVE CVE-2017-14531 | known affected: 94 recommended: 172 | 2026-07-29T00:03:09+00:00 | Vulnerability · Source |
| CVE-2017-14649 | suse_vex | SUSE CVE CVE-2017-14649 | known affected: 94 recommended: 186 | 2026-07-29T00:03:07+00:00 | Vulnerability · Source |
| CVE-2017-14858 | suse_vex | SUSE CVE CVE-2017-14858 | known not affected: 158 | 2026-07-29T00:03:06+00:00 | Vulnerability · Source |