VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286518 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5987 | suse_vex | SUSE CVE CVE-2017-5987 | known affected: 26 known not affected: 146 recommended: 1760 | 2026-07-29T00:05:25+00:00 | Vulnerability · Source |
| CVE-2017-6349 | suse_vex | SUSE CVE CVE-2017-6349 | known affected: 320 known not affected: 10 recommended: 469 | 2026-07-29T00:05:23+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-6470 | suse_vex | SUSE CVE CVE-2017-6470 | known affected: 73 recommended: 444 | 2026-07-29T00:05:18+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-6832 | suse_vex | SUSE CVE CVE-2017-6832 | known affected: 45 recommended: 202 | 2026-07-29T00:05:13+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-7048 | suse_vex | SUSE CVE CVE-2017-7048 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-29T00:05:09+00:00 | Vulnerability · Source |
| CVE-2017-7081 | suse_vex | SUSE CVE CVE-2017-7081 | known not affected: 87 recommended: 939 | 2026-07-29T00:05:07+00:00 | Vulnerability · Source |
| CVE-2017-7109 | suse_vex | SUSE CVE CVE-2017-7109 | known not affected: 87 recommended: 927 | 2026-07-29T00:05:05+00:00 | Vulnerability · Source |
| CVE-2017-7186 | suse_vex | SUSE CVE CVE-2017-7186 | known affected: 328 known not affected: 590 recommended: 1069 | 2026-07-29T00:05:04+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-7407 | suse_vex | SUSE CVE CVE-2017-7407 | known affected: 17 known not affected: 22 recommended: 131 | 2026-07-29T00:05:01+00:00 | Vulnerability · Source |
| CVE-2017-7544 | suse_vex | SUSE CVE CVE-2017-7544 | known affected: 28 recommended: 237 | 2026-07-29T00:04:59+00:00 | Vulnerability · Source |
| CVE-2017-7787 | suse_vex | SUSE CVE CVE-2017-7787 | known affected: 1 known not affected: 42 recommended: 417 | 2026-07-29T00:04:57+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-8395 | suse_vex | SUSE CVE CVE-2017-8395 | known affected: 1 known not affected: 134 recommended: 54 | 2026-07-29T00:04:43+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-9049 | suse_vex | SUSE CVE CVE-2017-9049 | known affected: 321 known not affected: 96 recommended: 568 | 2026-07-29T00:04:40+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-9116 | suse_vex | SUSE CVE CVE-2017-9116 | known not affected: 195 recommended: 205 | 2026-07-29T00:04:37+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-9349 | suse_vex | SUSE CVE CVE-2017-9349 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-29T00:04:29+00:00 | Vulnerability · Source |
| CVE-2017-9502 | suse_vex | SUSE CVE CVE-2017-9502 | known affected: 320 known not affected: 68 recommended: 365 | 2026-07-29T00:04:28+00:00 | Vulnerability · Source |
| CVE-2017-10074 | suse_vex | SUSE CVE CVE-2017-10074 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-29T00:04:26+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-10110 | suse_vex | SUSE CVE CVE-2017-10110 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-29T00:04:23+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-10379 | suse_vex | SUSE CVE CVE-2017-10379 | known affected: 1 known not affected: 104 recommended: 429 | 2026-07-29T00:04:19+00:00 | Vulnerability · Source |
| CVE-2017-10688 | suse_vex | SUSE CVE CVE-2017-10688 | known not affected: 144 | 2026-07-29T00:04:18+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-11113 | suse_vex | SUSE CVE CVE-2017-11113 | known affected: 1 known not affected: 251 recommended: 231 | 2026-07-29T00:04:12+00:00 | Vulnerability · Source |
| CVE-2017-11170 | suse_vex | SUSE CVE CVE-2017-11170 | known affected: 94 known not affected: 39 recommended: 136 | 2026-07-29T00:04:11+00:00 | Vulnerability · Source |