VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283936 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7914 | suse_vex | SUSE CVE CVE-2016-7914 | known not affected: 139 recommended: 121 | 2026-07-26T00:54:45+00:00 | Vulnerability · Source |
| CVE-2016-7916 | suse_vex | SUSE CVE CVE-2016-7916 | known not affected: 228 recommended: 168 | 2026-07-26T00:54:43+00:00 | Vulnerability · Source |
| CVE-2016-7925 | suse_vex | SUSE CVE CVE-2016-7925 | known affected: 320 recommended: 186 | 2026-07-26T00:54:41+00:00 | Vulnerability · Source |
| CVE-2016-7929 | suse_vex | SUSE CVE CVE-2016-7929 | known affected: 320 recommended: 182 | 2026-07-26T00:54:39+00:00 | Vulnerability · Source |
| CVE-2016-7930 | suse_vex | SUSE CVE CVE-2016-7930 | known affected: 320 recommended: 182 | 2026-07-26T00:54:38+00:00 | Vulnerability · Source |
| CVE-2016-7935 | suse_vex | SUSE CVE CVE-2016-7935 | known affected: 320 recommended: 186 | 2026-07-26T00:54:36+00:00 | Vulnerability · Source |
| CVE-2016-7936 | suse_vex | SUSE CVE CVE-2016-7936 | known affected: 320 recommended: 186 | 2026-07-26T00:54:34+00:00 | Vulnerability · Source |
| CVE-2016-7942 | suse_vex | SUSE CVE CVE-2016-7942 | known affected: 72 recommended: 297 | 2026-07-26T00:54:32+00:00 | Vulnerability · Source |
| CVE-2016-7946 | suse_vex | SUSE CVE CVE-2016-7946 | known affected: 36 recommended: 270 | 2026-07-26T00:54:29+00:00 | Vulnerability · Source |
| CVE-2016-7947 | suse_vex | SUSE CVE CVE-2016-7947 | known affected: 394 known not affected: 62 recommended: 467 | 2026-07-26T00:54:27+00:00 | Vulnerability · Source |
| CVE-2016-7951 | suse_vex | SUSE CVE CVE-2016-7951 | known affected: 36 recommended: 270 | 2026-07-26T00:54:24+00:00 | Vulnerability · Source |
| CVE-2016-7970 | suse_vex | SUSE CVE CVE-2016-7970 | recommended: 139 | 2026-07-26T00:54:22+00:00 | Vulnerability · Source |
| CVE-2016-7972 | suse_vex | SUSE CVE CVE-2016-7972 | recommended: 156 | 2026-07-26T00:54:19+00:00 | Vulnerability · Source |
| CVE-2016-7973 | suse_vex | SUSE CVE CVE-2016-7973 | known affected: 320 recommended: 186 | 2026-07-26T00:54:17+00:00 | Vulnerability · Source |
| CVE-2016-7975 | suse_vex | SUSE CVE CVE-2016-7975 | known affected: 320 recommended: 186 | 2026-07-26T00:54:14+00:00 | Vulnerability · Source |
| CVE-2016-7976 | suse_vex | SUSE CVE CVE-2016-7976 | recommended: 200 | 2026-07-26T00:54:12+00:00 | Vulnerability · Source |
| CVE-2016-7978 | suse_vex | SUSE CVE CVE-2016-7978 | recommended: 231 | 2026-07-26T00:54:10+00:00 | Vulnerability · Source |
| CVE-2016-7979 | suse_vex | SUSE CVE CVE-2016-7979 | recommended: 313 | 2026-07-26T00:54:07+00:00 | Vulnerability · Source |
| CVE-2016-7983 | suse_vex | SUSE CVE CVE-2016-7983 | known affected: 320 recommended: 186 | 2026-07-26T00:54:05+00:00 | Vulnerability · Source |
| CVE-2016-7985 | suse_vex | SUSE CVE CVE-2016-7985 | known affected: 320 recommended: 182 | 2026-07-26T00:54:03+00:00 | Vulnerability · Source |
| CVE-2016-7986 | suse_vex | SUSE CVE CVE-2016-7986 | known affected: 320 recommended: 182 | 2026-07-26T00:54:00+00:00 | Vulnerability · Source |
| CVE-2016-7992 | suse_vex | SUSE CVE CVE-2016-7992 | known affected: 320 recommended: 186 | 2026-07-26T00:53:58+00:00 | Vulnerability · Source |
| CVE-2016-7994 | suse_vex | SUSE CVE CVE-2016-7994 | known affected: 420 known not affected: 136 recommended: 1754 | 2026-07-26T00:53:55+00:00 | Vulnerability · Source |
| CVE-2016-7995 | suse_vex | SUSE CVE CVE-2016-7995 | known affected: 420 known not affected: 136 recommended: 1783 | 2026-07-26T00:53:52+00:00 | Vulnerability · Source |
| CVE-2016-8318 | suse_vex | SUSE CVE CVE-2016-8318 | known not affected: 78 | 2026-07-26T00:53:50+00:00 | Vulnerability · Source |
| CVE-2016-8328 | suse_vex | SUSE CVE CVE-2016-8328 | known affected: 15 known not affected: 150 | 2026-07-26T00:53:47+00:00 | Vulnerability · Source |
| CVE-2016-8331 | suse_vex | SUSE CVE CVE-2016-8331 | known affected: 47 recommended: 61 | 2026-07-26T00:53:45+00:00 | Vulnerability · Source |
| CVE-2016-8492 | suse_vex | SUSE CVE CVE-2016-8492 | known not affected: 115 | 2026-07-26T00:53:42+00:00 | Vulnerability · Source |
| CVE-2016-8568 | suse_vex | SUSE CVE CVE-2016-8568 | recommended: 156 | 2026-07-26T00:53:40+00:00 | Vulnerability · Source |
| CVE-2016-8576 | suse_vex | SUSE CVE CVE-2016-8576 | known affected: 421 known not affected: 137 recommended: 1897 | 2026-07-26T00:53:37+00:00 | Vulnerability · Source |
| CVE-2016-8578 | suse_vex | SUSE CVE CVE-2016-8578 | known affected: 421 known not affected: 136 recommended: 1834 | 2026-07-26T00:53:35+00:00 | Vulnerability · Source |
| CVE-2016-8602 | suse_vex | SUSE CVE CVE-2016-8602 | known affected: 45 recommended: 267 | 2026-07-26T00:53:33+00:00 | Vulnerability · Source |
| CVE-2016-8605 | suse_vex | SUSE CVE CVE-2016-8605 | known affected: 1 recommended: 500 | 2026-07-26T00:53:30+00:00 | Vulnerability · Source |
| CVE-2016-8610 | suse_vex | SUSE CVE CVE-2016-8610 | known affected: 320 known not affected: 370 recommended: 862 | 2026-07-26T00:53:28+00:00 | Vulnerability · Source |
| CVE-2016-8615 | suse_vex | SUSE CVE CVE-2016-8615 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:25+00:00 | Vulnerability · Source |
| CVE-2016-8619 | suse_vex | SUSE CVE CVE-2016-8619 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:23+00:00 | Vulnerability · Source |
| CVE-2016-8620 | suse_vex | SUSE CVE CVE-2016-8620 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:21+00:00 | Vulnerability · Source |
| CVE-2016-8621 | suse_vex | SUSE CVE CVE-2016-8621 | known affected: 337 known not affected: 34 recommended: 449 | 2026-07-26T00:53:18+00:00 | Vulnerability · Source |
| CVE-2016-8622 | suse_vex | SUSE CVE CVE-2016-8622 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:17+00:00 | Vulnerability · Source |
| CVE-2016-8623 | suse_vex | SUSE CVE CVE-2016-8623 | known affected: 340 known not affected: 21 recommended: 449 | 2026-07-26T00:53:15+00:00 | Vulnerability · Source |
| CVE-2016-8632 | suse_vex | SUSE CVE CVE-2016-8632 | known affected: 68 known not affected: 347 recommended: 438 | 2026-07-26T00:53:13+00:00 | Vulnerability · Source |
| CVE-2016-8649 | suse_vex | SUSE CVE CVE-2016-8649 | known not affected: 11 recommended: 3 | 2026-07-26T00:53:12+00:00 | Vulnerability · Source |
| CVE-2016-8650 | suse_vex | SUSE CVE CVE-2016-8650 | known affected: 14 known not affected: 484 recommended: 12 | 2026-07-26T00:53:10+00:00 | Vulnerability · Source |
| CVE-2016-8659 | suse_vex | SUSE CVE CVE-2016-8659 | known not affected: 49 recommended: 369 | 2026-07-26T00:53:09+00:00 | Vulnerability · Source |
| CVE-2016-8666 | suse_vex | SUSE CVE CVE-2016-8666 | known not affected: 409 recommended: 192 | 2026-07-26T00:53:07+00:00 | Vulnerability · Source |
| CVE-2016-8669 | suse_vex | SUSE CVE CVE-2016-8669 | known affected: 347 known not affected: 172 recommended: 2390 | 2026-07-26T00:53:05+00:00 | Vulnerability · Source |
| CVE-2016-8677 | suse_vex | SUSE CVE CVE-2016-8677 | known affected: 94 known not affected: 63 recommended: 132 | 2026-07-26T00:53:04+00:00 | Vulnerability · Source |
| CVE-2016-8682 | suse_vex | SUSE CVE CVE-2016-8682 | known affected: 95 recommended: 182 | 2026-07-26T00:53:02+00:00 | Vulnerability · Source |
| CVE-2016-8683 | suse_vex | SUSE CVE CVE-2016-8683 | known affected: 95 recommended: 182 | 2026-07-26T00:53:00+00:00 | Vulnerability · Source |
| CVE-2016-8684 | suse_vex | SUSE CVE CVE-2016-8684 | known affected: 95 recommended: 182 | 2026-07-26T00:52:59+00:00 | Vulnerability · Source |