VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
299422 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2017-14687 | suse_vex | SUSE CVE CVE-2017-14687 | No product status | 2026-05-13T15:57:30+00:00 | Vulnerability · Source |
| CVE-2017-14727 | suse_vex | SUSE CVE CVE-2017-14727 | recommended: 9 | 2026-05-13T15:57:29+00:00 | Vulnerability · Source |
| CVE-2017-14767 | suse_vex | SUSE CVE CVE-2017-14767 | No product status | 2026-05-13T15:57:27+00:00 | Vulnerability · Source |
| CVE-2017-14857 | suse_vex | SUSE CVE CVE-2017-14857 | known affected: 2 known not affected: 44 | 2026-05-13T15:57:24+00:00 | Vulnerability · Source |
| CVE-2017-14865 | suse_vex | SUSE CVE CVE-2017-14865 | known affected: 2 known not affected: 34 | 2026-05-13T15:57:18+00:00 | Vulnerability · Source |
| CVE-2017-15019 | suse_vex | SUSE CVE CVE-2017-15019 | known not affected: 15 recommended: 5 | 2026-05-13T15:57:09+00:00 | Vulnerability · Source |
| CVE-2017-15047 | suse_vex | SUSE CVE CVE-2017-15047 | recommended: 38 | 2026-05-13T15:57:08+00:00 | Vulnerability · Source |
| CVE-2017-15056 | suse_vex | SUSE CVE CVE-2017-15056 | No product status | 2026-05-13T15:57:06+00:00 | Vulnerability · Source |
| CVE-2017-15110 | suse_vex | SUSE CVE CVE-2017-15110 | No product status | 2026-05-13T15:57:01+00:00 | Vulnerability · Source |
| CVE-2017-15227 | suse_vex | SUSE CVE CVE-2017-15227 | recommended: 4 | 2026-05-13T15:56:56+00:00 | Vulnerability · Source |
| CVE-2017-15369 | suse_vex | SUSE CVE CVE-2017-15369 | recommended: 2 | 2026-05-13T15:56:51+00:00 | Vulnerability · Source |
| CVE-2017-15370 | suse_vex | SUSE CVE CVE-2017-15370 | recommended: 8 | 2026-05-13T15:56:50+00:00 | Vulnerability · Source |
| CVE-2017-15535 | suse_vex | SUSE CVE CVE-2017-15535 | known not affected: 3 recommended: 5 | 2026-05-13T15:56:49+00:00 | Vulnerability · Source |
| CVE-2017-15568 | suse_vex | SUSE CVE CVE-2017-15568 | No product status | 2026-05-13T15:56:45+00:00 | Vulnerability · Source |
| CVE-2017-15569 | suse_vex | SUSE CVE CVE-2017-15569 | No product status | 2026-05-13T15:56:44+00:00 | Vulnerability · Source |
| CVE-2017-15570 | suse_vex | SUSE CVE CVE-2017-15570 | No product status | 2026-05-13T15:56:43+00:00 | Vulnerability · Source |
| CVE-2017-15571 | suse_vex | SUSE CVE CVE-2017-15571 | No product status | 2026-05-13T15:56:42+00:00 | Vulnerability · Source |
| CVE-2017-15572 | suse_vex | SUSE CVE CVE-2017-15572 | No product status | 2026-05-13T15:56:41+00:00 | Vulnerability · Source |
| CVE-2017-15573 | suse_vex | SUSE CVE CVE-2017-15573 | No product status | 2026-05-13T15:56:39+00:00 | Vulnerability · Source |
| CVE-2017-15574 | suse_vex | SUSE CVE CVE-2017-15574 | No product status | 2026-05-13T15:56:38+00:00 | Vulnerability · Source |
| CVE-2017-15575 | suse_vex | SUSE CVE CVE-2017-15575 | No product status | 2026-05-13T15:56:37+00:00 | Vulnerability · Source |
| CVE-2017-15576 | suse_vex | SUSE CVE CVE-2017-15576 | No product status | 2026-05-13T15:56:36+00:00 | Vulnerability · Source |
| CVE-2017-15577 | suse_vex | SUSE CVE CVE-2017-15577 | No product status | 2026-05-13T15:56:35+00:00 | Vulnerability · Source |
| CVE-2017-15589 | suse_vex | SUSE CVE CVE-2017-15589 | known affected: 26 known not affected: 62 recommended: 129 | 2026-05-13T15:56:32+00:00 | Vulnerability · Source |
| CVE-2017-15723 | suse_vex | SUSE CVE CVE-2017-15723 | recommended: 4 | 2026-05-13T15:56:19+00:00 | Vulnerability · Source |
| CVE-2017-15737 | suse_vex | SUSE CVE CVE-2017-15737 | No product status | 2026-05-13T15:56:18+00:00 | Vulnerability · Source |
| CVE-2017-15741 | suse_vex | SUSE CVE CVE-2017-15741 | No product status | 2026-05-13T15:56:17+00:00 | Vulnerability · Source |
| CVE-2017-15789 | suse_vex | SUSE CVE CVE-2017-15789 | No product status | 2026-05-13T15:56:16+00:00 | Vulnerability · Source |
| CVE-2017-15864 | suse_vex | SUSE CVE CVE-2017-15864 | No product status | 2026-05-13T15:56:15+00:00 | Vulnerability · Source |
| CVE-2017-15924 | suse_vex | SUSE CVE CVE-2017-15924 | recommended: 4 | 2026-05-13T15:56:11+00:00 | Vulnerability · Source |
| CVE-2017-16516 | suse_vex | SUSE CVE CVE-2017-16516 | No product status | 2026-05-13T15:56:03+00:00 | Vulnerability · Source |
| CVE-2017-16547 | suse_vex | SUSE CVE CVE-2017-16547 | known affected: 3 recommended: 14 | 2026-05-13T15:56:00+00:00 | Vulnerability · Source |
| CVE-2017-16641 | suse_vex | SUSE CVE CVE-2017-16641 | recommended: 3 | 2026-05-13T15:55:58+00:00 | Vulnerability · Source |
| CVE-2017-16660 | suse_vex | SUSE CVE CVE-2017-16660 | recommended: 3 | 2026-05-13T15:55:54+00:00 | Vulnerability · Source |
| CVE-2017-16664 | suse_vex | SUSE CVE CVE-2017-16664 | No product status | 2026-05-13T15:55:53+00:00 | Vulnerability · Source |