VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285063 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-7156 | suse_vex | SUSE CVE CVE-2016-7156 | known affected: 394 known not affected: 166 recommended: 1815 | 2026-07-26T00:56:08+00:00 | Vulnerability · Source |
| CVE-2016-7163 | suse_vex | SUSE CVE CVE-2016-7163 | recommended: 203 | 2026-07-26T00:56:06+00:00 | Vulnerability · Source |
| CVE-2016-7170 | suse_vex | SUSE CVE CVE-2016-7170 | known affected: 421 known not affected: 136 recommended: 1834 | 2026-07-26T00:56:03+00:00 | Vulnerability · Source |
| CVE-2016-7423 | suse_vex | SUSE CVE CVE-2016-7423 | known affected: 394 known not affected: 177 recommended: 1688 | 2026-07-26T00:55:59+00:00 | Vulnerability · Source |
| CVE-2016-7426 | suse_vex | SUSE CVE CVE-2016-7426 | known affected: 30 recommended: 114 | 2026-07-26T00:55:57+00:00 | Vulnerability · Source |
| CVE-2016-7427 | suse_vex | SUSE CVE CVE-2016-7427 | known affected: 30 recommended: 109 | 2026-07-26T00:55:55+00:00 | Vulnerability · Source |
| CVE-2016-7428 | suse_vex | SUSE CVE CVE-2016-7428 | known affected: 30 recommended: 109 | 2026-07-26T00:55:52+00:00 | Vulnerability · Source |
| CVE-2016-7429 | suse_vex | SUSE CVE CVE-2016-7429 | known affected: 30 recommended: 114 | 2026-07-26T00:55:50+00:00 | Vulnerability · Source |
| CVE-2016-7444 | suse_vex | SUSE CVE CVE-2016-7444 | known affected: 8 recommended: 148 | 2026-07-26T00:55:47+00:00 | Vulnerability · Source |
| 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-7514 | suse_vex | SUSE CVE CVE-2016-7514 | known affected: 95 known not affected: 14 recommended: 168 | 2026-07-26T00:55:43+00:00 | Vulnerability · Source |
| CVE-2016-7516 | suse_vex | SUSE CVE CVE-2016-7516 | known affected: 95 recommended: 182 | 2026-07-26T00:55:40+00:00 | Vulnerability · Source |
| CVE-2016-7517 | suse_vex | SUSE CVE CVE-2016-7517 | known affected: 95 recommended: 182 | 2026-07-26T00:55:38+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-7526 | suse_vex | SUSE CVE CVE-2016-7526 | known affected: 95 recommended: 168 | 2026-07-26T00:55:26+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-7587 | suse_vex | SUSE CVE CVE-2016-7587 | known not affected: 87 recommended: 927 | 2026-07-26T00:55:14+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-7632 | suse_vex | SUSE CVE CVE-2016-7632 | known not affected: 87 recommended: 927 | 2026-07-26T00:55:09+00:00 | Vulnerability · Source |
| CVE-2016-7635 | suse_vex | SUSE CVE CVE-2016-7635 | known not affected: 87 recommended: 927 | 2026-07-26T00:55:06+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-7645 | suse_vex | SUSE CVE CVE-2016-7645 | known not affected: 87 recommended: 927 | 2026-07-26T00:55:01+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-7656 | suse_vex | SUSE CVE CVE-2016-7656 | known not affected: 87 recommended: 939 | 2026-07-26T00:54:53+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-7907 | suse_vex | SUSE CVE CVE-2016-7907 | known affected: 420 known not affected: 136 recommended: 1754 | 2026-07-26T00:54:49+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-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 |