VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287961 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-8079 | suse_vex | SUSE CVE CVE-2015-8079 | known not affected: 32 recommended: 246 | 2026-07-31T01:50:10+00:00 | Vulnerability · Source |
| CVE-2015-8569 | suse_vex | SUSE CVE CVE-2015-8569 | known not affected: 357 recommended: 320 | 2026-07-31T01:50:07+00:00 | Vulnerability · Source |
| CVE-2015-8605 | suse_vex | SUSE CVE CVE-2015-8605 | known affected: 403 recommended: 446 | 2026-07-31T01:50:06+00:00 | Vulnerability · Source |
| CVE-2015-8710 | suse_vex | SUSE CVE CVE-2015-8710 | known not affected: 102 recommended: 169 | 2026-07-31T01:50:04+00:00 | Vulnerability · Source |
| CVE-2015-8782 | suse_vex | SUSE CVE CVE-2015-8782 | known affected: 394 known not affected: 267 recommended: 301 | 2026-07-31T01:50:01+00:00 | Vulnerability · Source |
| CVE-2015-8899 | suse_vex | SUSE CVE CVE-2015-8899 | known affected: 22 known not affected: 2 recommended: 98 | 2026-07-31T01:49:59+00:00 | Vulnerability · Source |
| CVE-2015-8928 | suse_vex | SUSE CVE CVE-2015-8928 | known affected: 406 known not affected: 127 recommended: 225 | 2026-07-31T01:49:58+00:00 | Vulnerability · Source |
| CVE-2015-8946 | suse_vex | SUSE CVE CVE-2015-8946 | known not affected: 14 recommended: 29 | 2026-07-31T01:49:56+00:00 | Vulnerability · Source |
| CVE-2015-9004 | suse_vex | SUSE CVE CVE-2015-9004 | known not affected: 26 recommended: 43 | 2026-07-31T01:49:54+00:00 | Vulnerability · Source |
| CVE-2015-9262 | suse_vex | SUSE CVE CVE-2015-9262 | known not affected: 46 recommended: 269 | 2026-07-31T01:49:53+00:00 | Vulnerability · Source |
| CVE-2016-0594 | suse_vex | SUSE CVE CVE-2016-0594 | known affected: 2 known not affected: 176 recommended: 10 | 2026-07-31T01:49:51+00:00 | Vulnerability · Source |
| CVE-2016-0607 | suse_vex | SUSE CVE CVE-2016-0607 | known affected: 2 known not affected: 176 recommended: 10 | 2026-07-31T01:49:49+00:00 | Vulnerability · Source |
| CVE-2016-0616 | suse_vex | SUSE CVE CVE-2016-0616 | known not affected: 121 recommended: 688 | 2026-07-31T01:49:47+00:00 | Vulnerability · Source |
| CVE-2016-0714 | suse_vex | SUSE CVE CVE-2016-0714 | known affected: 394 recommended: 252 | 2026-07-31T01:49:45+00:00 | Vulnerability · Source |
| CVE-2016-1371 | suse_vex | SUSE CVE CVE-2016-1371 | known not affected: 12 | 2026-07-31T01:49:43+00:00 | Vulnerability · Source |
| CVE-2016-1549 | suse_vex | SUSE CVE CVE-2016-1549 | known affected: 24 known not affected: 20 recommended: 131 | 2026-07-31T01:49:41+00:00 | Vulnerability · Source |
| CVE-2016-1550 | suse_vex | SUSE CVE CVE-2016-1550 | known affected: 30 recommended: 114 | 2026-07-31T01:49:40+00:00 | Vulnerability · Source |
| CVE-2016-1939 | suse_vex | SUSE CVE CVE-2016-1939 | known affected: 21 recommended: 246 | 2026-07-31T01:49:38+00:00 | Vulnerability · Source |
| CVE-2016-1956 | suse_vex | SUSE CVE CVE-2016-1956 | known affected: 38 known not affected: 183 recommended: 336 | 2026-07-31T01:49:36+00:00 | Vulnerability · Source |
| CVE-2016-1957 | suse_vex | SUSE CVE CVE-2016-1957 | known affected: 2 recommended: 648 | 2026-07-31T01:49:35+00:00 | Vulnerability · Source |
| CVE-2016-2108 | suse_vex | SUSE CVE CVE-2016-2108 | known affected: 4 recommended: 211 | 2026-07-31T01:49:33+00:00 | Vulnerability · Source |
| CVE-2016-2318 | suse_vex | SUSE CVE CVE-2016-2318 | known not affected: 551 recommended: 14 | 2026-07-31T01:49:30+00:00 | Vulnerability · Source |
| CVE-2016-2538 | suse_vex | SUSE CVE CVE-2016-2538 | known affected: 321 known not affected: 12 recommended: 631 | 2026-07-31T01:49:28+00:00 | Vulnerability · Source |
| CVE-2016-2544 | suse_vex | SUSE CVE CVE-2016-2544 | known not affected: 139 recommended: 185 | 2026-07-31T01:49:27+00:00 | Vulnerability · Source |
| CVE-2016-2550 | suse_vex | SUSE CVE CVE-2016-2550 | known not affected: 49 | 2026-07-31T01:49:25+00:00 | Vulnerability · Source |
| CVE-2016-2776 | suse_vex | SUSE CVE CVE-2016-2776 | known affected: 352 known not affected: 144 recommended: 992 | 2026-07-31T01:49:23+00:00 | Vulnerability · Source |
| CVE-2016-2793 | suse_vex | SUSE CVE CVE-2016-2793 | known affected: 2 recommended: 644 | 2026-07-31T01:49:22+00:00 | Vulnerability · Source |
| CVE-2016-2795 | suse_vex | SUSE CVE CVE-2016-2795 | known affected: 2 recommended: 644 | 2026-07-31T01:49:20+00:00 | Vulnerability · Source |
| CVE-2016-2797 | suse_vex | SUSE CVE CVE-2016-2797 | known affected: 2 recommended: 644 | 2026-07-31T01:49:18+00:00 | Vulnerability · Source |
| CVE-2016-2824 | suse_vex | SUSE CVE CVE-2016-2824 | known affected: 2 recommended: 621 | 2026-07-31T01:49:16+00:00 | Vulnerability · Source |
| CVE-2016-2825 | suse_vex | SUSE CVE CVE-2016-2825 | known affected: 1 known not affected: 41 recommended: 250 | 2026-07-31T01:49:14+00:00 | Vulnerability · Source |
| CVE-2016-2830 | suse_vex | SUSE CVE CVE-2016-2830 | known affected: 3 known not affected: 83 recommended: 494 | 2026-07-31T01:49:13+00:00 | Vulnerability · Source |
| CVE-2016-3182 | suse_vex | SUSE CVE CVE-2016-3182 | known not affected: 108 | 2026-07-31T01:49:11+00:00 | Vulnerability · Source |
| CVE-2016-3189 | suse_vex | SUSE CVE CVE-2016-3189 | known affected: 395 recommended: 465 | 2026-07-31T01:49:09+00:00 | Vulnerability · Source |
| CVE-2016-3492 | suse_vex | SUSE CVE CVE-2016-3492 | known affected: 1 known not affected: 93 recommended: 620 | 2026-07-31T01:49:07+00:00 | Vulnerability · Source |
| CVE-2016-3621 | suse_vex | SUSE CVE CVE-2016-3621 | known not affected: 30 recommended: 22 | 2026-07-31T01:49:06+00:00 | Vulnerability · Source |
| CVE-2016-3715 | suse_vex | SUSE CVE CVE-2016-3715 | known not affected: 151 recommended: 838 | 2026-07-31T01:49:04+00:00 | Vulnerability · Source |
| CVE-2016-4020 | suse_vex | SUSE CVE CVE-2016-4020 | known affected: 395 known not affected: 162 recommended: 1886 | 2026-07-31T01:49:01+00:00 | Vulnerability · Source |
| CVE-2016-4053 | suse_vex | SUSE CVE CVE-2016-4053 | known not affected: 55 recommended: 48 | 2026-07-31T01:49:00+00:00 | Vulnerability · Source |
| CVE-2016-4447 | suse_vex | SUSE CVE CVE-2016-4447 | known affected: 1 recommended: 116 | 2026-07-31T01:48:57+00:00 | Vulnerability · Source |
| CVE-2016-4454 | suse_vex | SUSE CVE CVE-2016-4454 | known affected: 394 known not affected: 164 recommended: 1899 | 2026-07-31T01:48:55+00:00 | Vulnerability · Source |
| CVE-2016-4622 | suse_vex | SUSE CVE CVE-2016-4622 | known not affected: 162 recommended: 927 | 2026-07-31T01:48:53+00:00 | Vulnerability · Source |
| CVE-2016-4963 | suse_vex | SUSE CVE CVE-2016-4963 | known affected: 1 known not affected: 3 recommended: 63 | 2026-07-31T01:48:51+00:00 | Vulnerability · Source |
| CVE-2016-5107 | suse_vex | SUSE CVE CVE-2016-5107 | known affected: 395 known not affected: 163 recommended: 1855 | 2026-07-31T01:48:47+00:00 | Vulnerability · Source |
| CVE-2016-5258 | suse_vex | SUSE CVE CVE-2016-5258 | known affected: 5 recommended: 438 | 2026-07-31T01:48:44+00:00 | Vulnerability · Source |
| CVE-2016-5321 | suse_vex | SUSE CVE CVE-2016-5321 | known affected: 394 known not affected: 310 recommended: 276 | 2026-07-31T01:48:41+00:00 | Vulnerability · Source |
| CVE-2016-5420 | suse_vex | SUSE CVE CVE-2016-5420 | known affected: 17 known not affected: 21 recommended: 135 | 2026-07-31T01:48:39+00:00 | Vulnerability · Source |
| CVE-2016-5542 | suse_vex | SUSE CVE CVE-2016-5542 | known affected: 394 known not affected: 109 recommended: 805 | 2026-07-31T01:48:37+00:00 | Vulnerability · Source |
| CVE-2016-5630 | suse_vex | SUSE CVE CVE-2016-5630 | known affected: 1 known not affected: 93 recommended: 10 | 2026-07-31T01:48:35+00:00 | Vulnerability · Source |
| CVE-2016-5691 | suse_vex | SUSE CVE CVE-2016-5691 | known affected: 95 recommended: 202 | 2026-07-31T01:48:33+00:00 | Vulnerability · Source |