VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
299407 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-11366 | suse_vex | SUSE CVE CVE-2017-11366 | No product status | 2026-05-13T16:01:49+00:00 | Vulnerability · Source |
| CVE-2017-11546 | suse_vex | SUSE CVE CVE-2017-11546 | recommended: 1 | 2026-05-13T16:01:21+00:00 | Vulnerability · Source |
| CVE-2017-11547 | suse_vex | SUSE CVE CVE-2017-11547 | recommended: 1 | 2026-05-13T16:01:19+00:00 | Vulnerability · Source |
| CVE-2017-11549 | suse_vex | SUSE CVE CVE-2017-11549 | No product status | 2026-05-13T16:01:17+00:00 | Vulnerability · Source |
| CVE-2017-11554 | suse_vex | SUSE CVE CVE-2017-11554 | No product status | 2026-05-13T16:01:12+00:00 | Vulnerability · Source |
| CVE-2017-11555 | suse_vex | SUSE CVE CVE-2017-11555 | No product status | 2026-05-13T16:01:11+00:00 | Vulnerability · Source |
| CVE-2017-11556 | suse_vex | SUSE CVE CVE-2017-11556 | No product status | 2026-05-13T16:01:09+00:00 | Vulnerability · Source |
| CVE-2017-11608 | suse_vex | SUSE CVE CVE-2017-11608 | No product status | 2026-05-13T16:01:00+00:00 | Vulnerability · Source |
| CVE-2017-11610 | suse_vex | SUSE CVE CVE-2017-11610 | No product status | 2026-05-13T16:00:58+00:00 | Vulnerability · Source |
| CVE-2017-11684 | suse_vex | SUSE CVE CVE-2017-11684 | No product status | 2026-05-13T16:00:48+00:00 | Vulnerability · Source |
| CVE-2017-11719 | suse_vex | SUSE CVE CVE-2017-11719 | No product status | 2026-05-13T16:00:45+00:00 | Vulnerability · Source |
| CVE-2017-11720 | suse_vex | SUSE CVE CVE-2017-11720 | known not affected: 15 recommended: 5 | 2026-05-13T16:00:44+00:00 | Vulnerability · Source |
| CVE-2017-11754 | suse_vex | SUSE CVE CVE-2017-11754 | known affected: 75 known not affected: 91 | 2026-05-13T16:00:34+00:00 | Vulnerability · Source |
| CVE-2017-12065 | suse_vex | SUSE CVE CVE-2017-12065 | recommended: 3 | 2026-05-13T16:00:32+00:00 | Vulnerability · Source |
| CVE-2017-12067 | suse_vex | SUSE CVE CVE-2017-12067 | known not affected: 38 recommended: 43 | 2026-05-13T16:00:31+00:00 | Vulnerability · Source |
| CVE-2017-12425 | suse_vex | SUSE CVE CVE-2017-12425 | No product status | 2026-05-13T16:00:12+00:00 | Vulnerability · Source |
| CVE-2017-12440 | suse_vex | SUSE CVE CVE-2017-12440 | recommended: 8 | 2026-05-13T16:00:01+00:00 | Vulnerability · Source |
| CVE-2017-12458 | suse_vex | SUSE CVE CVE-2017-12458 | No product status | 2026-05-13T16:00:00+00:00 | Vulnerability · Source |
| CVE-2017-12481 | suse_vex | SUSE CVE CVE-2017-12481 | recommended: 5 | 2026-05-13T15:59:59+00:00 | Vulnerability · Source |
| CVE-2017-12482 | suse_vex | SUSE CVE CVE-2017-12482 | recommended: 5 | 2026-05-13T15:59:58+00:00 | Vulnerability · Source |
| CVE-2017-12600 | suse_vex | SUSE CVE CVE-2017-12600 | No product status | 2026-05-13T15:59:52+00:00 | Vulnerability · Source |
| CVE-2017-12602 | suse_vex | SUSE CVE CVE-2017-12602 | No product status | 2026-05-13T15:59:51+00:00 | Vulnerability · Source |
| CVE-2017-12611 | suse_vex | SUSE CVE CVE-2017-12611 | known not affected: 14 | 2026-05-13T15:59:50+00:00 | Vulnerability · Source |
| CVE-2017-12635 | suse_vex | SUSE CVE CVE-2017-12635 | No product status | 2026-05-13T15:59:45+00:00 | Vulnerability · Source |
| CVE-2017-12636 | suse_vex | SUSE CVE CVE-2017-12636 | recommended: 2 | 2026-05-13T15:59:44+00:00 | Vulnerability · Source |
| CVE-2017-12875 | suse_vex | SUSE CVE CVE-2017-12875 | known affected: 5 known not affected: 110 | 2026-05-13T15:59:29+00:00 | Vulnerability · Source |
| CVE-2017-12904 | suse_vex | SUSE CVE CVE-2017-12904 | No product status | 2026-05-13T15:59:26+00:00 | Vulnerability · Source |
| CVE-2017-12927 | suse_vex | SUSE CVE CVE-2017-12927 | recommended: 3 | 2026-05-13T15:59:25+00:00 | Vulnerability · Source |
| CVE-2017-12958 | suse_vex | SUSE CVE CVE-2017-12958 | recommended: 5 | 2026-05-13T15:59:17+00:00 | Vulnerability · Source |
| CVE-2017-12959 | suse_vex | SUSE CVE CVE-2017-12959 | recommended: 5 | 2026-05-13T15:59:16+00:00 | Vulnerability · Source |
| CVE-2017-12960 | suse_vex | SUSE CVE CVE-2017-12960 | No product status | 2026-05-13T15:59:15+00:00 | Vulnerability · Source |
| CVE-2017-12961 | suse_vex | SUSE CVE CVE-2017-12961 | recommended: 5 | 2026-05-13T15:59:13+00:00 | Vulnerability · Source |
| CVE-2017-12962 | suse_vex | SUSE CVE CVE-2017-12962 | No product status | 2026-05-13T15:59:12+00:00 | Vulnerability · Source |
| CVE-2017-12963 | suse_vex | SUSE CVE CVE-2017-12963 | No product status | 2026-05-13T15:59:11+00:00 | Vulnerability · Source |
| CVE-2017-12964 | suse_vex | SUSE CVE CVE-2017-12964 | No product status | 2026-05-13T15:59:09+00:00 | Vulnerability · Source |
| CVE-2017-12976 | suse_vex | SUSE CVE CVE-2017-12976 | No product status | 2026-05-13T15:59:08+00:00 | Vulnerability · Source |
| CVE-2017-13704 | suse_vex | SUSE CVE CVE-2017-13704 | known affected: 1 known not affected: 24 | 2026-05-13T15:58:54+00:00 | Vulnerability · Source |
| CVE-2017-13709 | suse_vex | SUSE CVE CVE-2017-13709 | No product status | 2026-05-13T15:58:53+00:00 | Vulnerability · Source |
| CVE-2017-13712 | suse_vex | SUSE CVE CVE-2017-13712 | known not affected: 15 recommended: 5 | 2026-05-13T15:58:52+00:00 | Vulnerability · Source |
| CVE-2017-13797 | suse_vex | SUSE CVE CVE-2017-13797 | known affected: 8 known not affected: 45 | 2026-05-13T15:58:35+00:00 | Vulnerability · Source |
| CVE-2017-14226 | suse_vex | SUSE CVE CVE-2017-14226 | known not affected: 12 recommended: 97 | 2026-05-13T15:58:14+00:00 | Vulnerability · Source |
| CVE-2017-14339 | suse_vex | SUSE CVE CVE-2017-14339 | No product status | 2026-05-13T15:58:03+00:00 | Vulnerability · Source |
| CVE-2017-14409 | suse_vex | SUSE CVE CVE-2017-14409 | No product status | 2026-05-13T15:58:01+00:00 | Vulnerability · Source |
| CVE-2017-14411 | suse_vex | SUSE CVE CVE-2017-14411 | No product status | 2026-05-13T15:58:00+00:00 | Vulnerability · Source |
| CVE-2017-14412 | suse_vex | SUSE CVE CVE-2017-14412 | No product status | 2026-05-13T15:57:59+00:00 | Vulnerability · Source |
| CVE-2017-14500 | suse_vex | SUSE CVE CVE-2017-14500 | No product status | 2026-05-13T15:57:51+00:00 | Vulnerability · Source |
| CVE-2017-14532 | suse_vex | SUSE CVE CVE-2017-14532 | known affected: 5 known not affected: 124 | 2026-05-13T15:57:47+00:00 | Vulnerability · Source |
| CVE-2017-14635 | suse_vex | SUSE CVE CVE-2017-14635 | No product status | 2026-05-13T15:57:37+00:00 | Vulnerability · Source |
| CVE-2017-14685 | suse_vex | SUSE CVE CVE-2017-14685 | No product status | 2026-05-13T15:57:33+00:00 | Vulnerability · Source |
| CVE-2017-14686 | suse_vex | SUSE CVE CVE-2017-14686 | No product status | 2026-05-13T15:57:32+00:00 | Vulnerability · Source |