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-17383 | suse_vex | SUSE CVE CVE-2017-17383 | No product status | 2026-05-13T15:55:16+00:00 | Vulnerability · Source |
| CVE-2017-17439 | suse_vex | SUSE CVE CVE-2017-17439 | recommended: 2 | 2026-05-13T15:55:13+00:00 | Vulnerability · Source |
| CVE-2017-17459 | suse_vex | SUSE CVE CVE-2017-17459 | recommended: 1 | 2026-05-13T15:55:11+00:00 | Vulnerability · Source |
| CVE-2017-17476 | suse_vex | SUSE CVE CVE-2017-17476 | No product status | 2026-05-13T15:55:09+00:00 | Vulnerability · Source |
| CVE-2017-17506 | suse_vex | SUSE CVE CVE-2017-17506 | recommended: 1197 | 2026-05-13T15:55:06+00:00 | Vulnerability · Source |
| CVE-2017-17513 | suse_vex | SUSE CVE CVE-2017-17513 | No product status | 2026-05-13T15:55:05+00:00 | Vulnerability · Source |
| CVE-2017-17516 | suse_vex | SUSE CVE CVE-2017-17516 | No product status | 2026-05-13T15:55:04+00:00 | Vulnerability · Source |
| CVE-2017-17522 | suse_vex | SUSE CVE CVE-2017-17522 | No product status | 2026-05-13T15:55:03+00:00 | Vulnerability · Source |
| CVE-2017-17523 | suse_vex | SUSE CVE CVE-2017-17523 | No product status | 2026-05-13T15:55:01+00:00 | Vulnerability · Source |
| CVE-2017-17524 | suse_vex | SUSE CVE CVE-2017-17524 | No product status | 2026-05-13T15:55:00+00:00 | Vulnerability · Source |
| CVE-2017-17528 | suse_vex | SUSE CVE CVE-2017-17528 | recommended: 2 | 2026-05-13T15:54:59+00:00 | Vulnerability · Source |
| CVE-2017-17529 | suse_vex | SUSE CVE CVE-2017-17529 | No product status | 2026-05-13T15:54:58+00:00 | Vulnerability · Source |
| CVE-2017-17531 | suse_vex | SUSE CVE CVE-2017-17531 | recommended: 1 | 2026-05-13T15:54:57+00:00 | Vulnerability · Source |
| CVE-2017-17554 | suse_vex | SUSE CVE CVE-2017-17554 | recommended: 10 | 2026-05-13T15:54:56+00:00 | Vulnerability · Source |
| CVE-2017-17664 | suse_vex | SUSE CVE CVE-2017-17664 | No product status | 2026-05-13T15:54:54+00:00 | Vulnerability · Source |
| CVE-2017-17670 | suse_vex | SUSE CVE CVE-2017-17670 | No product status | 2026-05-13T15:54:52+00:00 | Vulnerability · Source |
| CVE-2017-17782 | suse_vex | SUSE CVE CVE-2017-17782 | known affected: 3 recommended: 14 | 2026-05-13T15:54:49+00:00 | Vulnerability · Source |
| CVE-2017-17783 | suse_vex | SUSE CVE CVE-2017-17783 | known not affected: 14 | 2026-05-13T15:54:48+00:00 | Vulnerability · Source |
| CVE-2017-17784 | suse_vex | SUSE CVE CVE-2017-17784 | known not affected: 24 recommended: 53 | 2026-05-13T15:54:47+00:00 | Vulnerability · Source |
| CVE-2017-17785 | suse_vex | SUSE CVE CVE-2017-17785 | known not affected: 24 recommended: 79 | 2026-05-13T15:54:45+00:00 | Vulnerability · Source |
| CVE-2017-17786 | suse_vex | SUSE CVE CVE-2017-17786 | known not affected: 24 recommended: 79 | 2026-05-13T15:54:44+00:00 | Vulnerability · Source |
| CVE-2017-17788 | suse_vex | SUSE CVE CVE-2017-17788 | recommended: 46 | 2026-05-13T15:54:43+00:00 | Vulnerability · Source |
| CVE-2017-17789 | suse_vex | SUSE CVE CVE-2017-17789 | known not affected: 24 recommended: 53 | 2026-05-13T15:54:42+00:00 | Vulnerability · Source |
| CVE-2017-17850 | suse_vex | SUSE CVE CVE-2017-17850 | No product status | 2026-05-13T15:54:37+00:00 | Vulnerability · Source |
| CVE-2017-17913 | suse_vex | SUSE CVE CVE-2017-17913 | known not affected: 14 | 2026-05-13T15:54:33+00:00 | Vulnerability · Source |
| CVE-2017-17915 | suse_vex | SUSE CVE CVE-2017-17915 | known affected: 3 recommended: 14 | 2026-05-13T15:54:32+00:00 | Vulnerability · Source |
| CVE-2017-1000024 | suse_vex | SUSE CVE CVE-2017-1000024 | recommended: 30 | 2026-05-13T15:54:21+00:00 | Vulnerability · Source |
| CVE-2017-1000025 | suse_vex | SUSE CVE CVE-2017-1000025 | No product status | 2026-05-13T15:54:20+00:00 | Vulnerability · Source |
| CVE-2017-1000031 | suse_vex | SUSE CVE CVE-2017-1000031 | No product status | 2026-05-13T15:54:19+00:00 | Vulnerability · Source |
| CVE-2017-1000065 | suse_vex | SUSE CVE CVE-2017-1000065 | No product status | 2026-05-13T15:54:18+00:00 | Vulnerability · Source |
| CVE-2017-1000067 | suse_vex | SUSE CVE CVE-2017-1000067 | No product status | 2026-05-13T15:54:17+00:00 | Vulnerability · Source |
| CVE-2017-1000185 | suse_vex | SUSE CVE CVE-2017-1000185 | No product status | 2026-05-13T15:54:08+00:00 | Vulnerability · Source |
| CVE-2017-1000186 | suse_vex | SUSE CVE CVE-2017-1000186 | No product status | 2026-05-13T15:54:07+00:00 | Vulnerability · Source |
| CVE-2017-1000187 | suse_vex | SUSE CVE CVE-2017-1000187 | No product status | 2026-05-13T15:54:06+00:00 | Vulnerability · Source |
| CVE-2017-1000229 | suse_vex | SUSE CVE CVE-2017-1000229 | recommended: 1 | 2026-05-13T15:54:03+00:00 | Vulnerability · Source |
| CVE-2017-1000362 | suse_vex | SUSE CVE CVE-2017-1000362 | No product status | 2026-05-13T15:53:59+00:00 | Vulnerability · Source |
| CVE-2017-1000369 | suse_vex | SUSE CVE CVE-2017-1000369 | recommended: 18 | 2026-05-13T15:42:14+00:00 | Vulnerability · Source |
| CVE-2017-1000370 | suse_vex | SUSE CVE CVE-2017-1000370 | known not affected: 191 | 2026-05-13T15:42:12+00:00 | Vulnerability · Source |
| CVE-2019-15892 | suse_vex | SUSE CVE CVE-2019-15892 | recommended: 22 | 2026-05-13T15:36:09+00:00 | Vulnerability · Source |
| CVE-2021-28687 | suse_vex | SUSE CVE CVE-2021-28687 | known affected: 297 known not affected: 171 recommended: 367 | 2026-05-13T15:27:15+00:00 | Vulnerability · Source |
| CVE-2022-23959 | suse_vex | SUSE CVE CVE-2022-23959 | recommended: 22 | 2026-05-13T15:20:51+00:00 | Vulnerability · Source |
| CVE-2022-45059 | suse_vex | SUSE CVE CVE-2022-45059 | recommended: 12 | 2026-05-13T15:18:23+00:00 | Vulnerability · Source |
| CVE-2025-15534 | suse_vex | SUSE CVE CVE-2025-15534 | recommended: 4 | 2026-05-13T14:50:47+00:00 | Vulnerability · Source |
| CVE-2025-61669 | suse_vex | SUSE CVE CVE-2025-61669 | recommended: 6 | 2026-05-13T14:27:47+00:00 | Vulnerability · Source |
| CVE-2025-61688 | suse_vex | SUSE CVE CVE-2025-61688 | recommended: 1 | 2026-05-13T14:27:45+00:00 | Vulnerability · Source |
| CVE-2025-64751 | suse_vex | SUSE CVE CVE-2025-64751 | recommended: 21 | 2026-05-13T14:27:35+00:00 | Vulnerability · Source |
| CVE-2026-25710 | suse_vex | SUSE CVE CVE-2026-25710 | No product status | 2026-05-13T14:24:25+00:00 | Vulnerability · Source |
| CVE-2026-33516 | suse_vex | SUSE CVE CVE-2026-33516 | known not affected: 73 | 2026-05-13T14:23:43+00:00 | Vulnerability · Source |
| CVE-2026-6815 | redhat_vex | CVE-2026-6815 | known not affected: 1 | 2026-05-13T14:22:02+00:00 | Vulnerability · Source |
| CVE-2026-43652 | redhat_vex | CVE-2026-43652 | known not affected: 1 | 2026-05-13T14:22:01+00:00 | Vulnerability · Source |