VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287965 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-8394 | suse_vex | SUSE CVE CVE-2017-8394 | known affected: 394 known not affected: 23 recommended: 340 | 2026-07-31T01:45:38+00:00 | Vulnerability · Source |
| CVE-2017-9122 | suse_vex | SUSE CVE CVE-2017-9122 | known affected: 30 recommended: 208 | 2026-07-31T01:45:34+00:00 | Vulnerability · Source |
| CVE-2017-9128 | suse_vex | SUSE CVE CVE-2017-9128 | known affected: 30 recommended: 208 | 2026-07-31T01:45:32+00:00 | Vulnerability · Source |
| CVE-2017-9208 | suse_vex | SUSE CVE CVE-2017-9208 | known affected: 4 known not affected: 33 recommended: 326 | 2026-07-31T01:45:31+00:00 | Vulnerability · Source |
| CVE-2017-9353 | suse_vex | SUSE CVE CVE-2017-9353 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-31T01:45:29+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-9746 | suse_vex | SUSE CVE CVE-2017-9746 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-31T01:45:25+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-9985 | suse_vex | SUSE CVE CVE-2017-9985 | known not affected: 510 | 2026-07-31T01:45:22+00:00 | Vulnerability · Source |
| CVE-2017-10320 | suse_vex | SUSE CVE CVE-2017-10320 | known not affected: 237 recommended: 415 | 2026-07-31T01:45:20+00:00 | Vulnerability · Source |
| CVE-2017-10356 | suse_vex | SUSE CVE CVE-2017-10356 | known affected: 497 known not affected: 226 recommended: 758 | 2026-07-31T01:45:18+00:00 | Vulnerability · Source |
| CVE-2017-10664 | suse_vex | SUSE CVE CVE-2017-10664 | known affected: 394 known not affected: 65 recommended: 2005 | 2026-07-31T01:45:16+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-10790 | suse_vex | SUSE CVE CVE-2017-10790 | known affected: 443 known not affected: 213 recommended: 425 | 2026-07-31T01:45:12+00:00 | Vulnerability · Source |
| CVE-2017-10806 | suse_vex | SUSE CVE CVE-2017-10806 | known affected: 438 known not affected: 91 recommended: 1894 | 2026-07-31T01:45:09+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-11335 | suse_vex | SUSE CVE CVE-2017-11335 | known not affected: 123 recommended: 22 | 2026-07-31T01:45:04+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-11407 | suse_vex | SUSE CVE CVE-2017-11407 | known affected: 86 known not affected: 115 recommended: 565 | 2026-07-31T01:45:00+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-12145 | suse_vex | SUSE CVE CVE-2017-12145 | known affected: 4 known not affected: 91 | 2026-07-31T01:44:53+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-12452 | suse_vex | SUSE CVE CVE-2017-12452 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:46+00:00 | Vulnerability · Source |
| CVE-2017-12454 | suse_vex | SUSE CVE CVE-2017-12454 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:45+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-12814 | suse_vex | SUSE CVE CVE-2017-12814 | known not affected: 303 recommended: 15 | 2026-07-31T01:44:41+00:00 | Vulnerability · Source |
| CVE-2017-12852 | suse_vex | SUSE CVE CVE-2017-12852 | known affected: 417 known not affected: 124 recommended: 274 | 2026-07-31T01:44:40+00:00 | Vulnerability · Source |
| CVE-2017-12902 | suse_vex | SUSE CVE CVE-2017-12902 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:38+00:00 | Vulnerability · Source |
| CVE-2017-12955 | suse_vex | SUSE CVE CVE-2017-12955 | known not affected: 16 recommended: 163 | 2026-07-31T01:44:36+00:00 | Vulnerability · Source |
| CVE-2017-12996 | suse_vex | SUSE CVE CVE-2017-12996 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:34+00:00 | Vulnerability · Source |
| CVE-2017-13002 | suse_vex | SUSE CVE CVE-2017-13002 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:33+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-13081 | suse_vex | SUSE CVE CVE-2017-13081 | known affected: 6 known not affected: 354 recommended: 1393 | 2026-07-31T01:44:28+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-13757 | suse_vex | SUSE CVE CVE-2017-13757 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:23+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 |