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-5985 | suse_vex | SUSE CVE CVE-2017-5985 | known not affected: 11 recommended: 5 | 2026-05-13T16:09:52+00:00 | Vulnerability · Source |
| CVE-2017-5992 | suse_vex | SUSE CVE CVE-2017-5992 | recommended: 6 | 2026-05-13T16:09:51+00:00 | Vulnerability · Source |
| CVE-2017-6209 | suse_vex | SUSE CVE CVE-2017-6209 | recommended: 26 | 2026-05-13T16:09:43+00:00 | Vulnerability · Source |
| CVE-2017-6307 | suse_vex | SUSE CVE CVE-2017-6307 | No product status | 2026-05-13T16:09:40+00:00 | Vulnerability · Source |
| CVE-2017-6308 | suse_vex | SUSE CVE CVE-2017-6308 | No product status | 2026-05-13T16:09:39+00:00 | Vulnerability · Source |
| CVE-2017-6309 | suse_vex | SUSE CVE CVE-2017-6309 | No product status | 2026-05-13T16:09:38+00:00 | Vulnerability · Source |
| CVE-2017-6310 | suse_vex | SUSE CVE CVE-2017-6310 | No product status | 2026-05-13T16:09:37+00:00 | Vulnerability · Source |
| CVE-2017-6384 | suse_vex | SUSE CVE CVE-2017-6384 | recommended: 3 | 2026-05-13T16:09:25+00:00 | Vulnerability · Source |
| CVE-2017-6421 | suse_vex | SUSE CVE CVE-2017-6421 | No product status | 2026-05-13T16:09:22+00:00 | Vulnerability · Source |
| CVE-2017-6504 | suse_vex | SUSE CVE CVE-2017-6504 | No product status | 2026-05-13T16:09:15+00:00 | Vulnerability · Source |
| CVE-2017-6542 | suse_vex | SUSE CVE CVE-2017-6542 | recommended: 1 | 2026-05-13T16:09:14+00:00 | Vulnerability · Source |
| CVE-2017-6844 | suse_vex | SUSE CVE CVE-2017-6844 | known affected: 6 recommended: 28 | 2026-05-13T16:09:10+00:00 | Vulnerability · Source |
| CVE-2017-6889 | suse_vex | SUSE CVE CVE-2017-6889 | recommended: 36 | 2026-05-13T16:09:08+00:00 | Vulnerability · Source |
| CVE-2017-7091 | suse_vex | SUSE CVE CVE-2017-7091 | known not affected: 69 recommended: 894 | 2026-05-13T16:08:24+00:00 | Vulnerability · Source |
| CVE-2017-7191 | suse_vex | SUSE CVE CVE-2017-7191 | No product status | 2026-05-13T16:08:00+00:00 | Vulnerability · Source |
| CVE-2017-7208 | suse_vex | SUSE CVE CVE-2017-7208 | No product status | 2026-05-13T16:07:59+00:00 | Vulnerability · Source |
| CVE-2017-7214 | suse_vex | SUSE CVE CVE-2017-7214 | known not affected: 16 recommended: 64 | 2026-05-13T16:07:58+00:00 | Vulnerability · Source |
| CVE-2017-7263 | suse_vex | SUSE CVE CVE-2017-7263 | No product status | 2026-05-13T16:07:50+00:00 | Vulnerability · Source |
| CVE-2017-7358 | suse_vex | SUSE CVE CVE-2017-7358 | No product status | 2026-05-13T16:07:47+00:00 | Vulnerability · Source |
| CVE-2017-7499 | suse_vex | SUSE CVE CVE-2017-7499 | No product status | 2026-05-13T16:07:40+00:00 | Vulnerability · Source |
| CVE-2017-7551 | suse_vex | SUSE CVE CVE-2017-7551 | No product status | 2026-05-13T16:07:26+00:00 | Vulnerability · Source |
| CVE-2017-7572 | suse_vex | SUSE CVE CVE-2017-7572 | recommended: 3 | 2026-05-13T16:07:23+00:00 | Vulnerability · Source |
| CVE-2017-7617 | suse_vex | SUSE CVE CVE-2017-7617 | No product status | 2026-05-13T16:07:00+00:00 | Vulnerability · Source |
| CVE-2017-7619 | suse_vex | SUSE CVE CVE-2017-7619 | known not affected: 111 | 2026-05-13T16:06:57+00:00 | Vulnerability · Source |
| CVE-2017-7622 | suse_vex | SUSE CVE CVE-2017-7622 | No product status | 2026-05-13T16:06:56+00:00 | Vulnerability · Source |
| CVE-2017-7672 | suse_vex | SUSE CVE CVE-2017-7672 | known not affected: 2 | 2026-05-13T16:06:53+00:00 | Vulnerability · Source |
| CVE-2017-7692 | suse_vex | SUSE CVE CVE-2017-7692 | No product status | 2026-05-13T16:06:52+00:00 | Vulnerability · Source |
| CVE-2017-7698 | suse_vex | SUSE CVE CVE-2017-7698 | No product status | 2026-05-13T16:06:51+00:00 | Vulnerability · Source |
| CVE-2017-7875 | suse_vex | SUSE CVE CVE-2017-7875 | recommended: 1 | 2026-05-13T16:06:24+00:00 | Vulnerability · Source |
| CVE-2017-7882 | suse_vex | SUSE CVE CVE-2017-7882 | recommended: 4418 | 2026-05-13T16:06:22+00:00 | Vulnerability · Source |
| CVE-2017-7885 | suse_vex | SUSE CVE CVE-2017-7885 | No product status | 2026-05-13T16:06:21+00:00 | Vulnerability · Source |
| CVE-2017-7975 | suse_vex | SUSE CVE CVE-2017-7975 | No product status | 2026-05-13T16:06:15+00:00 | Vulnerability · Source |
| CVE-2017-7976 | suse_vex | SUSE CVE CVE-2017-7976 | recommended: 2 | 2026-05-13T16:06:13+00:00 | Vulnerability · Source |
| CVE-2017-7995 | suse_vex | SUSE CVE CVE-2017-7995 | known not affected: 53 recommended: 52 | 2026-05-13T16:06:12+00:00 | Vulnerability · Source |
| CVE-2017-8062 | suse_vex | SUSE CVE CVE-2017-8062 | known not affected: 20 | 2026-05-13T16:06:11+00:00 | Vulnerability · Source |
| CVE-2017-8073 | suse_vex | SUSE CVE CVE-2017-8073 | recommended: 9 | 2026-05-13T16:06:02+00:00 | Vulnerability · Source |
| CVE-2017-8108 | suse_vex | SUSE CVE CVE-2017-8108 | recommended: 1 | 2026-05-13T16:06:01+00:00 | Vulnerability · Source |
| CVE-2017-8109 | suse_vex | SUSE CVE CVE-2017-8109 | recommended: 147 | 2026-05-13T16:06:00+00:00 | Vulnerability · Source |
| CVE-2017-8310 | suse_vex | SUSE CVE CVE-2017-8310 | No product status | 2026-05-13T16:05:56+00:00 | Vulnerability · Source |
| CVE-2017-8311 | suse_vex | SUSE CVE CVE-2017-8311 | No product status | 2026-05-13T16:05:55+00:00 | Vulnerability · Source |
| CVE-2017-8313 | suse_vex | SUSE CVE CVE-2017-8313 | No product status | 2026-05-13T16:05:54+00:00 | Vulnerability · Source |
| CVE-2017-8342 | suse_vex | SUSE CVE CVE-2017-8342 | No product status | 2026-05-13T16:05:53+00:00 | Vulnerability · Source |
| CVE-2017-8359 | suse_vex | SUSE CVE CVE-2017-8359 | No product status | 2026-05-13T16:05:50+00:00 | Vulnerability · Source |
| CVE-2017-8364 | suse_vex | SUSE CVE CVE-2017-8364 | recommended: 1 | 2026-05-13T16:05:49+00:00 | Vulnerability · Source |
| CVE-2017-8399 | suse_vex | SUSE CVE CVE-2017-8399 | No product status | 2026-05-13T16:05:44+00:00 | Vulnerability · Source |
| CVE-2017-8400 | suse_vex | SUSE CVE CVE-2017-8400 | No product status | 2026-05-13T16:05:43+00:00 | Vulnerability · Source |
| CVE-2017-8418 | suse_vex | SUSE CVE CVE-2017-8418 | No product status | 2026-05-13T16:05:41+00:00 | Vulnerability · Source |
| CVE-2017-8419 | suse_vex | SUSE CVE CVE-2017-8419 | No product status | 2026-05-13T16:05:40+00:00 | Vulnerability · Source |
| CVE-2017-8438 | suse_vex | SUSE CVE CVE-2017-8438 | No product status | 2026-05-13T16:05:39+00:00 | Vulnerability · Source |
| CVE-2017-8443 | suse_vex | SUSE CVE CVE-2017-8443 | known not affected: 1 | 2026-05-13T16:05:38+00:00 | Vulnerability · Source |