VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
299385 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5016 | suse_vex | SUSE CVE CVE-2017-5016 | recommended: 10 | 2026-05-13T16:11:13+00:00 | Vulnerability · Source |
| CVE-2017-5017 | suse_vex | SUSE CVE CVE-2017-5017 | recommended: 10 | 2026-05-13T16:11:12+00:00 | Vulnerability · Source |
| CVE-2017-5018 | suse_vex | SUSE CVE CVE-2017-5018 | recommended: 10 | 2026-05-13T16:11:11+00:00 | Vulnerability · Source |
| CVE-2017-5019 | suse_vex | SUSE CVE CVE-2017-5019 | recommended: 10 | 2026-05-13T16:11:10+00:00 | Vulnerability · Source |
| CVE-2017-5020 | suse_vex | SUSE CVE CVE-2017-5020 | recommended: 10 | 2026-05-13T16:11:09+00:00 | Vulnerability · Source |
| CVE-2017-5021 | suse_vex | SUSE CVE CVE-2017-5021 | recommended: 10 | 2026-05-13T16:11:07+00:00 | Vulnerability · Source |
| CVE-2017-5022 | suse_vex | SUSE CVE CVE-2017-5022 | recommended: 10 | 2026-05-13T16:11:06+00:00 | Vulnerability · Source |
| CVE-2017-5023 | suse_vex | SUSE CVE CVE-2017-5023 | recommended: 10 | 2026-05-13T16:11:05+00:00 | Vulnerability · Source |
| CVE-2017-5024 | suse_vex | SUSE CVE CVE-2017-5024 | recommended: 29 | 2026-05-13T16:11:04+00:00 | Vulnerability · Source |
| CVE-2017-5025 | suse_vex | SUSE CVE CVE-2017-5025 | recommended: 29 | 2026-05-13T16:11:03+00:00 | Vulnerability · Source |
| CVE-2017-5026 | suse_vex | SUSE CVE CVE-2017-5026 | recommended: 10 | 2026-05-13T16:11:01+00:00 | Vulnerability · Source |
| CVE-2017-5047 | suse_vex | SUSE CVE CVE-2017-5047 | No product status | 2026-05-13T16:10:59+00:00 | Vulnerability · Source |
| CVE-2017-5048 | suse_vex | SUSE CVE CVE-2017-5048 | No product status | 2026-05-13T16:10:57+00:00 | Vulnerability · Source |
| CVE-2017-5049 | suse_vex | SUSE CVE CVE-2017-5049 | No product status | 2026-05-13T16:10:56+00:00 | Vulnerability · Source |
| CVE-2017-5050 | suse_vex | SUSE CVE CVE-2017-5050 | No product status | 2026-05-13T16:10:55+00:00 | Vulnerability · Source |
| CVE-2017-5051 | suse_vex | SUSE CVE CVE-2017-5051 | No product status | 2026-05-13T16:10:54+00:00 | Vulnerability · Source |
| CVE-2017-5112 | suse_vex | SUSE CVE CVE-2017-5112 | recommended: 10 | 2026-05-13T16:10:53+00:00 | Vulnerability · Source |
| CVE-2017-5115 | suse_vex | SUSE CVE CVE-2017-5115 | recommended: 10 | 2026-05-13T16:10:51+00:00 | Vulnerability · Source |
| CVE-2017-5193 | suse_vex | SUSE CVE CVE-2017-5193 | recommended: 4 | 2026-05-13T16:10:49+00:00 | Vulnerability · Source |
| CVE-2017-5194 | suse_vex | SUSE CVE CVE-2017-5194 | recommended: 4 | 2026-05-13T16:10:47+00:00 | Vulnerability · Source |
| CVE-2017-5223 | suse_vex | SUSE CVE CVE-2017-5223 | No product status | 2026-05-13T16:10:41+00:00 | Vulnerability · Source |
| CVE-2017-5361 | suse_vex | SUSE CVE CVE-2017-5361 | No product status | 2026-05-13T16:10:37+00:00 | Vulnerability · Source |
| CVE-2017-5537 | suse_vex | SUSE CVE CVE-2017-5537 | No product status | 2026-05-13T16:10:26+00:00 | Vulnerability · Source |
| CVE-2017-5545 | suse_vex | SUSE CVE CVE-2017-5545 | known affected: 27 recommended: 351 | 2026-05-13T16:10:25+00:00 | Vulnerability · Source |
| CVE-2017-5630 | suse_vex | SUSE CVE CVE-2017-5630 | No product status | 2026-05-13T16:10:17+00:00 | Vulnerability · Source |
| CVE-2017-5923 | suse_vex | SUSE CVE CVE-2017-5923 | No product status | 2026-05-13T16:10:05+00:00 | Vulnerability · Source |
| CVE-2017-5924 | suse_vex | SUSE CVE CVE-2017-5924 | No product status | 2026-05-13T16:10:04+00:00 | Vulnerability · Source |
| CVE-2017-5930 | suse_vex | SUSE CVE CVE-2017-5930 | recommended: 2 | 2026-05-13T16:10:03+00:00 | Vulnerability · Source |
| 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 |