VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284336 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2016-1955 | suse_vex | SUSE CVE CVE-2016-1955 | known affected: 38 known not affected: 183 recommended: 336 | 2026-07-26T01:04:34+00:00 | Vulnerability · Source |
| CVE-2016-1958 | suse_vex | SUSE CVE CVE-2016-1958 | known affected: 2 recommended: 642 | 2026-07-26T01:04:32+00:00 | Vulnerability · Source |
| CVE-2016-1959 | suse_vex | SUSE CVE CVE-2016-1959 | known affected: 38 known not affected: 183 recommended: 250 | 2026-07-26T01:04:29+00:00 | Vulnerability · Source |
| CVE-2016-1961 | suse_vex | SUSE CVE CVE-2016-1961 | known affected: 2 recommended: 648 | 2026-07-26T01:04:27+00:00 | Vulnerability · Source |
| CVE-2016-1965 | suse_vex | SUSE CVE CVE-2016-1965 | known affected: 2 recommended: 642 | 2026-07-26T01:04:25+00:00 | Vulnerability · Source |
| CVE-2016-1969 | suse_vex | SUSE CVE CVE-2016-1969 | known affected: 38 known not affected: 183 | 2026-07-26T01:04:22+00:00 | Vulnerability · Source |
| CVE-2016-2037 | suse_vex | SUSE CVE CVE-2016-2037 | known affected: 350 recommended: 337 | 2026-07-26T01:04:20+00:00 | Vulnerability · Source |
| CVE-2016-2053 | suse_vex | SUSE CVE CVE-2016-2053 | known not affected: 42 recommended: 363 | 2026-07-26T01:04:17+00:00 | Vulnerability · Source |
| CVE-2016-2089 | suse_vex | SUSE CVE CVE-2016-2089 | known affected: 1 recommended: 204 | 2026-07-26T01:04:15+00:00 | Vulnerability · Source |
| CVE-2016-2111 | suse_vex | SUSE CVE CVE-2016-2111 | known affected: 320 known not affected: 90 recommended: 4427 | 2026-07-26T01:04:11+00:00 | Vulnerability · Source |
| CVE-2016-2112 | suse_vex | SUSE CVE CVE-2016-2112 | known affected: 320 known not affected: 90 recommended: 4427 | 2026-07-26T01:04:08+00:00 | Vulnerability · Source |
| CVE-2016-2114 | suse_vex | SUSE CVE CVE-2016-2114 | known not affected: 635 recommended: 53 | 2026-07-26T01:04:06+00:00 | Vulnerability · Source |
| CVE-2016-2115 | suse_vex | SUSE CVE CVE-2016-2115 | known affected: 320 known not affected: 90 recommended: 4427 | 2026-07-26T01:04:03+00:00 | Vulnerability · Source |