VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293833 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-0601 | suse_vex | SUSE CVE CVE-2016-0601 | known affected: 1 known not affected: 176 | 2026-07-29T00:08:52+00:00 | Vulnerability · Source |
| CVE-2016-0666 | suse_vex | SUSE CVE CVE-2016-0666 | known not affected: 121 recommended: 293 | 2026-07-29T00:08:49+00:00 | Vulnerability · Source |
| CVE-2016-1585 | suse_vex | SUSE CVE CVE-2016-1585 | known not affected: 270 recommended: 157 | 2026-07-29T00:08:39+00:00 | Vulnerability · Source |
| CVE-2016-1602 | suse_vex | SUSE CVE CVE-2016-1602 | known not affected: 51 recommended: 24 | 2026-07-29T00:08:38+00:00 | Vulnerability · Source |
| CVE-2016-1944 | suse_vex | SUSE CVE CVE-2016-1944 | known affected: 21 recommended: 250 | 2026-07-29T00:08:33+00:00 | Vulnerability · Source |
| CVE-2016-1951 | suse_vex | SUSE CVE CVE-2016-1951 | known not affected: 40 | 2026-07-29T00:08:31+00:00 | Vulnerability · Source |
| CVE-2016-2185 | suse_vex | SUSE CVE CVE-2016-2185 | known affected: 21 known not affected: 210 recommended: 510 | 2026-07-29T00:08:19+00:00 | Vulnerability · Source |
| CVE-2016-2517 | suse_vex | SUSE CVE CVE-2016-2517 | known affected: 30 recommended: 109 | 2026-07-29T00:08:17+00:00 | Vulnerability · Source |
| CVE-2016-2571 | suse_vex | SUSE CVE CVE-2016-2571 | known affected: 397 known not affected: 33 recommended: 50 | 2026-07-29T00:08:12+00:00 | Vulnerability · Source |
| CVE-2016-2814 | suse_vex | SUSE CVE CVE-2016-2814 | known affected: 2 known not affected: 3 recommended: 417 | 2026-07-29T00:08:08+00:00 | Vulnerability · Source |
| CVE-2016-2851 | suse_vex | SUSE CVE CVE-2016-2851 | known affected: 31 known not affected: 31 recommended: 97 | 2026-07-29T00:08:05+00:00 | Vulnerability · Source |
| CVE-2016-4037 | suse_vex | SUSE CVE CVE-2016-4037 | known affected: 1 known not affected: 33 recommended: 169 | 2026-07-29T00:07:54+00:00 | Vulnerability · Source |
| CVE-2016-4492 | suse_vex | SUSE CVE CVE-2016-4492 | known affected: 2 known not affected: 416 | 2026-07-29T00:07:52+00:00 | Vulnerability · Source |
| CVE-2016-4553 | suse_vex | SUSE CVE CVE-2016-4553 | known affected: 396 known not affected: 31 recommended: 49 | 2026-07-29T00:07:50+00:00 | Vulnerability · Source |
| CVE-2016-5271 | suse_vex | SUSE CVE CVE-2016-5271 | known affected: 5 recommended: 250 | 2026-07-29T00:07:39+00:00 | Vulnerability · Source |
| CVE-2016-5546 | suse_vex | SUSE CVE CVE-2016-5546 | known affected: 103 known not affected: 150 recommended: 354 | 2026-07-29T00:07:31+00:00 | Vulnerability · Source |
| CVE-2016-5863 | suse_vex | SUSE CVE CVE-2016-5863 | known not affected: 78 | 2026-07-29T00:07:30+00:00 | Vulnerability · Source |
| CVE-2016-6213 | suse_vex | SUSE CVE CVE-2016-6213 | known not affected: 326 recommended: 12 | 2026-07-29T00:07:27+00:00 | Vulnerability · Source |
| CVE-2016-6787 | suse_vex | SUSE CVE CVE-2016-6787 | known not affected: 529 | 2026-07-29T00:07:20+00:00 | Vulnerability · Source |
| CVE-2016-6906 | suse_vex | SUSE CVE CVE-2016-6906 | known affected: 12 known not affected: 1226 recommended: 56 | 2026-07-29T00:07:17+00:00 | Vulnerability · Source |
| CVE-2016-7039 | suse_vex | SUSE CVE CVE-2016-7039 | known affected: 27 known not affected: 409 recommended: 215 | 2026-07-29T00:07:16+00:00 | Vulnerability · Source |
| CVE-2016-7531 | suse_vex | SUSE CVE CVE-2016-7531 | known affected: 95 recommended: 182 | 2026-07-29T00:07:10+00:00 | Vulnerability · Source |
| CVE-2016-7533 | suse_vex | SUSE CVE CVE-2016-7533 | known affected: 95 recommended: 182 | 2026-07-29T00:07:08+00:00 | Vulnerability · Source |
| CVE-2016-7540 | suse_vex | SUSE CVE CVE-2016-7540 | known affected: 94 known not affected: 51 recommended: 132 | 2026-07-29T00:07:07+00:00 | Vulnerability · Source |
| CVE-2016-7649 | suse_vex | SUSE CVE CVE-2016-7649 | known not affected: 87 | 2026-07-29T00:07:04+00:00 | Vulnerability · Source |
| CVE-2016-7795 | suse_vex | SUSE CVE CVE-2016-7795 | known not affected: 196 recommended: 154 | 2026-07-29T00:07:02+00:00 | Vulnerability · Source |
| CVE-2016-7949 | suse_vex | SUSE CVE CVE-2016-7949 | known affected: 36 recommended: 270 | 2026-07-29T00:06:56+00:00 | Vulnerability · Source |
| CVE-2016-7953 | suse_vex | SUSE CVE CVE-2016-7953 | known affected: 24 recommended: 261 | 2026-07-29T00:06:55+00:00 | Vulnerability · Source |
| CVE-2016-8283 | suse_vex | SUSE CVE CVE-2016-8283 | known affected: 35 known not affected: 163 recommended: 630 | 2026-07-29T00:06:53+00:00 | Vulnerability · Source |
| CVE-2016-8630 | suse_vex | SUSE CVE CVE-2016-8630 | known not affected: 449 recommended: 12 | 2026-07-29T00:06:51+00:00 | Vulnerability · Source |
| CVE-2016-8660 | suse_vex | SUSE CVE CVE-2016-8660 | known not affected: 22 | 2026-07-29T00:06:50+00:00 | Vulnerability · Source |
| CVE-2016-8670 | suse_vex | SUSE CVE CVE-2016-8670 | known affected: 551 recommended: 1346 | 2026-07-29T00:06:48+00:00 | Vulnerability · Source |
| CVE-2016-9536 | suse_vex | SUSE CVE CVE-2016-9536 | known not affected: 28 recommended: 26 | 2026-07-29T00:06:38+00:00 | Vulnerability · Source |
| CVE-2016-9625 | suse_vex | SUSE CVE CVE-2016-9625 | known affected: 1 recommended: 87 | 2026-07-29T00:06:35+00:00 | Vulnerability · Source |
| CVE-2016-9636 | suse_vex | SUSE CVE CVE-2016-9636 | known affected: 32 recommended: 86 | 2026-07-29T00:06:33+00:00 | Vulnerability · Source |
| CVE-2016-9952 | suse_vex | SUSE CVE CVE-2016-9952 | known not affected: 63 | 2026-07-29T00:06:19+00:00 | Vulnerability · Source |
| CVE-2016-10029 | suse_vex | SUSE CVE CVE-2016-10029 | known not affected: 1021 recommended: 66 | 2026-07-29T00:06:16+00:00 | Vulnerability · Source |
| CVE-2016-10046 | suse_vex | SUSE CVE CVE-2016-10046 | known affected: 1 recommended: 204 | 2026-07-29T00:06:15+00:00 | Vulnerability · Source |
| CVE-2016-10050 | suse_vex | SUSE CVE CVE-2016-10050 | recommended: 218 | 2026-07-29T00:06:13+00:00 | Vulnerability · Source |
| CVE-2016-10058 | suse_vex | SUSE CVE CVE-2016-10058 | known affected: 10 known not affected: 113 | 2026-07-29T00:06:12+00:00 | Vulnerability · Source |
| CVE-2016-10164 | suse_vex | SUSE CVE CVE-2016-10164 | recommended: 261 | 2026-07-29T00:06:10+00:00 | Vulnerability · Source |
| CVE-2016-10208 | suse_vex | SUSE CVE CVE-2016-10208 | known affected: 14 known not affected: 392 recommended: 122 | 2026-07-29T00:06:08+00:00 | Vulnerability · Source |
| CVE-2016-10318 | suse_vex | SUSE CVE CVE-2016-10318 | known not affected: 34 | 2026-07-29T00:06:06+00:00 | Vulnerability · Source |
| CVE-2016-10350 | suse_vex | SUSE CVE CVE-2016-10350 | known affected: 24 known not affected: 16 recommended: 25 | 2026-07-29T00:06:05+00:00 | Vulnerability · Source |
| CVE-2017-2538 | suse_vex | SUSE CVE CVE-2017-2538 | known affected: 116 known not affected: 87 recommended: 939 | 2026-07-29T00:05:59+00:00 | Vulnerability · Source |
| CVE-2017-3144 | suse_vex | SUSE CVE CVE-2017-3144 | known affected: 344 known not affected: 95 recommended: 407 | 2026-07-29T00:05:55+00:00 | Vulnerability · Source |
| CVE-2017-3638 | suse_vex | SUSE CVE CVE-2017-3638 | known affected: 1 known not affected: 64 | 2026-07-29T00:05:52+00:00 | Vulnerability · Source |
| CVE-2017-3730 | suse_vex | SUSE CVE CVE-2017-3730 | known not affected: 103 | 2026-07-29T00:05:49+00:00 | Vulnerability · Source |
| CVE-2017-5336 | suse_vex | SUSE CVE CVE-2017-5336 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-29T00:05:43+00:00 | Vulnerability · Source |
| CVE-2017-5500 | suse_vex | SUSE CVE CVE-2017-5500 | known affected: 46 known not affected: 16 | 2026-07-29T00:05:36+00:00 | Vulnerability · Source |