VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285064 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-0657 | suse_vex | SUSE CVE CVE-2016-0657 | known not affected: 121 | 2026-07-26T01:06:43+00:00 | Vulnerability · Source |
| CVE-2016-0663 | suse_vex | SUSE CVE CVE-2016-0663 | known not affected: 121 | 2026-07-26T01:06:40+00:00 | Vulnerability · Source |
| CVE-2016-0668 | suse_vex | SUSE CVE CVE-2016-0668 | known not affected: 121 recommended: 630 | 2026-07-26T01:06:38+00:00 | Vulnerability · Source |
| CVE-2016-0687 | suse_vex | SUSE CVE CVE-2016-0687 | known affected: 112 known not affected: 93 recommended: 788 | 2026-07-26T01:06:35+00:00 | Vulnerability · Source |
| CVE-2016-0695 | suse_vex | SUSE CVE CVE-2016-0695 | known affected: 112 known not affected: 93 recommended: 364 | 2026-07-26T01:06:33+00:00 | Vulnerability · Source |
| CVE-2016-0703 | suse_vex | SUSE CVE CVE-2016-0703 | recommended: 184 | 2026-07-26T01:06:30+00:00 | Vulnerability · Source |
| CVE-2016-0705 | suse_vex | SUSE CVE CVE-2016-0705 | known affected: 321 known not affected: 322 recommended: 1336 | 2026-07-26T01:06:28+00:00 | Vulnerability · Source |
| CVE-2016-0706 | suse_vex | SUSE CVE CVE-2016-0706 | known affected: 394 known not affected: 4 recommended: 252 | 2026-07-26T01:06:25+00:00 | Vulnerability · Source |
| CVE-2016-0729 | suse_vex | SUSE CVE CVE-2016-0729 | recommended: 192 | 2026-07-26T01:06:22+00:00 | Vulnerability · Source |
| CVE-2016-0736 | suse_vex | SUSE CVE CVE-2016-0736 | known affected: 86 known not affected: 38 recommended: 415 | 2026-07-26T01:06:20+00:00 | Vulnerability · Source |
| CVE-2016-0749 | suse_vex | SUSE CVE CVE-2016-0749 | known not affected: 139 recommended: 137 | 2026-07-26T01:06:17+00:00 | Vulnerability · Source |
| CVE-2016-0755 | suse_vex | SUSE CVE CVE-2016-0755 | known affected: 337 known not affected: 21 recommended: 474 | 2026-07-26T01:06:14+00:00 | Vulnerability · Source |
| CVE-2016-0758 | suse_vex | SUSE CVE CVE-2016-0758 | known affected: 5 known not affected: 443 recommended: 438 | 2026-07-26T01:06:12+00:00 | Vulnerability · Source |
| CVE-2016-0763 | suse_vex | SUSE CVE CVE-2016-0763 | known affected: 394 known not affected: 26 recommended: 220 | 2026-07-26T01:06:09+00:00 | Vulnerability · Source |
| CVE-2016-0766 | suse_vex | SUSE CVE CVE-2016-0766 | known affected: 1 known not affected: 20 recommended: 252 | 2026-07-26T01:06:07+00:00 | Vulnerability · Source |
| CVE-2016-0771 | suse_vex | SUSE CVE CVE-2016-0771 | known affected: 320 known not affected: 749 recommended: 3467 | 2026-07-26T01:06:04+00:00 | Vulnerability · Source |
| CVE-2016-0772 | suse_vex | SUSE CVE CVE-2016-0772 | known affected: 320 known not affected: 443 recommended: 1456 | 2026-07-26T01:06:01+00:00 | Vulnerability · Source |
| CVE-2016-0773 | suse_vex | SUSE CVE CVE-2016-0773 | known affected: 1 known not affected: 19 recommended: 263 | 2026-07-26T01:05:58+00:00 | Vulnerability · Source |
| CVE-2016-0777 | suse_vex | SUSE CVE CVE-2016-0777 | known affected: 322 recommended: 508 | 2026-07-26T01:05:55+00:00 | Vulnerability · Source |
| CVE-2016-0795 | suse_vex | SUSE CVE CVE-2016-0795 | recommended: 5100 | 2026-07-26T01:05:52+00:00 | Vulnerability · Source |
| CVE-2016-0797 | suse_vex | SUSE CVE CVE-2016-0797 | known affected: 321 known not affected: 236 recommended: 1076 | 2026-07-26T01:05:49+00:00 | Vulnerability · Source |
| CVE-2016-0800 | suse_vex | SUSE CVE CVE-2016-0800 | known affected: 321 known not affected: 292 recommended: 1078 | 2026-07-26T01:05:47+00:00 | Vulnerability · Source |
| CVE-2016-0821 | suse_vex | SUSE CVE CVE-2016-0821 | known not affected: 582 | 2026-07-26T01:05:44+00:00 | Vulnerability · Source |
| CVE-2016-0823 | suse_vex | SUSE CVE CVE-2016-0823 | known not affected: 403 recommended: 193 | 2026-07-26T01:05:42+00:00 | Vulnerability · Source |
| CVE-2016-1237 | suse_vex | SUSE CVE CVE-2016-1237 | known affected: 3 known not affected: 637 recommended: 189 | 2026-07-26T01:05:40+00:00 | Vulnerability · Source |
| CVE-2016-1245 | suse_vex | SUSE CVE CVE-2016-1245 | known affected: 3 known not affected: 125 recommended: 349 | 2026-07-26T01:05:37+00:00 | Vulnerability · Source |
| CVE-2016-1246 | suse_vex | SUSE CVE CVE-2016-1246 | known affected: 17 recommended: 78 | 2026-07-26T01:05:35+00:00 | Vulnerability · Source |
| CVE-2016-1251 | suse_vex | SUSE CVE CVE-2016-1251 | known affected: 17 recommended: 78 | 2026-07-26T01:05:33+00:00 | Vulnerability · Source |
| CVE-2016-1283 | suse_vex | SUSE CVE CVE-2016-1283 | known affected: 320 known not affected: 172 recommended: 741 | 2026-07-26T01:05:30+00:00 | Vulnerability · Source |
| CVE-2016-1285 | suse_vex | SUSE CVE CVE-2016-1285 | known affected: 490 recommended: 1003 | 2026-07-26T01:05:28+00:00 | Vulnerability · Source |
| CVE-2016-1372 | suse_vex | SUSE CVE CVE-2016-1372 | known not affected: 12 recommended: 16 | 2026-07-26T01:05:25+00:00 | Vulnerability · Source |
| CVE-2016-1521 | suse_vex | SUSE CVE CVE-2016-1521 | known affected: 395 recommended: 253 | 2026-07-26T01:05:23+00:00 | Vulnerability · Source |
| CVE-2016-1526 | suse_vex | SUSE CVE CVE-2016-1526 | known affected: 1 recommended: 66 | 2026-07-26T01:05:20+00:00 | Vulnerability · Source |
| CVE-2016-1541 | suse_vex | SUSE CVE CVE-2016-1541 | known affected: 394 recommended: 233 | 2026-07-26T01:05:18+00:00 | Vulnerability · Source |
| CVE-2016-1547 | suse_vex | SUSE CVE CVE-2016-1547 | known affected: 30 recommended: 114 | 2026-07-26T01:05:16+00:00 | Vulnerability · Source |
| CVE-2016-1567 | suse_vex | SUSE CVE CVE-2016-1567 | known affected: 320 known not affected: 22 recommended: 252 | 2026-07-26T01:05:13+00:00 | Vulnerability · Source |
| CVE-2016-1568 | suse_vex | SUSE CVE CVE-2016-1568 | known affected: 321 known not affected: 178 recommended: 2322 | 2026-07-26T01:05:11+00:00 | Vulnerability · Source |
| CVE-2016-1571 | suse_vex | SUSE CVE CVE-2016-1571 | known affected: 322 known not affected: 12 recommended: 544 | 2026-07-26T01:05:08+00:00 | Vulnerability · Source |
| CVE-2016-1572 | suse_vex | SUSE CVE CVE-2016-1572 | known affected: 11 recommended: 232 | 2026-07-26T01:05:06+00:00 | Vulnerability · Source |
| CVE-2016-1577 | suse_vex | SUSE CVE CVE-2016-1577 | known affected: 1 recommended: 204 | 2026-07-26T01:05:03+00:00 | Vulnerability · Source |
| CVE-2016-1583 | suse_vex | SUSE CVE CVE-2016-1583 | known affected: 35 known not affected: 447 recommended: 552 | 2026-07-26T01:05:01+00:00 | Vulnerability · Source |
| CVE-2016-1714 | suse_vex | SUSE CVE CVE-2016-1714 | known affected: 320 known not affected: 197 recommended: 2395 | 2026-07-26T01:04:56+00:00 | Vulnerability · Source |
| CVE-2016-1833 | suse_vex | SUSE CVE CVE-2016-1833 | known affected: 1 known not affected: 102 recommended: 532 | 2026-07-26T01:04:54+00:00 | Vulnerability · Source |
| CVE-2016-1834 | suse_vex | SUSE CVE CVE-2016-1834 | known affected: 1 known not affected: 102 recommended: 532 | 2026-07-26T01:04:52+00:00 | Vulnerability · Source |
| CVE-2016-1835 | suse_vex | SUSE CVE CVE-2016-1835 | known affected: 1 known not affected: 102 recommended: 532 | 2026-07-26T01:04:50+00:00 | Vulnerability · Source |
| CVE-2016-1838 | suse_vex | SUSE CVE CVE-2016-1838 | known affected: 1 known not affected: 102 recommended: 532 | 2026-07-26T01:04:47+00:00 | Vulnerability · Source |
| CVE-2016-1840 | suse_vex | SUSE CVE CVE-2016-1840 | known affected: 321 known not affected: 102 recommended: 606 | 2026-07-26T01:04:45+00:00 | Vulnerability · Source |
| CVE-2016-1931 | suse_vex | SUSE CVE CVE-2016-1931 | known affected: 49 recommended: 287 | 2026-07-26T01:04:42+00:00 | Vulnerability · Source |
| CVE-2016-1937 | suse_vex | SUSE CVE CVE-2016-1937 | known not affected: 175 recommended: 250 | 2026-07-26T01:04:39+00:00 | Vulnerability · Source |
| CVE-2016-1949 | suse_vex | SUSE CVE CVE-2016-1949 | known affected: 1 known not affected: 43 recommended: 250 | 2026-07-26T01:04:37+00:00 | Vulnerability · Source |