VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7447 | suse_vex | SUSE CVE CVE-2016-7447 | known affected: 3 known not affected: 103 recommended: 14 | 2026-07-26T00:55:45+00:00 | Vulnerability · Source |
| CVE-2016-7519 | suse_vex | SUSE CVE CVE-2016-7519 | known affected: 95 recommended: 182 | 2026-07-26T00:55:35+00:00 | Vulnerability · Source |
| CVE-2016-7521 | suse_vex | SUSE CVE CVE-2016-7521 | known affected: 94 known not affected: 51 recommended: 132 | 2026-07-26T00:55:33+00:00 | Vulnerability · Source |
| CVE-2016-7522 | suse_vex | SUSE CVE CVE-2016-7522 | known affected: 95 recommended: 182 | 2026-07-26T00:55:31+00:00 | Vulnerability · Source |
| CVE-2016-7523 | suse_vex | SUSE CVE CVE-2016-7523 | known affected: 95 known not affected: 14 recommended: 168 | 2026-07-26T00:55:28+00:00 | Vulnerability · Source |
| CVE-2016-7527 | suse_vex | SUSE CVE CVE-2016-7527 | known affected: 95 recommended: 182 | 2026-07-26T00:55:23+00:00 | Vulnerability · Source |
| CVE-2016-7529 | suse_vex | SUSE CVE CVE-2016-7529 | known affected: 95 recommended: 182 | 2026-07-26T00:55:21+00:00 | Vulnerability · Source |
| CVE-2016-7532 | suse_vex | SUSE CVE CVE-2016-7532 | known affected: 94 known not affected: 51 recommended: 132 | 2026-07-26T00:55:19+00:00 | Vulnerability · Source |
| CVE-2016-7537 | suse_vex | SUSE CVE CVE-2016-7537 | known affected: 95 recommended: 182 | 2026-07-26T00:55:17+00:00 | Vulnerability · Source |
| CVE-2016-7611 | suse_vex | SUSE CVE CVE-2016-7611 | known not affected: 87 | 2026-07-26T00:55:11+00:00 | Vulnerability · Source |
| CVE-2016-7642 | suse_vex | SUSE CVE CVE-2016-7642 | known not affected: 87 | 2026-07-26T00:55:04+00:00 | Vulnerability · Source |
| CVE-2016-7648 | suse_vex | SUSE CVE CVE-2016-7648 | known not affected: 87 | 2026-07-26T00:54:59+00:00 | Vulnerability · Source |
| CVE-2016-7652 | suse_vex | SUSE CVE CVE-2016-7652 | known not affected: 87 recommended: 927 | 2026-07-26T00:54:56+00:00 | Vulnerability · Source |
| CVE-2016-7654 | suse_vex | SUSE CVE CVE-2016-7654 | known not affected: 87 recommended: 939 | 2026-07-26T00:54:54+00:00 | Vulnerability · Source |
| CVE-2016-7798 | suse_vex | SUSE CVE CVE-2016-7798 | known affected: 5 known not affected: 41 recommended: 83 | 2026-07-26T00:54:51+00:00 | Vulnerability · Source |
| CVE-2016-7912 | suse_vex | SUSE CVE CVE-2016-7912 | known not affected: 34 | 2026-07-26T00:54:47+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-7929 | suse_vex | SUSE CVE CVE-2016-7929 | known affected: 320 recommended: 182 | 2026-07-26T00:54:39+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-7951 | suse_vex | SUSE CVE CVE-2016-7951 | known affected: 36 recommended: 270 | 2026-07-26T00:54:24+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-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-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-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-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-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-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-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 |
| CVE-2016-8692 | suse_vex | SUSE CVE CVE-2016-8692 | known affected: 1 recommended: 204 | 2026-07-26T00:52:54+00:00 | Vulnerability · Source |
| CVE-2016-8693 | suse_vex | SUSE CVE CVE-2016-8693 | known affected: 1 recommended: 204 | 2026-07-26T00:52:52+00:00 | Vulnerability · Source |
| CVE-2016-8707 | suse_vex | SUSE CVE CVE-2016-8707 | known affected: 1 recommended: 204 | 2026-07-26T00:52:48+00:00 | Vulnerability · Source |
| CVE-2016-8862 | suse_vex | SUSE CVE CVE-2016-8862 | known affected: 1 recommended: 218 | 2026-07-26T00:52:45+00:00 | Vulnerability · Source |
| CVE-2016-8881 | suse_vex | SUSE CVE CVE-2016-8881 | known affected: 1 recommended: 200 | 2026-07-26T00:52:41+00:00 | Vulnerability · Source |
| CVE-2016-9042 | suse_vex | SUSE CVE CVE-2016-9042 | known affected: 31 recommended: 98 | 2026-07-26T00:52:35+00:00 | Vulnerability · Source |
| CVE-2016-9064 | suse_vex | SUSE CVE CVE-2016-9064 | known affected: 2 recommended: 569 | 2026-07-26T00:52:33+00:00 | Vulnerability · Source |
| CVE-2016-9068 | suse_vex | SUSE CVE CVE-2016-9068 | known affected: 1 known not affected: 79 recommended: 321 | 2026-07-26T00:52:28+00:00 | Vulnerability · Source |
| CVE-2016-9113 | suse_vex | SUSE CVE CVE-2016-9113 | known affected: 1080 recommended: 20 | 2026-07-26T00:52:13+00:00 | Vulnerability · Source |
| CVE-2016-9114 | suse_vex | SUSE CVE CVE-2016-9114 | recommended: 20 | 2026-07-26T00:52:11+00:00 | Vulnerability · Source |
| CVE-2016-9118 | suse_vex | SUSE CVE CVE-2016-9118 | recommended: 20 | 2026-07-26T00:52:10+00:00 | Vulnerability · Source |
| CVE-2016-9120 | suse_vex | SUSE CVE CVE-2016-9120 | known not affected: 34 | 2026-07-26T00:52:08+00:00 | Vulnerability · Source |
| CVE-2016-9310 | suse_vex | SUSE CVE CVE-2016-9310 | known affected: 30 recommended: 114 | 2026-07-26T00:52:02+00:00 | Vulnerability · Source |
| CVE-2016-9383 | suse_vex | SUSE CVE CVE-2016-9383 | known affected: 334 known not affected: 6 recommended: 556 | 2026-07-26T00:51:55+00:00 | Vulnerability · Source |
| CVE-2016-9387 | suse_vex | SUSE CVE CVE-2016-9387 | known not affected: 130 recommended: 136 | 2026-07-26T00:51:51+00:00 | Vulnerability · Source |