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-2016-10069 | suse_vex | SUSE CVE CVE-2016-10069 | known not affected: 49 recommended: 168 | 2026-07-26T00:49:49+00:00 | Vulnerability · Source |
| CVE-2016-10094 | suse_vex | SUSE CVE CVE-2016-10094 | known affected: 62 known not affected: 13 recommended: 289 | 2026-07-26T00:49:41+00:00 | Vulnerability · Source |
| CVE-2016-10095 | suse_vex | SUSE CVE CVE-2016-10095 | known affected: 438 known not affected: 79 recommended: 286 | 2026-07-26T00:49:39+00:00 | Vulnerability · Source |
| CVE-2016-10109 | suse_vex | SUSE CVE CVE-2016-10109 | known affected: 394 known not affected: 13 recommended: 339 | 2026-07-26T00:49:38+00:00 | Vulnerability · Source |
| CVE-2016-10145 | suse_vex | SUSE CVE CVE-2016-10145 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:49:36+00:00 | Vulnerability · Source |
| CVE-2016-10147 | suse_vex | SUSE CVE CVE-2016-10147 | known affected: 14 known not affected: 421 recommended: 12 | 2026-07-26T00:49:35+00:00 | Vulnerability · Source |
| CVE-2016-10166 | suse_vex | SUSE CVE CVE-2016-10166 | known affected: 1456 known not affected: 45 recommended: 1719 | 2026-07-26T00:49:32+00:00 | Vulnerability · Source |
| CVE-2016-10168 | suse_vex | SUSE CVE CVE-2016-10168 | known affected: 394 known not affected: 33 recommended: 1797 | 2026-07-26T00:49:28+00:00 | Vulnerability · Source |
| CVE-2016-10171 | suse_vex | SUSE CVE CVE-2016-10171 | known affected: 30 recommended: 57 | 2026-07-26T00:49:27+00:00 | Vulnerability · Source |
| CVE-2016-10209 | suse_vex | SUSE CVE CVE-2016-10209 | known affected: 24 known not affected: 16 recommended: 25 | 2026-07-26T00:49:25+00:00 | Vulnerability · Source |
| CVE-2016-10220 | suse_vex | SUSE CVE CVE-2016-10220 | known affected: 36 known not affected: 32 recommended: 240 | 2026-07-26T00:49:24+00:00 | Vulnerability · Source |
| CVE-2016-10243 | suse_vex | SUSE CVE CVE-2016-10243 | known not affected: 9311 recommended: 227408 | 2026-07-26T00:48:53+00:00 | Vulnerability · Source |
| CVE-2016-10248 | suse_vex | SUSE CVE CVE-2016-10248 | known not affected: 94 recommended: 4 | 2026-07-26T00:48:51+00:00 | Vulnerability · Source |
| CVE-2016-10254 | suse_vex | SUSE CVE CVE-2016-10254 | known affected: 136 recommended: 172 | 2026-07-26T00:48:50+00:00 | Vulnerability · Source |
| CVE-2016-10272 | suse_vex | SUSE CVE CVE-2016-10272 | known affected: 441 known not affected: 99 recommended: 276 | 2026-07-26T00:48:48+00:00 | Vulnerability · Source |
| CVE-2016-10328 | suse_vex | SUSE CVE CVE-2016-10328 | known affected: 9 known not affected: 63 recommended: 22 | 2026-07-26T00:48:47+00:00 | Vulnerability · Source |
| CVE-2016-10906 | suse_vex | SUSE CVE CVE-2016-10906 | known affected: 21 known not affected: 144 recommended: 216 | 2026-07-26T00:48:42+00:00 | Vulnerability · Source |
| CVE-2016-1000338 | suse_vex | SUSE CVE CVE-2016-1000338 | known not affected: 18 recommended: 134 | 2026-07-26T00:48:41+00:00 | Vulnerability · Source |
| CVE-2017-0478 | suse_vex | SUSE CVE CVE-2017-0478 | known affected: 16 known not affected: 40 | 2026-07-26T00:48:36+00:00 | Vulnerability · Source |
| CVE-2017-0605 | suse_vex | SUSE CVE CVE-2017-0605 | known not affected: 64 | 2026-07-26T00:48:35+00:00 | Vulnerability · Source |
| CVE-2017-0627 | suse_vex | SUSE CVE CVE-2017-0627 | known not affected: 64 | 2026-07-26T00:48:33+00:00 | Vulnerability · Source |
| CVE-2017-0630 | suse_vex | SUSE CVE CVE-2017-0630 | known not affected: 64 | 2026-07-26T00:48:32+00:00 | Vulnerability · Source |
| CVE-2017-0902 | suse_vex | SUSE CVE CVE-2017-0902 | known not affected: 54 recommended: 98 | 2026-07-26T00:48:28+00:00 | Vulnerability · Source |
| CVE-2017-1376 | suse_vex | SUSE CVE CVE-2017-1376 | known affected: 72 known not affected: 65 | 2026-07-26T00:48:27+00:00 | Vulnerability · Source |
| CVE-2017-2356 | suse_vex | SUSE CVE CVE-2017-2356 | known not affected: 248 recommended: 927 | 2026-07-26T00:48:25+00:00 | Vulnerability · Source |
| CVE-2017-2363 | suse_vex | SUSE CVE CVE-2017-2363 | known not affected: 248 recommended: 927 | 2026-07-26T00:48:23+00:00 | Vulnerability · Source |
| CVE-2017-2371 | suse_vex | SUSE CVE CVE-2017-2371 | known not affected: 248 recommended: 939 | 2026-07-26T00:48:20+00:00 | Vulnerability · Source |
| CVE-2017-2496 | suse_vex | SUSE CVE CVE-2017-2496 | known affected: 98 known not affected: 169 recommended: 939 | 2026-07-26T00:48:19+00:00 | Vulnerability · Source |
| CVE-2017-2579 | suse_vex | SUSE CVE CVE-2017-2579 | known affected: 16 recommended: 251 | 2026-07-26T00:48:16+00:00 | Vulnerability · Source |
| CVE-2017-2581 | suse_vex | SUSE CVE CVE-2017-2581 | known affected: 16 recommended: 78 | 2026-07-26T00:48:15+00:00 | Vulnerability · Source |
| CVE-2017-2584 | suse_vex | SUSE CVE CVE-2017-2584 | known affected: 12 known not affected: 447 recommended: 222 | 2026-07-26T00:48:13+00:00 | Vulnerability · Source |
| CVE-2017-2586 | suse_vex | SUSE CVE CVE-2017-2586 | known affected: 16 recommended: 56 | 2026-07-26T00:48:12+00:00 | Vulnerability · Source |
| CVE-2017-2618 | suse_vex | SUSE CVE CVE-2017-2618 | known not affected: 781 recommended: 12 | 2026-07-26T00:48:11+00:00 | Vulnerability · Source |
| CVE-2017-2620 | suse_vex | SUSE CVE CVE-2017-2620 | known affected: 360 known not affected: 191 recommended: 2385 | 2026-07-26T00:48:09+00:00 | Vulnerability · Source |
| CVE-2017-2628 | suse_vex | SUSE CVE CVE-2017-2628 | known not affected: 63 | 2026-07-26T00:48:07+00:00 | Vulnerability · Source |
| CVE-2017-2634 | suse_vex | SUSE CVE CVE-2017-2634 | known not affected: 54 | 2026-07-26T00:48:05+00:00 | Vulnerability · Source |
| CVE-2017-2669 | suse_vex | SUSE CVE CVE-2017-2669 | recommended: 82 | 2026-07-26T00:48:02+00:00 | Vulnerability · Source |
| CVE-2017-2671 | suse_vex | SUSE CVE CVE-2017-2671 | known affected: 14 known not affected: 320 recommended: 335 | 2026-07-26T00:48:00+00:00 | Vulnerability · Source |
| CVE-2017-3135 | suse_vex | SUSE CVE CVE-2017-3135 | known affected: 377 known not affected: 387 recommended: 958 | 2026-07-26T00:47:57+00:00 | Vulnerability · Source |
| CVE-2017-3139 | suse_vex | SUSE CVE CVE-2017-3139 | known affected: 63 known not affected: 118 | 2026-07-26T00:47:54+00:00 | Vulnerability · Source |
| CVE-2017-3143 | suse_vex | SUSE CVE CVE-2017-3143 | known not affected: 405 recommended: 869 | 2026-07-26T00:47:51+00:00 | Vulnerability · Source |
| CVE-2017-3169 | suse_vex | SUSE CVE CVE-2017-3169 | recommended: 169 | 2026-07-26T00:47:47+00:00 | Vulnerability · Source |
| CVE-2017-3238 | suse_vex | SUSE CVE CVE-2017-3238 | known not affected: 93 recommended: 667 | 2026-07-26T00:47:46+00:00 | Vulnerability · Source |
| CVE-2017-3253 | suse_vex | SUSE CVE CVE-2017-3253 | known affected: 124 known not affected: 166 recommended: 584 | 2026-07-26T00:47:44+00:00 | Vulnerability · Source |
| CVE-2017-3256 | suse_vex | SUSE CVE CVE-2017-3256 | known not affected: 93 | 2026-07-26T00:47:43+00:00 | Vulnerability · Source |
| CVE-2017-3259 | suse_vex | SUSE CVE CVE-2017-3259 | known affected: 36 known not affected: 150 recommended: 270 | 2026-07-26T00:47:41+00:00 | Vulnerability · Source |
| CVE-2017-3261 | suse_vex | SUSE CVE CVE-2017-3261 | known affected: 518 known not affected: 166 recommended: 584 | 2026-07-26T00:47:40+00:00 | Vulnerability · Source |
| CVE-2017-3302 | suse_vex | SUSE CVE CVE-2017-3302 | known affected: 35 known not affected: 104 recommended: 657 | 2026-07-26T00:47:39+00:00 | Vulnerability · Source |
| CVE-2017-3305 | suse_vex | SUSE CVE CVE-2017-3305 | known not affected: 93 recommended: 28 | 2026-07-26T00:47:37+00:00 | Vulnerability · Source |
| CVE-2017-3308 | suse_vex | SUSE CVE CVE-2017-3308 | known affected: 35 known not affected: 104 recommended: 649 | 2026-07-26T00:47:36+00:00 | Vulnerability · Source |