VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284624 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-9533 | suse_vex | SUSE CVE CVE-2016-9533 | known not affected: 47 recommended: 4 | 2026-07-26T00:51:30+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-9537 | suse_vex | SUSE CVE CVE-2016-9537 | known not affected: 149 recommended: 4 | 2026-07-26T00:51:27+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-9583 | suse_vex | SUSE CVE CVE-2016-9583 | known affected: 37 known not affected: 113 recommended: 204 | 2026-07-26T00:51:16+00:00 | Vulnerability · Source |
| CVE-2016-9587 | suse_vex | SUSE CVE CVE-2016-9587 | recommended: 30 | 2026-07-26T00:51:14+00:00 | Vulnerability · Source |
| CVE-2016-9588 | suse_vex | SUSE CVE CVE-2016-9588 | known not affected: 388 recommended: 122 | 2026-07-26T00:51:13+00:00 | Vulnerability · Source |
| CVE-2016-9603 | suse_vex | SUSE CVE CVE-2016-9603 | known not affected: 63 recommended: 268 | 2026-07-26T00:51:12+00:00 | Vulnerability · Source |
| CVE-2016-9604 | suse_vex | SUSE CVE CVE-2016-9604 | known affected: 2 known not affected: 505 recommended: 110 | 2026-07-26T00:51:10+00:00 | Vulnerability · Source |
| CVE-2016-9621 | suse_vex | SUSE CVE CVE-2016-9621 | known affected: 1 recommended: 87 | 2026-07-26T00:51:08+00:00 | Vulnerability · Source |
| CVE-2016-9630 | suse_vex | SUSE CVE CVE-2016-9630 | known affected: 1 recommended: 87 | 2026-07-26T00:51:07+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-9633 | suse_vex | SUSE CVE CVE-2016-9633 | known affected: 1 recommended: 87 | 2026-07-26T00:51:04+00:00 | Vulnerability · Source |
| CVE-2016-9634 | suse_vex | SUSE CVE CVE-2016-9634 | known affected: 32 recommended: 86 | 2026-07-26T00:51:02+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-9776 | suse_vex | SUSE CVE CVE-2016-9776 | known affected: 1 known not affected: 136 recommended: 1904 | 2026-07-26T00:50:55+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-9802 | suse_vex | SUSE CVE CVE-2016-9802 | known affected: 48 known not affected: 54 recommended: 297 | 2026-07-26T00:50:52+00:00 | Vulnerability · Source |
| CVE-2016-9806 | suse_vex | SUSE CVE CVE-2016-9806 | known affected: 45 known not affected: 165 recommended: 268 | 2026-07-26T00:50:50+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-9813 | suse_vex | SUSE CVE CVE-2016-9813 | known affected: 120 recommended: 253 | 2026-07-26T00:50:47+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-9842 | suse_vex | SUSE CVE CVE-2016-9842 | known affected: 22 known not affected: 200 recommended: 825 | 2026-07-26T00:50:39+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-9897 | suse_vex | SUSE CVE CVE-2016-9897 | known affected: 1 recommended: 418 | 2026-07-26T00:50:34+00:00 | Vulnerability · Source |
| CVE-2016-9899 | suse_vex | SUSE CVE CVE-2016-9899 | known affected: 1 recommended: 419 | 2026-07-26T00:50:32+00:00 | Vulnerability · Source |
| CVE-2016-9900 | suse_vex | SUSE CVE CVE-2016-9900 | known affected: 1 recommended: 419 | 2026-07-26T00:50:31+00:00 | Vulnerability · Source |
| CVE-2016-9901 | suse_vex | SUSE CVE CVE-2016-9901 | known affected: 1 recommended: 335 | 2026-07-26T00:50:29+00:00 | Vulnerability · Source |
| CVE-2016-9904 | suse_vex | SUSE CVE CVE-2016-9904 | known affected: 1 recommended: 418 | 2026-07-26T00:50:27+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-9917 | suse_vex | SUSE CVE CVE-2016-9917 | known affected: 50 known not affected: 106 recommended: 308 | 2026-07-26T00:50:24+00:00 | Vulnerability · Source |
| CVE-2016-9918 | suse_vex | SUSE CVE CVE-2016-9918 | known affected: 50 known not affected: 119 recommended: 312 | 2026-07-26T00:50:21+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-9941 | suse_vex | SUSE CVE CVE-2016-9941 | known affected: 44 known not affected: 4 recommended: 70 | 2026-07-26T00:50:18+00:00 | Vulnerability · Source |
| CVE-2016-9953 | suse_vex | SUSE CVE CVE-2016-9953 | known not affected: 63 | 2026-07-26T00:50:16+00:00 | Vulnerability · Source |
| CVE-2016-9957 | suse_vex | SUSE CVE CVE-2016-9957 | recommended: 156 | 2026-07-26T00:50:15+00:00 | Vulnerability · Source |