VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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-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-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-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-2089 | suse_vex | SUSE CVE CVE-2016-2089 | known affected: 1 recommended: 204 | 2026-07-26T01:04:15+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 |
| CVE-2016-2116 | suse_vex | SUSE CVE CVE-2016-2116 | known affected: 1 recommended: 204 | 2026-07-26T01:04:01+00:00 | Vulnerability · Source |
| CVE-2016-2117 | suse_vex | SUSE CVE CVE-2016-2117 | known affected: 12 known not affected: 111 recommended: 223 | 2026-07-26T01:03:59+00:00 | Vulnerability · Source |
| CVE-2016-2126 | suse_vex | SUSE CVE CVE-2016-2126 | known affected: 411 known not affected: 709 recommended: 4211 | 2026-07-26T01:03:53+00:00 | Vulnerability · Source |
| CVE-2016-2150 | suse_vex | SUSE CVE CVE-2016-2150 | known not affected: 85 recommended: 138 | 2026-07-26T01:03:51+00:00 | Vulnerability · Source |
| CVE-2016-2161 | suse_vex | SUSE CVE CVE-2016-2161 | known affected: 87 recommended: 456 | 2026-07-26T01:03:49+00:00 | Vulnerability · Source |
| CVE-2016-2182 | suse_vex | SUSE CVE CVE-2016-2182 | known affected: 325 known not affected: 314 recommended: 1067 | 2026-07-26T01:03:44+00:00 | Vulnerability · Source |
| CVE-2016-2186 | suse_vex | SUSE CVE CVE-2016-2186 | known not affected: 274 recommended: 510 | 2026-07-26T01:03:41+00:00 | Vulnerability · Source |
| CVE-2016-2188 | suse_vex | SUSE CVE CVE-2016-2188 | known affected: 3 known not affected: 204 recommended: 396 | 2026-07-26T01:03:39+00:00 | Vulnerability · Source |
| CVE-2016-2270 | suse_vex | SUSE CVE CVE-2016-2270 | known affected: 320 known not affected: 12 recommended: 544 | 2026-07-26T01:03:36+00:00 | Vulnerability · Source |
| CVE-2016-2334 | suse_vex | SUSE CVE CVE-2016-2334 | known not affected: 3 recommended: 78 | 2026-07-26T01:03:32+00:00 | Vulnerability · Source |
| CVE-2016-2335 | suse_vex | SUSE CVE CVE-2016-2335 | recommended: 100 | 2026-07-26T01:03:30+00:00 | Vulnerability · Source |
| CVE-2016-2338 | suse_vex | SUSE CVE CVE-2016-2338 | known not affected: 300 | 2026-07-26T01:03:27+00:00 | Vulnerability · Source |
| CVE-2016-2339 | suse_vex | SUSE CVE CVE-2016-2339 | known affected: 5 known not affected: 50 recommended: 140 | 2026-07-26T01:03:25+00:00 | Vulnerability · Source |
| CVE-2016-2381 | suse_vex | SUSE CVE CVE-2016-2381 | known affected: 59 recommended: 115 | 2026-07-26T01:03:23+00:00 | Vulnerability · Source |
| CVE-2016-2383 | suse_vex | SUSE CVE CVE-2016-2383 | known affected: 31 known not affected: 79 recommended: 75 | 2026-07-26T01:03:20+00:00 | Vulnerability · Source |
| CVE-2016-2524 | suse_vex | SUSE CVE CVE-2016-2524 | known affected: 3 recommended: 442 | 2026-07-26T01:03:18+00:00 | Vulnerability · Source |
| CVE-2016-2547 | suse_vex | SUSE CVE CVE-2016-2547 | known not affected: 201 recommended: 185 | 2026-07-26T01:03:12+00:00 | Vulnerability · Source |
| CVE-2016-2549 | suse_vex | SUSE CVE CVE-2016-2549 | known not affected: 230 recommended: 185 | 2026-07-26T01:03:10+00:00 | Vulnerability · Source |
| CVE-2016-2553 | suse_vex | SUSE CVE CVE-2016-2553 | known affected: 12 known not affected: 111 | 2026-07-26T01:03:08+00:00 | Vulnerability · Source |
| CVE-2016-2790 | suse_vex | SUSE CVE CVE-2016-2790 | known affected: 2 recommended: 644 | 2026-07-26T01:02:58+00:00 | Vulnerability · Source |
| CVE-2016-2791 | suse_vex | SUSE CVE CVE-2016-2791 | known affected: 2 recommended: 644 | 2026-07-26T01:02:55+00:00 | Vulnerability · Source |
| CVE-2016-2799 | suse_vex | SUSE CVE CVE-2016-2799 | known affected: 2 recommended: 644 | 2026-07-26T01:02:53+00:00 | Vulnerability · Source |
| CVE-2016-2800 | suse_vex | SUSE CVE CVE-2016-2800 | known affected: 2 recommended: 648 | 2026-07-26T01:02:50+00:00 | Vulnerability · Source |