VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-8318 | suse_vex | SUSE CVE CVE-2016-8318 | known not affected: 78 | 2026-07-26T00:53:50+00:00 | Vulnerability · Source |
| CVE-2016-8328 | suse_vex | SUSE CVE CVE-2016-8328 | known affected: 15 known not affected: 150 | 2026-07-26T00:53:47+00:00 | Vulnerability · Source |
| CVE-2016-8331 | suse_vex | SUSE CVE CVE-2016-8331 | known affected: 47 recommended: 61 | 2026-07-26T00:53:45+00:00 | Vulnerability · Source |
| CVE-2016-8492 | suse_vex | SUSE CVE CVE-2016-8492 | known not affected: 115 | 2026-07-26T00:53:42+00:00 | Vulnerability · Source |
| CVE-2016-8568 | suse_vex | SUSE CVE CVE-2016-8568 | recommended: 156 | 2026-07-26T00:53:40+00:00 | Vulnerability · Source |
| CVE-2016-8578 | suse_vex | SUSE CVE CVE-2016-8578 | known affected: 421 known not affected: 136 recommended: 1834 | 2026-07-26T00:53:35+00:00 | Vulnerability · Source |
| CVE-2016-8615 | suse_vex | SUSE CVE CVE-2016-8615 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:25+00:00 | Vulnerability · Source |
| CVE-2016-8619 | suse_vex | SUSE CVE CVE-2016-8619 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:23+00:00 | Vulnerability · Source |
| CVE-2016-8632 | suse_vex | SUSE CVE CVE-2016-8632 | known affected: 68 known not affected: 347 recommended: 438 | 2026-07-26T00:53:13+00:00 | Vulnerability · Source |
| CVE-2016-8649 | suse_vex | SUSE CVE CVE-2016-8649 | known not affected: 11 recommended: 3 | 2026-07-26T00:53:12+00:00 | Vulnerability · Source |
| CVE-2016-8650 | suse_vex | SUSE CVE CVE-2016-8650 | known affected: 14 known not affected: 484 recommended: 12 | 2026-07-26T00:53:10+00:00 | Vulnerability · Source |
| CVE-2016-8666 | suse_vex | SUSE CVE CVE-2016-8666 | known not affected: 409 recommended: 192 | 2026-07-26T00:53:07+00:00 | Vulnerability · Source |
| CVE-2016-8677 | suse_vex | SUSE CVE CVE-2016-8677 | known affected: 94 known not affected: 63 recommended: 132 | 2026-07-26T00:53:04+00:00 | Vulnerability · Source |
| CVE-2016-8682 | suse_vex | SUSE CVE CVE-2016-8682 | known affected: 95 recommended: 182 | 2026-07-26T00:53:02+00:00 | Vulnerability · Source |
| CVE-2016-8683 | suse_vex | SUSE CVE CVE-2016-8683 | known affected: 95 recommended: 182 | 2026-07-26T00:53:00+00:00 | Vulnerability · Source |
| CVE-2016-8684 | suse_vex | SUSE CVE CVE-2016-8684 | known affected: 95 recommended: 182 | 2026-07-26T00:52:59+00:00 | Vulnerability · Source |
| CVE-2016-8688 | suse_vex | SUSE CVE CVE-2016-8688 | known affected: 394 known not affected: 17 recommended: 222 | 2026-07-26T00:52:57+00:00 | Vulnerability · Source |
| CVE-2016-8692 | suse_vex | SUSE CVE CVE-2016-8692 | known affected: 1 recommended: 204 | 2026-07-26T00:52:54+00:00 | Vulnerability · Source |
| CVE-2016-8693 | suse_vex | SUSE CVE CVE-2016-8693 | known affected: 1 recommended: 204 | 2026-07-26T00:52:52+00:00 | Vulnerability · Source |
| CVE-2016-8707 | suse_vex | SUSE CVE CVE-2016-8707 | known affected: 1 recommended: 204 | 2026-07-26T00:52:48+00:00 | Vulnerability · Source |
| CVE-2016-8745 | suse_vex | SUSE CVE CVE-2016-8745 | known affected: 440 known not affected: 122 recommended: 268 | 2026-07-26T00:52:46+00:00 | Vulnerability · Source |
| CVE-2016-8862 | suse_vex | SUSE CVE CVE-2016-8862 | known affected: 1 recommended: 218 | 2026-07-26T00:52:45+00:00 | Vulnerability · Source |
| CVE-2016-8864 | suse_vex | SUSE CVE CVE-2016-8864 | known affected: 378 known not affected: 383 recommended: 998 | 2026-07-26T00:52:43+00:00 | Vulnerability · Source |
| CVE-2016-8881 | suse_vex | SUSE CVE CVE-2016-8881 | known affected: 1 recommended: 200 | 2026-07-26T00:52:41+00:00 | Vulnerability · Source |
| CVE-2016-9042 | suse_vex | SUSE CVE CVE-2016-9042 | known affected: 31 recommended: 98 | 2026-07-26T00:52:35+00:00 | Vulnerability · Source |
| CVE-2016-9064 | suse_vex | SUSE CVE CVE-2016-9064 | known affected: 2 recommended: 569 | 2026-07-26T00:52:33+00:00 | Vulnerability · Source |
| CVE-2016-9066 | suse_vex | SUSE CVE CVE-2016-9066 | known affected: 2 recommended: 655 | 2026-07-26T00:52:31+00:00 | Vulnerability · Source |
| CVE-2016-9068 | suse_vex | SUSE CVE CVE-2016-9068 | known affected: 1 known not affected: 79 recommended: 321 | 2026-07-26T00:52:28+00:00 | Vulnerability · Source |
| CVE-2016-9077 | suse_vex | SUSE CVE CVE-2016-9077 | known affected: 1 known not affected: 60 recommended: 321 | 2026-07-26T00:52:25+00:00 | Vulnerability · Source |
| CVE-2016-9083 | suse_vex | SUSE CVE CVE-2016-9083 | known affected: 12 known not affected: 75 recommended: 222 | 2026-07-26T00:52:20+00:00 | Vulnerability · Source |
| CVE-2016-9084 | suse_vex | SUSE CVE CVE-2016-9084 | known affected: 12 known not affected: 156 recommended: 222 | 2026-07-26T00:52:18+00:00 | Vulnerability · Source |
| CVE-2016-9106 | suse_vex | SUSE CVE CVE-2016-9106 | known affected: 421 known not affected: 211 recommended: 1834 | 2026-07-26T00:52:14+00:00 | Vulnerability · Source |
| CVE-2016-9113 | suse_vex | SUSE CVE CVE-2016-9113 | known affected: 1080 recommended: 20 | 2026-07-26T00:52:13+00:00 | Vulnerability · Source |
| CVE-2016-9114 | suse_vex | SUSE CVE CVE-2016-9114 | recommended: 20 | 2026-07-26T00:52:11+00:00 | Vulnerability · Source |
| CVE-2016-9118 | suse_vex | SUSE CVE CVE-2016-9118 | recommended: 20 | 2026-07-26T00:52:10+00:00 | Vulnerability · Source |
| CVE-2016-9120 | suse_vex | SUSE CVE CVE-2016-9120 | known not affected: 34 | 2026-07-26T00:52:08+00:00 | Vulnerability · Source |
| CVE-2016-9191 | suse_vex | SUSE CVE CVE-2016-9191 | known affected: 12 known not affected: 509 recommended: 186 | 2026-07-26T00:52:05+00:00 | Vulnerability · Source |
| CVE-2016-9273 | suse_vex | SUSE CVE CVE-2016-9273 | known affected: 433 known not affected: 81 recommended: 298 | 2026-07-26T00:52:03+00:00 | Vulnerability · Source |
| CVE-2016-9310 | suse_vex | SUSE CVE CVE-2016-9310 | known affected: 30 recommended: 114 | 2026-07-26T00:52:02+00:00 | Vulnerability · Source |
| CVE-2016-9317 | suse_vex | SUSE CVE CVE-2016-9317 | known affected: 406 known not affected: 1248 recommended: 244 | 2026-07-26T00:52:00+00:00 | Vulnerability · Source |
| CVE-2016-9318 | suse_vex | SUSE CVE CVE-2016-9318 | recommended: 178 | 2026-07-26T00:51:59+00:00 | Vulnerability · Source |
| CVE-2016-9374 | suse_vex | SUSE CVE CVE-2016-9374 | known affected: 1 recommended: 586 | 2026-07-26T00:51:58+00:00 | Vulnerability · Source |
| CVE-2016-9378 | suse_vex | SUSE CVE CVE-2016-9378 | known affected: 12 known not affected: 41 recommended: 377 | 2026-07-26T00:51:56+00:00 | Vulnerability · Source |
| CVE-2016-9383 | suse_vex | SUSE CVE CVE-2016-9383 | known affected: 334 known not affected: 6 recommended: 556 | 2026-07-26T00:51:55+00:00 | Vulnerability · Source |
| CVE-2016-9384 | suse_vex | SUSE CVE CVE-2016-9384 | known affected: 332 known not affected: 65 recommended: 430 | 2026-07-26T00:51:53+00:00 | Vulnerability · Source |
| CVE-2016-9387 | suse_vex | SUSE CVE CVE-2016-9387 | known not affected: 130 recommended: 136 | 2026-07-26T00:51:51+00:00 | Vulnerability · Source |
| CVE-2016-9389 | suse_vex | SUSE CVE CVE-2016-9389 | known affected: 37 recommended: 194 | 2026-07-26T00:51:50+00:00 | Vulnerability · Source |
| CVE-2016-9395 | suse_vex | SUSE CVE CVE-2016-9395 | known affected: 45 known not affected: 131 recommended: 200 | 2026-07-26T00:51:48+00:00 | Vulnerability · Source |
| CVE-2016-9424 | suse_vex | SUSE CVE CVE-2016-9424 | known not affected: 35 recommended: 4 | 2026-07-26T00:51:45+00:00 | Vulnerability · Source |
| CVE-2016-9426 | suse_vex | SUSE CVE CVE-2016-9426 | known not affected: 15 | 2026-07-26T00:51:44+00:00 | Vulnerability · Source |