VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-8862 | suse_vex | SUSE CVE CVE-2016-8862 | known affected: 1 recommended: 218 | 2026-07-26T00:52:45+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-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-9310 | suse_vex | SUSE CVE CVE-2016-9310 | known affected: 30 recommended: 114 | 2026-07-26T00:52:02+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-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-9435 | suse_vex | SUSE CVE CVE-2016-9435 | known affected: 1 recommended: 87 | 2026-07-26T00:51:39+00:00 | Vulnerability · Source |
| CVE-2016-9444 | suse_vex | SUSE CVE CVE-2016-9444 | known affected: 58 known not affected: 386 recommended: 893 | 2026-07-26T00:51:33+00:00 | Vulnerability · Source |
| CVE-2016-9445 | suse_vex | SUSE CVE CVE-2016-9445 | known affected: 185 recommended: 552 | 2026-07-26T00:51:31+00:00 | Vulnerability · Source |
| CVE-2016-9534 | suse_vex | SUSE CVE CVE-2016-9534 | known not affected: 47 recommended: 4 | 2026-07-26T00:51:28+00:00 | Vulnerability · Source |
| CVE-2016-9540 | suse_vex | SUSE CVE CVE-2016-9540 | known not affected: 28 recommended: 26 | 2026-07-26T00:51:25+00:00 | Vulnerability · Source |
| CVE-2016-9560 | suse_vex | SUSE CVE CVE-2016-9560 | known affected: 37 known not affected: 125 recommended: 204 | 2026-07-26T00:51:23+00:00 | Vulnerability · Source |
| CVE-2016-9573 | suse_vex | SUSE CVE CVE-2016-9573 | recommended: 23 | 2026-07-26T00:51:22+00:00 | Vulnerability · Source |
| CVE-2016-9577 | suse_vex | SUSE CVE CVE-2016-9577 | known affected: 1 known not affected: 100 recommended: 137 | 2026-07-26T00:51:20+00:00 | Vulnerability · Source |
| CVE-2016-9580 | suse_vex | SUSE CVE CVE-2016-9580 | recommended: 20 | 2026-07-26T00:51:19+00:00 | Vulnerability · Source |
| CVE-2016-9581 | suse_vex | SUSE CVE CVE-2016-9581 | recommended: 20 | 2026-07-26T00:51:17+00:00 | Vulnerability · Source |
| CVE-2016-9632 | suse_vex | SUSE CVE CVE-2016-9632 | known affected: 1 recommended: 87 | 2026-07-26T00:51:05+00:00 | Vulnerability · Source |
| CVE-2016-9635 | suse_vex | SUSE CVE CVE-2016-9635 | known affected: 32 recommended: 86 | 2026-07-26T00:51:01+00:00 | Vulnerability · Source |
| CVE-2016-9644 | suse_vex | SUSE CVE CVE-2016-9644 | known not affected: 61 | 2026-07-26T00:50:59+00:00 | Vulnerability · Source |
| CVE-2016-9685 | suse_vex | SUSE CVE CVE-2016-9685 | known not affected: 47 recommended: 205 | 2026-07-26T00:50:58+00:00 | Vulnerability · Source |
| CVE-2016-9755 | suse_vex | SUSE CVE CVE-2016-9755 | known not affected: 34 | 2026-07-26T00:50:57+00:00 | Vulnerability · Source |
| CVE-2016-9799 | suse_vex | SUSE CVE CVE-2016-9799 | known not affected: 46 | 2026-07-26T00:50:53+00:00 | Vulnerability · Source |
| CVE-2016-9811 | suse_vex | SUSE CVE CVE-2016-9811 | known affected: 272 recommended: 845 | 2026-07-26T00:50:48+00:00 | Vulnerability · Source |
| CVE-2016-9815 | suse_vex | SUSE CVE CVE-2016-9815 | known not affected: 68 | 2026-07-26T00:50:45+00:00 | Vulnerability · Source |
| CVE-2016-9816 | suse_vex | SUSE CVE CVE-2016-9816 | known not affected: 68 | 2026-07-26T00:50:44+00:00 | Vulnerability · Source |
| CVE-2016-9818 | suse_vex | SUSE CVE CVE-2016-9818 | known not affected: 68 | 2026-07-26T00:50:42+00:00 | Vulnerability · Source |
| CVE-2016-9840 | suse_vex | SUSE CVE CVE-2016-9840 | known affected: 545 known not affected: 278 recommended: 2545 | 2026-07-26T00:50:40+00:00 | Vulnerability · Source |
| CVE-2016-9845 | suse_vex | SUSE CVE CVE-2016-9845 | known not affected: 183 recommended: 1707 | 2026-07-26T00:50:37+00:00 | Vulnerability · Source |
| CVE-2016-9895 | suse_vex | SUSE CVE CVE-2016-9895 | known affected: 1 recommended: 419 | 2026-07-26T00:50:36+00:00 | Vulnerability · Source |
| CVE-2016-9914 | suse_vex | SUSE CVE CVE-2016-9914 | known not affected: 251 | 2026-07-26T00:50:25+00:00 | Vulnerability · Source |
| CVE-2016-9932 | suse_vex | SUSE CVE CVE-2016-9932 | known affected: 333 known not affected: 55 recommended: 545 | 2026-07-26T00:50:20+00:00 | Vulnerability · Source |
| CVE-2016-9961 | suse_vex | SUSE CVE CVE-2016-9961 | recommended: 153 | 2026-07-26T00:50:10+00:00 | Vulnerability · Source |
| CVE-2016-10040 | suse_vex | SUSE CVE CVE-2016-10040 | recommended: 308 | 2026-07-26T00:50:03+00:00 | Vulnerability · Source |
| CVE-2016-10049 | suse_vex | SUSE CVE CVE-2016-10049 | known affected: 1 recommended: 218 | 2026-07-26T00:50:01+00:00 | Vulnerability · Source |
| CVE-2016-10051 | suse_vex | SUSE CVE CVE-2016-10051 | known affected: 1 recommended: 218 | 2026-07-26T00:50:00+00:00 | Vulnerability · Source |
| CVE-2016-10052 | suse_vex | SUSE CVE CVE-2016-10052 | known affected: 1 recommended: 204 | 2026-07-26T00:49:58+00:00 | Vulnerability · Source |