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-2015-4142 | suse_vex | SUSE CVE CVE-2015-4142 | known affected: 9 known not affected: 14 recommended: 104 | 2026-07-28T00:13:21+00:00 | Vulnerability · Source |
| CVE-2015-4842 | suse_vex | SUSE CVE CVE-2015-4842 | known affected: 76 known not affected: 231 recommended: 703 | 2026-07-28T00:13:16+00:00 | Vulnerability · Source |
| CVE-2015-4901 | suse_vex | SUSE CVE CVE-2015-4901 | known affected: 74 known not affected: 270 recommended: 235 | 2026-07-28T00:13:15+00:00 | Vulnerability · Source |
| CVE-2015-5292 | suse_vex | SUSE CVE CVE-2015-5292 | known not affected: 93 recommended: 27 | 2026-07-28T00:13:12+00:00 | Vulnerability · Source |
| CVE-2015-5327 | suse_vex | SUSE CVE CVE-2015-5327 | known not affected: 71 | 2026-07-28T00:13:11+00:00 | Vulnerability · Source |
| CVE-2015-5370 | suse_vex | SUSE CVE CVE-2015-5370 | known affected: 321 known not affected: 57 recommended: 4198 | 2026-07-28T00:13:07+00:00 | Vulnerability · Source |
| CVE-2015-5928 | suse_vex | SUSE CVE CVE-2015-5928 | known not affected: 18 recommended: 229 | 2026-07-28T00:13:05+00:00 | Vulnerability · Source |
| CVE-2015-6360 | suse_vex | SUSE CVE CVE-2015-6360 | known not affected: 36 recommended: 166 | 2026-07-28T00:13:04+00:00 | Vulnerability · Source |
| CVE-2015-7555 | suse_vex | SUSE CVE CVE-2015-7555 | known affected: 394 recommended: 232 | 2026-07-28T00:13:01+00:00 | Vulnerability · Source |
| CVE-2015-7853 | suse_vex | SUSE CVE CVE-2015-7853 | known affected: 1 known not affected: 31 recommended: 109 | 2026-07-28T00:12:58+00:00 | Vulnerability · Source |
| CVE-2015-8374 | suse_vex | SUSE CVE CVE-2015-8374 | known not affected: 379 recommended: 12 | 2026-07-28T00:12:55+00:00 | Vulnerability · Source |
| CVE-2015-8394 | suse_vex | SUSE CVE CVE-2015-8394 | known affected: 15 known not affected: 114 recommended: 118 | 2026-07-28T00:12:54+00:00 | Vulnerability · Source |
| CVE-2015-8540 | suse_vex | SUSE CVE CVE-2015-8540 | known affected: 385 known not affected: 3 recommended: 361 | 2026-07-28T00:12:52+00:00 | Vulnerability · Source |
| CVE-2015-8630 | suse_vex | SUSE CVE CVE-2015-8630 | known affected: 300 known not affected: 164 recommended: 650 | 2026-07-28T00:12:50+00:00 | Vulnerability · Source |
| CVE-2015-8711 | suse_vex | SUSE CVE CVE-2015-8711 | known affected: 69 recommended: 534 | 2026-07-28T00:12:49+00:00 | Vulnerability · Source |
| CVE-2015-8715 | suse_vex | SUSE CVE CVE-2015-8715 | known affected: 63 recommended: 92 | 2026-07-28T00:12:47+00:00 | Vulnerability · Source |
| CVE-2015-8720 | suse_vex | SUSE CVE CVE-2015-8720 | known affected: 63 recommended: 528 | 2026-07-28T00:12:46+00:00 | Vulnerability · Source |
| CVE-2015-8726 | suse_vex | SUSE CVE CVE-2015-8726 | known affected: 63 recommended: 528 | 2026-07-28T00:12:44+00:00 | Vulnerability · Source |
| CVE-2015-8898 | suse_vex | SUSE CVE CVE-2015-8898 | known affected: 76 known not affected: 14 recommended: 200 | 2026-07-28T00:12:42+00:00 | Vulnerability · Source |
| CVE-2015-8924 | suse_vex | SUSE CVE CVE-2015-8924 | known affected: 24 recommended: 51 | 2026-07-28T00:12:40+00:00 | Vulnerability · Source |
| CVE-2015-8925 | suse_vex | SUSE CVE CVE-2015-8925 | known affected: 23 recommended: 38 | 2026-07-28T00:12:39+00:00 | Vulnerability · Source |
| CVE-2015-9016 | suse_vex | SUSE CVE CVE-2015-9016 | known not affected: 31 | 2026-07-28T00:12:35+00:00 | Vulnerability · Source |
| CVE-2016-0611 | suse_vex | SUSE CVE CVE-2016-0611 | known affected: 2 known not affected: 147 recommended: 10 | 2026-07-28T00:12:34+00:00 | Vulnerability · Source |
| CVE-2016-0617 | suse_vex | SUSE CVE CVE-2016-0617 | known affected: 28 known not affected: 6 recommended: 59 | 2026-07-28T00:12:32+00:00 | Vulnerability · Source |
| CVE-2016-0667 | suse_vex | SUSE CVE CVE-2016-0667 | known not affected: 110 | 2026-07-28T00:12:29+00:00 | Vulnerability · Source |
| CVE-2016-1523 | suse_vex | SUSE CVE CVE-2016-1523 | known affected: 1 recommended: 141 | 2026-07-28T00:12:25+00:00 | Vulnerability · Source |
| CVE-2016-1546 | suse_vex | SUSE CVE CVE-2016-1546 | known not affected: 153 recommended: 57 | 2026-07-28T00:12:24+00:00 | Vulnerability · Source |
| CVE-2016-1974 | suse_vex | SUSE CVE CVE-2016-1974 | known affected: 2 recommended: 600 | 2026-07-28T00:12:19+00:00 | Vulnerability · Source |
| CVE-2016-2073 | suse_vex | SUSE CVE CVE-2016-2073 | known affected: 1 recommended: 102 | 2026-07-28T00:12:18+00:00 | Vulnerability · Source |
| CVE-2016-2099 | suse_vex | SUSE CVE CVE-2016-2099 | known not affected: 12 recommended: 172 | 2026-07-28T00:12:17+00:00 | Vulnerability · Source |
| CVE-2016-2189 | suse_vex | SUSE CVE CVE-2016-2189 | recommended: 18 | 2026-07-28T00:12:11+00:00 | Vulnerability · Source |
| CVE-2016-2193 | suse_vex | SUSE CVE CVE-2016-2193 | known not affected: 351 recommended: 80 | 2026-07-28T00:12:09+00:00 | Vulnerability · Source |
| CVE-2016-2226 | suse_vex | SUSE CVE CVE-2016-2226 | known affected: 1 known not affected: 460 | 2026-07-28T00:12:08+00:00 | Vulnerability · Source |
| CVE-2016-2516 | suse_vex | SUSE CVE CVE-2016-2516 | known affected: 23 recommended: 99 | 2026-07-28T00:12:06+00:00 | Vulnerability · Source |
| CVE-2016-2523 | suse_vex | SUSE CVE CVE-2016-2523 | known affected: 3 recommended: 526 | 2026-07-28T00:12:03+00:00 | Vulnerability · Source |
| CVE-2016-2530 | suse_vex | SUSE CVE CVE-2016-2530 | known affected: 3 recommended: 520 | 2026-07-28T00:12:01+00:00 | Vulnerability · Source |
| CVE-2016-2774 | suse_vex | SUSE CVE CVE-2016-2774 | known affected: 1 recommended: 96 | 2026-07-28T00:12:00+00:00 | Vulnerability · Source |
| CVE-2016-3135 | suse_vex | SUSE CVE CVE-2016-3135 | known affected: 29 known not affected: 118 recommended: 165 | 2026-07-28T00:11:56+00:00 | Vulnerability · Source |
| CVE-2016-3458 | suse_vex | SUSE CVE CVE-2016-3458 | recommended: 319 | 2026-07-28T00:11:53+00:00 | Vulnerability · Source |
| CVE-2016-3689 | suse_vex | SUSE CVE CVE-2016-3689 | known affected: 24 known not affected: 93 recommended: 294 | 2026-07-28T00:11:51+00:00 | Vulnerability · Source |
| CVE-2016-4001 | suse_vex | SUSE CVE CVE-2016-4001 | known affected: 3 known not affected: 472 recommended: 197 | 2026-07-28T00:11:46+00:00 | Vulnerability · Source |
| CVE-2016-4356 | suse_vex | SUSE CVE CVE-2016-4356 | known not affected: 11 | 2026-07-28T00:11:43+00:00 | Vulnerability · Source |
| CVE-2016-4415 | suse_vex | SUSE CVE CVE-2016-4415 | known not affected: 64 | 2026-07-28T00:11:42+00:00 | Vulnerability · Source |
| CVE-2016-4490 | suse_vex | SUSE CVE CVE-2016-4490 | known not affected: 986 | 2026-07-28T00:11:40+00:00 | Vulnerability · Source |
| CVE-2016-4562 | suse_vex | SUSE CVE CVE-2016-4562 | known not affected: 480 recommended: 194 | 2026-07-28T00:11:39+00:00 | Vulnerability · Source |
| CVE-2016-4568 | suse_vex | SUSE CVE CVE-2016-4568 | known not affected: 417 | 2026-07-28T00:11:37+00:00 | Vulnerability · Source |
| CVE-2016-4574 | suse_vex | SUSE CVE CVE-2016-4574 | known affected: 321 recommended: 269 | 2026-07-28T00:11:35+00:00 | Vulnerability · Source |
| CVE-2016-4858 | suse_vex | SUSE CVE CVE-2016-4858 | known not affected: 359 | 2026-07-28T00:11:32+00:00 | Vulnerability · Source |
| CVE-2016-4964 | suse_vex | SUSE CVE CVE-2016-4964 | known affected: 394 known not affected: 202 recommended: 1662 | 2026-07-28T00:11:30+00:00 | Vulnerability · Source |
| CVE-2016-4975 | suse_vex | SUSE CVE CVE-2016-4975 | known affected: 63 known not affected: 63 recommended: 107 | 2026-07-28T00:11:29+00:00 | Vulnerability · Source |