VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286561 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-2546 | suse_vex | SUSE CVE CVE-2016-2546 | known not affected: 201 recommended: 185 | 2026-07-29T00:08:14+00:00 | Vulnerability · Source |
| CVE-2016-2571 | suse_vex | SUSE CVE CVE-2016-2571 | known affected: 397 known not affected: 33 recommended: 50 | 2026-07-29T00:08:12+00:00 | Vulnerability · Source |
| CVE-2016-2794 | suse_vex | SUSE CVE CVE-2016-2794 | known affected: 2 recommended: 644 | 2026-07-29T00:08:11+00:00 | Vulnerability · Source |
| CVE-2016-2796 | suse_vex | SUSE CVE CVE-2016-2796 | known affected: 2 recommended: 648 | 2026-07-29T00:08:09+00:00 | Vulnerability · Source |
| CVE-2016-2814 | suse_vex | SUSE CVE CVE-2016-2814 | known affected: 2 known not affected: 3 recommended: 417 | 2026-07-29T00:08:08+00:00 | Vulnerability · Source |
| CVE-2016-2833 | suse_vex | SUSE CVE CVE-2016-2833 | known affected: 1 known not affected: 41 recommended: 250 | 2026-07-29T00:08:06+00:00 | Vulnerability · Source |
| CVE-2016-2851 | suse_vex | SUSE CVE CVE-2016-2851 | known affected: 31 known not affected: 31 recommended: 97 | 2026-07-29T00:08:05+00:00 | Vulnerability · Source |
| CVE-2016-3069 | suse_vex | SUSE CVE CVE-2016-3069 | known not affected: 24 recommended: 65 | 2026-07-29T00:08:03+00:00 | Vulnerability · Source |
| CVE-2016-3511 | suse_vex | SUSE CVE CVE-2016-3511 | known not affected: 406 recommended: 666 | 2026-07-29T00:08:02+00:00 | Vulnerability · Source |
| CVE-2016-3706 | suse_vex | SUSE CVE CVE-2016-3706 | known affected: 321 known not affected: 133 recommended: 1354 | 2026-07-29T00:08:00+00:00 | Vulnerability · Source |
| CVE-2016-3945 | suse_vex | SUSE CVE CVE-2016-3945 | known affected: 394 known not affected: 289 recommended: 285 | 2026-07-29T00:07:58+00:00 | Vulnerability · Source |
| CVE-2016-4002 | suse_vex | SUSE CVE CVE-2016-4002 | known affected: 398 known not affected: 421 recommended: 1945 | 2026-07-29T00:07:56+00:00 | Vulnerability · Source |
| CVE-2016-4037 | suse_vex | SUSE CVE CVE-2016-4037 | known affected: 1 known not affected: 33 recommended: 169 | 2026-07-29T00:07:54+00:00 | Vulnerability · Source |
| CVE-2016-4492 | suse_vex | SUSE CVE CVE-2016-4492 | known affected: 2 known not affected: 416 | 2026-07-29T00:07:52+00:00 | Vulnerability · Source |
| CVE-2016-4553 | suse_vex | SUSE CVE CVE-2016-4553 | known affected: 396 known not affected: 31 recommended: 49 | 2026-07-29T00:07:50+00:00 | Vulnerability · Source |
| CVE-2016-4565 | suse_vex | SUSE CVE CVE-2016-4565 | known affected: 2 known not affected: 550 recommended: 392 | 2026-07-29T00:07:49+00:00 | Vulnerability · Source |
| CVE-2016-4912 | suse_vex | SUSE CVE CVE-2016-4912 | known affected: 396 known not affected: 210 recommended: 298 | 2026-07-29T00:07:47+00:00 | Vulnerability · Source |
| CVE-2016-5106 | suse_vex | SUSE CVE CVE-2016-5106 | known affected: 396 known not affected: 162 recommended: 1855 | 2026-07-29T00:07:44+00:00 | Vulnerability · Source |
| CVE-2016-5159 | suse_vex | SUSE CVE CVE-2016-5159 | recommended: 195 | 2026-07-29T00:07:43+00:00 | Vulnerability · Source |
| CVE-2016-5238 | suse_vex | SUSE CVE CVE-2016-5238 | known affected: 323 known not affected: 454 recommended: 2341 | 2026-07-29T00:07:41+00:00 | Vulnerability · Source |
| CVE-2016-5271 | suse_vex | SUSE CVE CVE-2016-5271 | known affected: 5 recommended: 250 | 2026-07-29T00:07:39+00:00 | Vulnerability · Source |
| CVE-2016-5278 | suse_vex | SUSE CVE CVE-2016-5278 | known affected: 5 recommended: 332 | 2026-07-29T00:07:37+00:00 | Vulnerability · Source |
| CVE-2016-5353 | suse_vex | SUSE CVE CVE-2016-5353 | known not affected: 115 recommended: 533 | 2026-07-29T00:07:36+00:00 | Vulnerability · Source |
| CVE-2016-5421 | suse_vex | SUSE CVE CVE-2016-5421 | known not affected: 45 recommended: 89 | 2026-07-29T00:07:34+00:00 | Vulnerability · Source |
| CVE-2016-5423 | suse_vex | SUSE CVE CVE-2016-5423 | known affected: 1 known not affected: 2 recommended: 140 | 2026-07-29T00:07:33+00:00 | Vulnerability · Source |
| CVE-2016-5546 | suse_vex | SUSE CVE CVE-2016-5546 | known affected: 103 known not affected: 150 recommended: 354 | 2026-07-29T00:07:31+00:00 | Vulnerability · Source |
| CVE-2016-5863 | suse_vex | SUSE CVE CVE-2016-5863 | known not affected: 78 | 2026-07-29T00:07:30+00:00 | Vulnerability · Source |
| CVE-2016-6131 | suse_vex | SUSE CVE CVE-2016-6131 | known affected: 191 known not affected: 305 recommended: 54 | 2026-07-29T00:07:28+00:00 | Vulnerability · Source |
| CVE-2016-6213 | suse_vex | SUSE CVE CVE-2016-6213 | known not affected: 326 recommended: 12 | 2026-07-29T00:07:27+00:00 | Vulnerability · Source |
| CVE-2016-6302 | suse_vex | SUSE CVE CVE-2016-6302 | known affected: 325 known not affected: 314 recommended: 1063 | 2026-07-29T00:07:25+00:00 | Vulnerability · Source |
| CVE-2016-6318 | suse_vex | SUSE CVE CVE-2016-6318 | known affected: 320 recommended: 503 | 2026-07-29T00:07:24+00:00 | Vulnerability · Source |
| CVE-2016-6515 | suse_vex | SUSE CVE CVE-2016-6515 | known affected: 322 known not affected: 34 recommended: 510 | 2026-07-29T00:07:22+00:00 | Vulnerability · Source |
| CVE-2016-6787 | suse_vex | SUSE CVE CVE-2016-6787 | known not affected: 529 | 2026-07-29T00:07:20+00:00 | Vulnerability · Source |
| CVE-2016-6797 | suse_vex | SUSE CVE CVE-2016-6797 | known affected: 46 recommended: 202 | 2026-07-29T00:07:19+00:00 | Vulnerability · Source |
| CVE-2016-6906 | suse_vex | SUSE CVE CVE-2016-6906 | known affected: 12 known not affected: 1226 recommended: 56 | 2026-07-29T00:07:17+00:00 | Vulnerability · Source |
| CVE-2016-7039 | suse_vex | SUSE CVE CVE-2016-7039 | known affected: 27 known not affected: 409 recommended: 215 | 2026-07-29T00:07:16+00:00 | Vulnerability · Source |
| CVE-2016-7055 | suse_vex | SUSE CVE CVE-2016-7055 | known affected: 320 known not affected: 368 recommended: 983 | 2026-07-29T00:07:14+00:00 | Vulnerability · Source |
| CVE-2016-7167 | suse_vex | SUSE CVE CVE-2016-7167 | known affected: 337 known not affected: 56 recommended: 452 | 2026-07-29T00:07:12+00:00 | Vulnerability · Source |
| CVE-2016-7531 | suse_vex | SUSE CVE CVE-2016-7531 | known affected: 95 recommended: 182 | 2026-07-29T00:07:10+00:00 | Vulnerability · Source |
| CVE-2016-7533 | suse_vex | SUSE CVE CVE-2016-7533 | known affected: 95 recommended: 182 | 2026-07-29T00:07:08+00:00 | Vulnerability · Source |
| CVE-2016-7540 | suse_vex | SUSE CVE CVE-2016-7540 | known affected: 94 known not affected: 51 recommended: 132 | 2026-07-29T00:07:07+00:00 | Vulnerability · Source |
| CVE-2016-7543 | suse_vex | SUSE CVE CVE-2016-7543 | known affected: 1 recommended: 206 | 2026-07-29T00:07:06+00:00 | Vulnerability · Source |
| CVE-2016-7649 | suse_vex | SUSE CVE CVE-2016-7649 | known not affected: 87 | 2026-07-29T00:07:04+00:00 | Vulnerability · Source |
| CVE-2016-7795 | suse_vex | SUSE CVE CVE-2016-7795 | known not affected: 196 recommended: 154 | 2026-07-29T00:07:02+00:00 | Vulnerability · Source |
| CVE-2016-7913 | suse_vex | SUSE CVE CVE-2016-7913 | known affected: 12 known not affected: 389 recommended: 336 | 2026-07-29T00:07:01+00:00 | Vulnerability · Source |
| CVE-2016-7923 | suse_vex | SUSE CVE CVE-2016-7923 | known affected: 320 recommended: 186 | 2026-07-29T00:06:59+00:00 | Vulnerability · Source |
| CVE-2016-7924 | suse_vex | SUSE CVE CVE-2016-7924 | known affected: 320 recommended: 182 | 2026-07-29T00:06:58+00:00 | Vulnerability · Source |
| CVE-2016-7949 | suse_vex | SUSE CVE CVE-2016-7949 | known affected: 36 recommended: 270 | 2026-07-29T00:06:56+00:00 | Vulnerability · Source |
| CVE-2016-7953 | suse_vex | SUSE CVE CVE-2016-7953 | known affected: 24 recommended: 261 | 2026-07-29T00:06:55+00:00 | Vulnerability · Source |
| CVE-2016-8283 | suse_vex | SUSE CVE CVE-2016-8283 | known affected: 35 known not affected: 163 recommended: 630 | 2026-07-29T00:06:53+00:00 | Vulnerability · Source |