VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283936 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-8689 | suse_vex | SUSE CVE CVE-2016-8689 | known affected: 394 known not affected: 17 recommended: 222 | 2026-07-26T00:52:56+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-8704 | suse_vex | SUSE CVE CVE-2016-8704 | known not affected: 24 recommended: 105 | 2026-07-26T00:52:51+00:00 | Vulnerability · Source |
| CVE-2016-8706 | suse_vex | SUSE CVE CVE-2016-8706 | recommended: 105 | 2026-07-26T00:52:49+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-8882 | suse_vex | SUSE CVE CVE-2016-8882 | known affected: 1 recommended: 200 | 2026-07-26T00:52:39+00:00 | Vulnerability · Source |
| CVE-2016-8886 | suse_vex | SUSE CVE CVE-2016-8886 | known affected: 1 known not affected: 65 recommended: 200 | 2026-07-26T00:52:38+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-9067 | suse_vex | SUSE CVE CVE-2016-9067 | known affected: 1 known not affected: 60 recommended: 321 | 2026-07-26T00:52:30+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-9074 | suse_vex | SUSE CVE CVE-2016-9074 | known affected: 229 recommended: 677 | 2026-07-26T00:52:27+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-9079 | suse_vex | SUSE CVE CVE-2016-9079 | known affected: 2 recommended: 495 | 2026-07-26T00:52:23+00:00 | Vulnerability · Source |
| CVE-2016-9082 | suse_vex | SUSE CVE CVE-2016-9082 | known affected: 480 recommended: 423 | 2026-07-26T00:52:21+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-9105 | suse_vex | SUSE CVE CVE-2016-9105 | known affected: 421 known not affected: 211 recommended: 1834 | 2026-07-26T00:52:16+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-9131 | suse_vex | SUSE CVE CVE-2016-9131 | known affected: 378 known not affected: 386 recommended: 971 | 2026-07-26T00:52:07+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-9398 | suse_vex | SUSE CVE CVE-2016-9398 | known affected: 42 known not affected: 31 recommended: 222 | 2026-07-26T00:51:47+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 |
| CVE-2016-9431 | suse_vex | SUSE CVE CVE-2016-9431 | known not affected: 15 | 2026-07-26T00:51:42+00:00 | Vulnerability · Source |
| CVE-2016-9434 | suse_vex | SUSE CVE CVE-2016-9434 | known affected: 1 recommended: 87 | 2026-07-26T00:51:41+00:00 | Vulnerability · Source |
| CVE-2016-9435 | suse_vex | SUSE CVE CVE-2016-9435 | known affected: 1 recommended: 87 | 2026-07-26T00:51:39+00:00 | Vulnerability · Source |
| CVE-2016-9439 | suse_vex | SUSE CVE CVE-2016-9439 | known affected: 1 recommended: 87 | 2026-07-26T00:51:38+00:00 | Vulnerability · Source |