VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2017-7979 | suse_vex | SUSE CVE CVE-2017-7979 | known not affected: 34 | 2026-07-26T00:40:02+00:00 | Vulnerability · Source |
| CVE-2017-8053 | suse_vex | SUSE CVE CVE-2017-8053 | known not affected: 37 | 2026-07-26T00:40:01+00:00 | Vulnerability · Source |
| CVE-2017-8064 | suse_vex | SUSE CVE CVE-2017-8064 | known not affected: 34 | 2026-07-26T00:40:00+00:00 | Vulnerability · Source |
| CVE-2017-8070 | suse_vex | SUSE CVE CVE-2017-8070 | known not affected: 34 | 2026-07-26T00:39:59+00:00 | Vulnerability · Source |
| CVE-2017-8071 | suse_vex | SUSE CVE CVE-2017-8071 | known not affected: 34 | 2026-07-26T00:39:57+00:00 | Vulnerability · Source |
| CVE-2017-8281 | suse_vex | SUSE CVE CVE-2017-8281 | known not affected: 78 | 2026-07-26T00:39:56+00:00 | Vulnerability · Source |
| CVE-2017-8287 | suse_vex | SUSE CVE CVE-2017-8287 | known affected: 2 known not affected: 134 recommended: 263 | 2026-07-26T00:39:55+00:00 | Vulnerability · Source |
| CVE-2017-8288 | suse_vex | SUSE CVE CVE-2017-8288 | recommended: 308 | 2026-07-26T00:39:54+00:00 | Vulnerability · Source |
| CVE-2017-8343 | suse_vex | SUSE CVE CVE-2017-8343 | known not affected: 50 recommended: 134 | 2026-07-26T00:39:53+00:00 | Vulnerability · Source |
| CVE-2017-8352 | suse_vex | SUSE CVE CVE-2017-8352 | recommended: 184 | 2026-07-26T00:39:51+00:00 | Vulnerability · Source |
| CVE-2017-8397 | suse_vex | SUSE CVE CVE-2017-8397 | known affected: 1 known not affected: 134 recommended: 54 | 2026-07-26T00:39:44+00:00 | Vulnerability · Source |
| CVE-2017-8398 | suse_vex | SUSE CVE CVE-2017-8398 | known affected: 2 known not affected: 163 recommended: 54 | 2026-07-26T00:39:42+00:00 | Vulnerability · Source |
| CVE-2017-8422 | suse_vex | SUSE CVE CVE-2017-8422 | known affected: 1 known not affected: 10 recommended: 165 | 2026-07-26T00:39:41+00:00 | Vulnerability · Source |
| CVE-2017-8765 | suse_vex | SUSE CVE CVE-2017-8765 | recommended: 184 | 2026-07-26T00:39:39+00:00 | Vulnerability · Source |
| CVE-2017-8786 | suse_vex | SUSE CVE CVE-2017-8786 | known affected: 320 known not affected: 482 recommended: 412 | 2026-07-26T00:39:37+00:00 | Vulnerability · Source |
| CVE-2017-8804 | suse_vex | SUSE CVE CVE-2017-8804 | known affected: 62 recommended: 265 | 2026-07-26T00:39:36+00:00 | Vulnerability · Source |
| CVE-2017-8816 | suse_vex | SUSE CVE CVE-2017-8816 | known affected: 322 known not affected: 80 recommended: 399 | 2026-07-26T00:39:34+00:00 | Vulnerability · Source |
| CVE-2017-8871 | suse_vex | SUSE CVE CVE-2017-8871 | known affected: 28 known not affected: 36 recommended: 232 | 2026-07-26T00:39:29+00:00 | Vulnerability · Source |
| CVE-2017-8908 | suse_vex | SUSE CVE CVE-2017-8908 | known affected: 6 known not affected: 59 | 2026-07-26T00:39:26+00:00 | Vulnerability · Source |
| CVE-2017-8924 | suse_vex | SUSE CVE CVE-2017-8924 | known affected: 2 known not affected: 7 recommended: 297 | 2026-07-26T00:39:25+00:00 | Vulnerability · Source |
| CVE-2017-8925 | suse_vex | SUSE CVE CVE-2017-8925 | known not affected: 643 recommended: 297 | 2026-07-26T00:39:23+00:00 | Vulnerability · Source |
| CVE-2017-9059 | suse_vex | SUSE CVE CVE-2017-9059 | known not affected: 136 recommended: 89 | 2026-07-26T00:39:20+00:00 | Vulnerability · Source |
| CVE-2017-9083 | suse_vex | SUSE CVE CVE-2017-9083 | known affected: 14 recommended: 12 | 2026-07-26T00:39:16+00:00 | Vulnerability · Source |
| CVE-2017-9105 | suse_vex | SUSE CVE CVE-2017-9105 | known affected: 18 recommended: 44 | 2026-07-26T00:39:14+00:00 | Vulnerability · Source |
| CVE-2017-9126 | suse_vex | SUSE CVE CVE-2017-9126 | known affected: 30 recommended: 208 | 2026-07-26T00:39:08+00:00 | Vulnerability · Source |
| CVE-2017-9147 | suse_vex | SUSE CVE CVE-2017-9147 | known not affected: 13 recommended: 22 | 2026-07-26T00:39:06+00:00 | Vulnerability · Source |