VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5387 | suse_vex | SUSE CVE CVE-2016-5387 | known affected: 426 recommended: 463 | 2026-07-26T00:58:38+00:00 | Vulnerability · Source |
| CVE-2016-5408 | suse_vex | SUSE CVE CVE-2016-5408 | known not affected: 26 | 2026-07-26T00:58:33+00:00 | Vulnerability · Source |
| CVE-2016-5412 | suse_vex | SUSE CVE CVE-2016-5412 | known not affected: 585 recommended: 87 | 2026-07-26T00:58:31+00:00 | Vulnerability · Source |
| CVE-2016-5552 | suse_vex | SUSE CVE CVE-2016-5552 | known affected: 518 known not affected: 166 recommended: 584 | 2026-07-26T00:58:20+00:00 | Vulnerability · Source |
| CVE-2016-5688 | suse_vex | SUSE CVE CVE-2016-5688 | known affected: 95 recommended: 216 | 2026-07-26T00:57:58+00:00 | Vulnerability · Source |
| CVE-2016-5696 | suse_vex | SUSE CVE CVE-2016-5696 | known affected: 17 known not affected: 412 recommended: 371 | 2026-07-26T00:57:56+00:00 | Vulnerability · Source |
| CVE-2016-5829 | suse_vex | SUSE CVE CVE-2016-5829 | known affected: 44 known not affected: 106 recommended: 523 | 2026-07-26T00:57:53+00:00 | Vulnerability · Source |
| CVE-2016-5842 | suse_vex | SUSE CVE CVE-2016-5842 | known affected: 95 known not affected: 14 recommended: 202 | 2026-07-26T00:57:47+00:00 | Vulnerability · Source |
| CVE-2016-5857 | suse_vex | SUSE CVE CVE-2016-5857 | known not affected: 55 | 2026-07-26T00:57:42+00:00 | Vulnerability · Source |
| CVE-2016-6162 | suse_vex | SUSE CVE CVE-2016-6162 | known not affected: 42 | 2026-07-26T00:57:37+00:00 | Vulnerability · Source |
| CVE-2016-6163 | suse_vex | SUSE CVE CVE-2016-6163 | known not affected: 267 recommended: 10 | 2026-07-26T00:57:35+00:00 | Vulnerability · Source |
| CVE-2016-6224 | suse_vex | SUSE CVE CVE-2016-6224 | known not affected: 14 recommended: 29 | 2026-07-26T00:57:24+00:00 | Vulnerability · Source |
| CVE-2016-6258 | suse_vex | SUSE CVE CVE-2016-6258 | known affected: 320 known not affected: 18 recommended: 549 | 2026-07-26T00:57:19+00:00 | Vulnerability · Source |
| CVE-2016-6305 | suse_vex | SUSE CVE CVE-2016-6305 | known not affected: 65 | 2026-07-26T00:57:04+00:00 | Vulnerability · Source |
| CVE-2016-6309 | suse_vex | SUSE CVE CVE-2016-6309 | known not affected: 72 | 2026-07-26T00:56:58+00:00 | Vulnerability · Source |
| CVE-2016-6321 | suse_vex | SUSE CVE CVE-2016-6321 | known affected: 322 known not affected: 55 recommended: 313 | 2026-07-26T00:56:56+00:00 | Vulnerability · Source |
| CVE-2016-6508 | suse_vex | SUSE CVE CVE-2016-6508 | known affected: 75 recommended: 533 | 2026-07-26T00:56:50+00:00 | Vulnerability · Source |
| CVE-2016-6823 | suse_vex | SUSE CVE CVE-2016-6823 | known affected: 61 recommended: 218 | 2026-07-26T00:56:42+00:00 | Vulnerability · Source |
| CVE-2016-7091 | suse_vex | SUSE CVE CVE-2016-7091 | known not affected: 24 recommended: 2 | 2026-07-26T00:56:22+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-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-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 |