VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-10197 | suse_vex | SUSE CVE CVE-2016-10197 | known affected: 30 recommended: 39 | 2026-07-31T01:47:04+00:00 | Vulnerability · Source |
| CVE-2016-10266 | suse_vex | SUSE CVE CVE-2016-10266 | known affected: 441 known not affected: 80 recommended: 298 | 2026-07-31T01:47:00+00:00 | Vulnerability · Source |
| CVE-2016-11069 | suse_vex | SUSE CVE CVE-2016-11069 | recommended: 1 | 2026-07-31T01:46:58+00:00 | Vulnerability · Source |
| CVE-2017-0750 | suse_vex | SUSE CVE CVE-2017-0750 | known not affected: 48 | 2026-07-31T01:46:55+00:00 | Vulnerability · Source |
| CVE-2017-0900 | suse_vex | SUSE CVE CVE-2017-0900 | known not affected: 54 recommended: 98 | 2026-07-31T01:46:53+00:00 | Vulnerability · Source |
| CVE-2017-3329 | suse_vex | SUSE CVE CVE-2017-3329 | known affected: 35 known not affected: 104 recommended: 28 | 2026-07-31T01:46:42+00:00 | Vulnerability · Source |
| CVE-2017-3733 | suse_vex | SUSE CVE CVE-2017-3733 | known not affected: 69 recommended: 9 | 2026-07-31T01:46:40+00:00 | Vulnerability · Source |
| CVE-2017-5495 | suse_vex | SUSE CVE CVE-2017-5495 | known affected: 1 known not affected: 125 recommended: 350 | 2026-07-31T01:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5550 | suse_vex | SUSE CVE CVE-2017-5550 | known not affected: 48 | 2026-07-31T01:46:29+00:00 | Vulnerability · Source |
| CVE-2017-5651 | suse_vex | SUSE CVE CVE-2017-5651 | known not affected: 54 | 2026-07-31T01:46:27+00:00 | Vulnerability · Source |
| CVE-2017-6314 | suse_vex | SUSE CVE CVE-2017-6314 | known not affected: 540 recommended: 129 | 2026-07-31T01:46:21+00:00 | Vulnerability · Source |
| CVE-2017-6464 | suse_vex | SUSE CVE CVE-2017-6464 | known affected: 31 recommended: 103 | 2026-07-31T01:46:20+00:00 | Vulnerability · Source |
| CVE-2017-7396 | suse_vex | SUSE CVE CVE-2017-7396 | recommended: 34 | 2026-07-31T01:46:08+00:00 | Vulnerability · Source |
| CVE-2017-7478 | suse_vex | SUSE CVE CVE-2017-7478 | known affected: 30 recommended: 41 | 2026-07-31T01:46:05+00:00 | Vulnerability · Source |
| CVE-2017-7593 | suse_vex | SUSE CVE CVE-2017-7593 | known affected: 439 known not affected: 80 recommended: 286 | 2026-07-31T01:45:58+00:00 | Vulnerability · Source |
| CVE-2017-7606 | suse_vex | SUSE CVE CVE-2017-7606 | recommended: 184 | 2026-07-31T01:45:55+00:00 | Vulnerability · Source |
| CVE-2017-7858 | suse_vex | SUSE CVE CVE-2017-7858 | known affected: 6 known not affected: 52 | 2026-07-31T01:45:44+00:00 | Vulnerability · Source |
| CVE-2017-8344 | suse_vex | SUSE CVE CVE-2017-8344 | recommended: 184 | 2026-07-31T01:45:43+00:00 | Vulnerability · Source |
| CVE-2017-8346 | suse_vex | SUSE CVE CVE-2017-8346 | recommended: 184 | 2026-07-31T01:45:41+00:00 | Vulnerability · Source |
| CVE-2017-8349 | suse_vex | SUSE CVE CVE-2017-8349 | recommended: 184 | 2026-07-31T01:45:39+00:00 | Vulnerability · Source |
| CVE-2017-9433 | suse_vex | SUSE CVE CVE-2017-9433 | known not affected: 8 recommended: 2376 | 2026-07-31T01:45:27+00:00 | Vulnerability · Source |
| CVE-2017-9776 | suse_vex | SUSE CVE CVE-2017-9776 | known affected: 52 known not affected: 207 recommended: 165 | 2026-07-31T01:45:23+00:00 | Vulnerability · Source |
| CVE-2017-10684 | suse_vex | SUSE CVE CVE-2017-10684 | known affected: 1 recommended: 231 | 2026-07-31T01:45:15+00:00 | Vulnerability · Source |
| CVE-2017-10784 | suse_vex | SUSE CVE CVE-2017-10784 | known affected: 2 known not affected: 283 recommended: 98 | 2026-07-31T01:45:13+00:00 | Vulnerability · Source |
| CVE-2017-10915 | suse_vex | SUSE CVE CVE-2017-10915 | known affected: 12 known not affected: 104 recommended: 35 | 2026-07-31T01:45:08+00:00 | Vulnerability · Source |
| CVE-2017-10920 | suse_vex | SUSE CVE CVE-2017-10920 | known not affected: 6 recommended: 43 | 2026-07-31T01:45:06+00:00 | Vulnerability · Source |
| CVE-2017-11352 | suse_vex | SUSE CVE CVE-2017-11352 | known affected: 10 known not affected: 101 | 2026-07-31T01:45:03+00:00 | Vulnerability · Source |
| CVE-2017-11403 | suse_vex | SUSE CVE CVE-2017-11403 | known affected: 60 recommended: 186 | 2026-07-31T01:45:01+00:00 | Vulnerability · Source |
| CVE-2017-11505 | suse_vex | SUSE CVE CVE-2017-11505 | known affected: 94 recommended: 186 | 2026-07-31T01:44:58+00:00 | Vulnerability · Source |
| CVE-2017-11534 | suse_vex | SUSE CVE CVE-2017-11534 | recommended: 186 | 2026-07-31T01:44:56+00:00 | Vulnerability · Source |
| CVE-2017-11714 | suse_vex | SUSE CVE CVE-2017-11714 | known affected: 1 recommended: 85 | 2026-07-31T01:44:55+00:00 | Vulnerability · Source |
| CVE-2017-12183 | suse_vex | SUSE CVE CVE-2017-12183 | known affected: 2 known not affected: 52 recommended: 61 | 2026-07-31T01:44:51+00:00 | Vulnerability · Source |
| CVE-2017-12194 | suse_vex | SUSE CVE CVE-2017-12194 | recommended: 77 | 2026-07-31T01:44:50+00:00 | Vulnerability · Source |
| CVE-2017-12429 | suse_vex | SUSE CVE CVE-2017-12429 | known affected: 95 recommended: 186 | 2026-07-31T01:44:48+00:00 | Vulnerability · Source |
| CVE-2017-12643 | suse_vex | SUSE CVE CVE-2017-12643 | known affected: 94 recommended: 186 | 2026-07-31T01:44:43+00:00 | Vulnerability · Source |
| CVE-2017-13016 | suse_vex | SUSE CVE CVE-2017-13016 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:31+00:00 | Vulnerability · Source |
| CVE-2017-13039 | suse_vex | SUSE CVE CVE-2017-13039 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-31T01:44:30+00:00 | Vulnerability · Source |
| CVE-2017-13133 | suse_vex | SUSE CVE CVE-2017-13133 | known not affected: 14 recommended: 172 | 2026-07-31T01:44:27+00:00 | Vulnerability · Source |
| CVE-2017-13730 | suse_vex | SUSE CVE CVE-2017-13730 | known affected: 157 recommended: 201 | 2026-07-31T01:44:25+00:00 | Vulnerability · Source |
| CVE-2017-14064 | suse_vex | SUSE CVE CVE-2017-14064 | known not affected: 94 recommended: 98 | 2026-07-31T01:44:21+00:00 | Vulnerability · Source |
| CVE-2017-14519 | suse_vex | SUSE CVE CVE-2017-14519 | known affected: 12 known not affected: 341 | 2026-07-31T01:44:19+00:00 | Vulnerability · Source |
| CVE-2017-14617 | suse_vex | SUSE CVE CVE-2017-14617 | known affected: 50 known not affected: 55 recommended: 102 | 2026-07-31T01:44:17+00:00 | Vulnerability · Source |
| CVE-2017-14626 | suse_vex | SUSE CVE CVE-2017-14626 | known affected: 10 known not affected: 144 | 2026-07-31T01:44:16+00:00 | Vulnerability · Source |
| CVE-2017-15116 | suse_vex | SUSE CVE CVE-2017-15116 | known not affected: 261 recommended: 12 | 2026-07-31T01:44:12+00:00 | Vulnerability · Source |
| CVE-2017-15652 | suse_vex | SUSE CVE CVE-2017-15652 | known not affected: 233 | 2026-07-31T01:44:07+00:00 | Vulnerability · Source |
| CVE-2017-15715 | suse_vex | SUSE CVE CVE-2017-15715 | known affected: 92 known not affected: 39 recommended: 127 | 2026-07-31T01:44:03+00:00 | Vulnerability · Source |
| CVE-2017-15908 | suse_vex | SUSE CVE CVE-2017-15908 | known affected: 451 known not affected: 240 recommended: 1131 | 2026-07-31T01:43:59+00:00 | Vulnerability · Source |
| CVE-2017-16899 | suse_vex | SUSE CVE CVE-2017-16899 | known affected: 16 known not affected: 16 recommended: 40 | 2026-07-31T01:43:48+00:00 | Vulnerability · Source |
| CVE-2017-17884 | suse_vex | SUSE CVE CVE-2017-17884 | known affected: 94 recommended: 186 | 2026-07-31T01:43:43+00:00 | Vulnerability · Source |
| CVE-2017-18220 | suse_vex | SUSE CVE CVE-2017-18220 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-31T01:43:40+00:00 | Vulnerability · Source |