VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5957 | suse_vex | SUSE CVE CVE-2017-5957 | recommended: 134 | 2026-07-26T00:44:49+00:00 | Vulnerability · Source |
| CVE-2017-6056 | suse_vex | SUSE CVE CVE-2017-6056 | known not affected: 54 | 2026-07-26T00:44:39+00:00 | Vulnerability · Source |
| CVE-2017-6181 | suse_vex | SUSE CVE CVE-2017-6181 | known not affected: 58 | 2026-07-26T00:44:38+00:00 | Vulnerability · Source |
| CVE-2017-6311 | suse_vex | SUSE CVE CVE-2017-6311 | known affected: 14 known not affected: 60 | 2026-07-26T00:44:35+00:00 | Vulnerability · Source |
| CVE-2017-6317 | suse_vex | SUSE CVE CVE-2017-6317 | recommended: 29 | 2026-07-26T00:44:32+00:00 | Vulnerability · Source |
| CVE-2017-6462 | suse_vex | SUSE CVE CVE-2017-6462 | known affected: 31 recommended: 103 | 2026-07-26T00:44:16+00:00 | Vulnerability · Source |
| CVE-2017-6590 | suse_vex | SUSE CVE CVE-2017-6590 | known not affected: 172 recommended: 253 | 2026-07-26T00:44:09+00:00 | Vulnerability · Source |
| CVE-2017-6830 | suse_vex | SUSE CVE CVE-2017-6830 | known affected: 45 recommended: 202 | 2026-07-26T00:44:05+00:00 | Vulnerability · Source |
| CVE-2017-6835 | suse_vex | SUSE CVE CVE-2017-6835 | known affected: 45 recommended: 202 | 2026-07-26T00:44:00+00:00 | Vulnerability · Source |
| CVE-2017-6852 | suse_vex | SUSE CVE CVE-2017-6852 | known not affected: 100 | 2026-07-26T00:43:58+00:00 | Vulnerability · Source |
| CVE-2017-6874 | suse_vex | SUSE CVE CVE-2017-6874 | known not affected: 343 | 2026-07-26T00:43:56+00:00 | Vulnerability · Source |
| CVE-2017-7006 | suse_vex | SUSE CVE CVE-2017-7006 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:49+00:00 | Vulnerability · Source |
| CVE-2017-7111 | suse_vex | SUSE CVE CVE-2017-7111 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:09+00:00 | Vulnerability · Source |
| CVE-2017-7209 | suse_vex | SUSE CVE CVE-2017-7209 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-26T00:42:56+00:00 | Vulnerability · Source |
| CVE-2017-7228 | suse_vex | SUSE CVE CVE-2017-7228 | known affected: 13 recommended: 111 | 2026-07-26T00:42:46+00:00 | Vulnerability · Source |
| CVE-2017-7244 | suse_vex | SUSE CVE CVE-2017-7244 | known affected: 415 known not affected: 537 recommended: 644 | 2026-07-26T00:42:43+00:00 | Vulnerability · Source |
| CVE-2017-7302 | suse_vex | SUSE CVE CVE-2017-7302 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-26T00:42:32+00:00 | Vulnerability · Source |
| CVE-2017-7319 | suse_vex | SUSE CVE CVE-2017-7319 | known not affected: 64 | 2026-07-26T00:42:28+00:00 | Vulnerability · Source |
| CVE-2017-7392 | suse_vex | SUSE CVE CVE-2017-7392 | recommended: 34 | 2026-07-26T00:42:21+00:00 | Vulnerability · Source |
| CVE-2017-7393 | suse_vex | SUSE CVE CVE-2017-7393 | recommended: 34 | 2026-07-26T00:42:19+00:00 | Vulnerability · Source |
| CVE-2017-7395 | suse_vex | SUSE CVE CVE-2017-7395 | recommended: 34 | 2026-07-26T00:42:17+00:00 | Vulnerability · Source |
| CVE-2017-7471 | suse_vex | SUSE CVE CVE-2017-7471 | known affected: 420 known not affected: 137 recommended: 1812 | 2026-07-26T00:42:08+00:00 | Vulnerability · Source |
| CVE-2017-7472 | suse_vex | SUSE CVE CVE-2017-7472 | known affected: 23 known not affected: 319 recommended: 221 | 2026-07-26T00:42:06+00:00 | Vulnerability · Source |
| CVE-2017-7486 | suse_vex | SUSE CVE CVE-2017-7486 | recommended: 154 | 2026-07-26T00:41:57+00:00 | Vulnerability · Source |
| CVE-2017-7516 | suse_vex | SUSE CVE CVE-2017-7516 | known not affected: 27 | 2026-07-26T00:41:50+00:00 | Vulnerability · Source |
| CVE-2017-7548 | suse_vex | SUSE CVE CVE-2017-7548 | known affected: 98 known not affected: 45 recommended: 252 | 2026-07-26T00:41:42+00:00 | Vulnerability · Source |
| CVE-2017-7612 | suse_vex | SUSE CVE CVE-2017-7612 | known affected: 522 recommended: 834 | 2026-07-26T00:41:28+00:00 | Vulnerability · Source |
| CVE-2017-7659 | suse_vex | SUSE CVE CVE-2017-7659 | known not affected: 63 recommended: 87 | 2026-07-26T00:41:22+00:00 | Vulnerability · Source |
| CVE-2017-7674 | suse_vex | SUSE CVE CVE-2017-7674 | known affected: 46 known not affected: 19 recommended: 154 | 2026-07-26T00:41:21+00:00 | Vulnerability · Source |
| CVE-2017-7701 | suse_vex | SUSE CVE CVE-2017-7701 | known affected: 1 recommended: 588 | 2026-07-26T00:41:17+00:00 | Vulnerability · Source |
| CVE-2017-7741 | suse_vex | SUSE CVE CVE-2017-7741 | known affected: 1 recommended: 68 | 2026-07-26T00:41:11+00:00 | Vulnerability · Source |
| CVE-2017-7754 | suse_vex | SUSE CVE CVE-2017-7754 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:40:58+00:00 | Vulnerability · Source |
| CVE-2017-7781 | suse_vex | SUSE CVE CVE-2017-7781 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:42+00:00 | Vulnerability · Source |
| CVE-2017-7783 | suse_vex | SUSE CVE CVE-2017-7783 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:39+00:00 | Vulnerability · Source |
| CVE-2017-7784 | suse_vex | SUSE CVE CVE-2017-7784 | known affected: 1 known not affected: 42 recommended: 417 | 2026-07-26T00:40:38+00:00 | Vulnerability · Source |
| CVE-2017-7788 | suse_vex | SUSE CVE CVE-2017-7788 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:36+00:00 | Vulnerability · Source |
| CVE-2017-7806 | suse_vex | SUSE CVE CVE-2017-7806 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:33+00:00 | Vulnerability · Source |
| CVE-2017-7815 | suse_vex | SUSE CVE CVE-2017-7815 | known not affected: 42 recommended: 12 | 2026-07-26T00:40:27+00:00 | Vulnerability · Source |
| CVE-2017-7817 | suse_vex | SUSE CVE CVE-2017-7817 | known not affected: 42 recommended: 12 | 2026-07-26T00:40:26+00:00 | Vulnerability · Source |
| CVE-2017-7820 | suse_vex | SUSE CVE CVE-2017-7820 | known not affected: 42 recommended: 12 | 2026-07-26T00:40:23+00:00 | Vulnerability · Source |
| CVE-2017-7821 | suse_vex | SUSE CVE CVE-2017-7821 | known not affected: 42 recommended: 12 | 2026-07-26T00:40:22+00:00 | Vulnerability · Source |
| CVE-2017-7831 | suse_vex | SUSE CVE CVE-2017-7831 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:18+00:00 | Vulnerability · Source |
| CVE-2017-7832 | suse_vex | SUSE CVE CVE-2017-7832 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:17+00:00 | Vulnerability · Source |
| CVE-2017-7835 | suse_vex | SUSE CVE CVE-2017-7835 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:16+00:00 | Vulnerability · Source |
| CVE-2017-7839 | suse_vex | SUSE CVE CVE-2017-7839 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:14+00:00 | Vulnerability · Source |
| CVE-2017-7840 | suse_vex | SUSE CVE CVE-2017-7840 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:13+00:00 | Vulnerability · Source |
| CVE-2017-7842 | suse_vex | SUSE CVE CVE-2017-7842 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:40:12+00:00 | Vulnerability · Source |
| CVE-2017-7864 | suse_vex | SUSE CVE CVE-2017-7864 | known affected: 36 known not affected: 18 recommended: 37 | 2026-07-26T00:40:10+00:00 | Vulnerability · Source |
| CVE-2017-7867 | suse_vex | SUSE CVE CVE-2017-7867 | recommended: 136 | 2026-07-26T00:40:09+00:00 | Vulnerability · Source |
| CVE-2017-7874 | suse_vex | SUSE CVE CVE-2017-7874 | known affected: 22 known not affected: 128 | 2026-07-26T00:40:08+00:00 | Vulnerability · Source |