VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-7486 | suse_vex | SUSE CVE CVE-2017-7486 | recommended: 154 | 2026-07-26T00:41:57+00:00 | Vulnerability · Source |
| CVE-2017-7501 | suse_vex | SUSE CVE CVE-2017-7501 | known affected: 54 known not affected: 147 recommended: 121 | 2026-07-26T00:41:52+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-7519 | suse_vex | SUSE CVE CVE-2017-7519 | known not affected: 33 recommended: 42 | 2026-07-26T00:41:48+00:00 | Vulnerability · Source |
| CVE-2017-7522 | suse_vex | SUSE CVE CVE-2017-7522 | known affected: 31 known not affected: 60 recommended: 191 | 2026-07-26T00:41:46+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-7592 | suse_vex | SUSE CVE CVE-2017-7592 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T00:41:40+00:00 | Vulnerability · Source |
| CVE-2017-7594 | suse_vex | SUSE CVE CVE-2017-7594 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T00:41:38+00:00 | Vulnerability · Source |
| CVE-2017-7600 | suse_vex | SUSE CVE CVE-2017-7600 | known affected: 45 known not affected: 80 recommended: 281 | 2026-07-26T00:41:35+00:00 | Vulnerability · Source |
| CVE-2017-7607 | suse_vex | SUSE CVE CVE-2017-7607 | known affected: 522 recommended: 834 | 2026-07-26T00:41:33+00:00 | Vulnerability · Source |
| CVE-2017-7610 | suse_vex | SUSE CVE CVE-2017-7610 | known affected: 522 recommended: 834 | 2026-07-26T00:41:31+00:00 | Vulnerability · Source |
| CVE-2017-7611 | suse_vex | SUSE CVE CVE-2017-7611 | known affected: 522 recommended: 834 | 2026-07-26T00:41:29+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-7613 | suse_vex | SUSE CVE CVE-2017-7613 | known affected: 522 known not affected: 1 recommended: 825 | 2026-07-26T00:41:26+00:00 | Vulnerability · Source |
| CVE-2017-7616 | suse_vex | SUSE CVE CVE-2017-7616 | known affected: 14 known not affected: 343 recommended: 346 | 2026-07-26T00:41:25+00:00 | Vulnerability · Source |
| CVE-2017-7618 | suse_vex | SUSE CVE CVE-2017-7618 | known affected: 12 known not affected: 425 recommended: 101 | 2026-07-26T00:41:24+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-7702 | suse_vex | SUSE CVE CVE-2017-7702 | known affected: 1 known not affected: 115 recommended: 588 | 2026-07-26T00:41:15+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-7747 | suse_vex | SUSE CVE CVE-2017-7747 | known affected: 1 recommended: 588 | 2026-07-26T00:41:06+00:00 | Vulnerability · Source |
| CVE-2017-7751 | suse_vex | SUSE CVE CVE-2017-7751 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:41:02+00:00 | Vulnerability · Source |
| CVE-2017-7752 | suse_vex | SUSE CVE CVE-2017-7752 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:41:00+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-7764 | suse_vex | SUSE CVE CVE-2017-7764 | known affected: 2 known not affected: 42 recommended: 462 | 2026-07-26T00:40:53+00:00 | Vulnerability · Source |
| CVE-2017-7772 | suse_vex | SUSE CVE CVE-2017-7772 | known affected: 2 known not affected: 42 recommended: 324 | 2026-07-26T00:40:49+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-7807 | suse_vex | SUSE CVE CVE-2017-7807 | known affected: 1 known not affected: 42 recommended: 417 | 2026-07-26T00:40:31+00:00 | Vulnerability · Source |
| CVE-2017-7809 | suse_vex | SUSE CVE CVE-2017-7809 | known affected: 1 known not affected: 42 recommended: 14 | 2026-07-26T00:40:30+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 |
| CVE-2017-7941 | suse_vex | SUSE CVE CVE-2017-7941 | recommended: 184 | 2026-07-26T00:40:06+00:00 | Vulnerability · Source |
| CVE-2017-7943 | suse_vex | SUSE CVE CVE-2017-7943 | known not affected: 14 recommended: 170 | 2026-07-26T00:40:05+00:00 | Vulnerability · Source |
| CVE-2017-7948 | suse_vex | SUSE CVE CVE-2017-7948 | known affected: 6 known not affected: 59 | 2026-07-26T00:40:04+00:00 | Vulnerability · Source |