VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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 |
| CVE-2017-5507 | suse_vex | SUSE CVE CVE-2017-5507 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-29T00:05:33+00:00 | Vulnerability · Source |
| CVE-2017-5650 | suse_vex | SUSE CVE CVE-2017-5650 | known not affected: 54 | 2026-07-29T00:05:32+00:00 | Vulnerability · Source |
| CVE-2017-5967 | suse_vex | SUSE CVE CVE-2017-5967 | known not affected: 351 | 2026-07-29T00:05:27+00:00 | Vulnerability · Source |
| CVE-2017-6355 | suse_vex | SUSE CVE CVE-2017-6355 | recommended: 29 | 2026-07-29T00:05:22+00:00 | Vulnerability · Source |
| CVE-2017-6460 | suse_vex | SUSE CVE CVE-2017-6460 | known affected: 31 recommended: 98 | 2026-07-29T00:05:19+00:00 | Vulnerability · Source |
| CVE-2017-6472 | suse_vex | SUSE CVE CVE-2017-6472 | known affected: 73 recommended: 444 | 2026-07-29T00:05:16+00:00 | Vulnerability · Source |
| CVE-2017-6499 | suse_vex | SUSE CVE CVE-2017-6499 | known affected: 10 known not affected: 113 | 2026-07-29T00:05:15+00:00 | Vulnerability · Source |
| CVE-2017-6836 | suse_vex | SUSE CVE CVE-2017-6836 | known affected: 45 recommended: 196 | 2026-07-29T00:05:12+00:00 | Vulnerability · Source |
| CVE-2017-6891 | suse_vex | SUSE CVE CVE-2017-6891 | known not affected: 321 recommended: 89 | 2026-07-29T00:05:10+00:00 | Vulnerability · Source |
| CVE-2017-7286 | suse_vex | SUSE CVE CVE-2017-7286 | known not affected: 64 | 2026-07-29T00:05:02+00:00 | Vulnerability · Source |
| CVE-2017-7794 | suse_vex | SUSE CVE CVE-2017-7794 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:55+00:00 | Vulnerability · Source |
| CVE-2017-7797 | suse_vex | SUSE CVE CVE-2017-7797 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:54+00:00 | Vulnerability · Source |
| CVE-2017-7837 | suse_vex | SUSE CVE CVE-2017-7837 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-29T00:04:53+00:00 | Vulnerability · Source |
| CVE-2017-7895 | suse_vex | SUSE CVE CVE-2017-7895 | known not affected: 36 recommended: 12 | 2026-07-29T00:04:51+00:00 | Vulnerability · Source |
| CVE-2017-7942 | suse_vex | SUSE CVE CVE-2017-7942 | known not affected: 25 recommended: 170 | 2026-07-29T00:04:50+00:00 | Vulnerability · Source |
| CVE-2017-8065 | suse_vex | SUSE CVE CVE-2017-8065 | known not affected: 34 | 2026-07-29T00:04:48+00:00 | Vulnerability · Source |
| CVE-2017-8284 | suse_vex | SUSE CVE CVE-2017-8284 | known not affected: 793 | 2026-07-29T00:04:46+00:00 | Vulnerability · Source |
| CVE-2017-8354 | suse_vex | SUSE CVE CVE-2017-8354 | known not affected: 14 recommended: 170 | 2026-07-29T00:04:44+00:00 | Vulnerability · Source |
| CVE-2017-8813 | suse_vex | SUSE CVE CVE-2017-8813 | known affected: 26 known not affected: 261 | 2026-07-29T00:04:41+00:00 | Vulnerability · Source |
| CVE-2017-9109 | suse_vex | SUSE CVE CVE-2017-9109 | known affected: 18 recommended: 44 | 2026-07-29T00:04:38+00:00 | Vulnerability · Source |
| CVE-2017-9117 | suse_vex | SUSE CVE CVE-2017-9117 | known not affected: 135 recommended: 22 | 2026-07-29T00:04:35+00:00 | Vulnerability · Source |
| CVE-2017-9141 | suse_vex | SUSE CVE CVE-2017-9141 | known not affected: 14 recommended: 170 | 2026-07-29T00:04:34+00:00 | Vulnerability · Source |
| CVE-2017-9263 | suse_vex | SUSE CVE CVE-2017-9263 | known affected: 4 known not affected: 27 recommended: 21 | 2026-07-29T00:04:32+00:00 | Vulnerability · Source |
| CVE-2017-10105 | suse_vex | SUSE CVE CVE-2017-10105 | known affected: 15 known not affected: 109 recommended: 667 | 2026-07-29T00:04:24+00:00 | Vulnerability · Source |
| CVE-2017-10912 | suse_vex | SUSE CVE CVE-2017-10912 | known not affected: 6 recommended: 43 | 2026-07-29T00:04:15+00:00 | Vulnerability · Source |
| CVE-2017-10986 | suse_vex | SUSE CVE CVE-2017-10986 | known affected: 24 known not affected: 111 recommended: 577 | 2026-07-29T00:04:14+00:00 | Vulnerability · Source |
| CVE-2017-11640 | suse_vex | SUSE CVE CVE-2017-11640 | known affected: 94 recommended: 186 | 2026-07-29T00:04:06+00:00 | Vulnerability · Source |
| CVE-2017-12587 | suse_vex | SUSE CVE CVE-2017-12587 | known affected: 94 recommended: 186 | 2026-07-29T00:03:54+00:00 | Vulnerability · Source |
| CVE-2017-12668 | suse_vex | SUSE CVE CVE-2017-12668 | known affected: 95 known not affected: 21 recommended: 186 | 2026-07-29T00:03:53+00:00 | Vulnerability · Source |
| CVE-2017-12671 | suse_vex | SUSE CVE CVE-2017-12671 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-29T00:03:51+00:00 | Vulnerability · Source |