VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
308823 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-11069 | suse_vex | SUSE CVE CVE-2016-11069 | recommended: 3 | 2026-10-17T02:21:36+00:00 | Vulnerability · Source |
| CVE-2016-11071 | suse_vex | SUSE CVE CVE-2016-11071 | recommended: 3 | 2026-10-17T02:21:35+00:00 | Vulnerability · Source |
| CVE-2016-11072 | suse_vex | SUSE CVE CVE-2016-11072 | recommended: 3 | 2026-10-17T02:21:34+00:00 | Vulnerability · Source |
| CVE-2016-11074 | suse_vex | SUSE CVE CVE-2016-11074 | recommended: 3 | 2026-10-17T02:21:32+00:00 | Vulnerability · Source |
| CVE-2016-11079 | suse_vex | SUSE CVE CVE-2016-11079 | recommended: 3 | 2026-10-17T02:21:31+00:00 | Vulnerability · Source |
| CVE-2016-11080 | suse_vex | SUSE CVE CVE-2016-11080 | recommended: 3 | 2026-10-17T02:21:30+00:00 | Vulnerability · Source |
| CVE-2016-1000342 | suse_vex | SUSE CVE CVE-2016-1000342 | known affected: 0 known not affected: 18 recommended: 142 | 2026-10-17T02:21:29+00:00 | Vulnerability · Source |
| CVE-2016-1000345 | suse_vex | SUSE CVE CVE-2016-1000345 | known affected: 0 known not affected: 18 recommended: 142 | 2026-10-17T02:21:28+00:00 | Vulnerability · Source |
| CVE-2017-0663 | suse_vex | SUSE CVE CVE-2017-0663 | known affected: 393 known not affected: 106 recommended: 522 | 2026-10-17T02:21:26+00:00 | Vulnerability · Source |
| CVE-2017-2355 | suse_vex | SUSE CVE CVE-2017-2355 | known affected: 0 known not affected: 275 recommended: 915 | 2026-10-17T02:21:25+00:00 | Vulnerability · Source |
| CVE-2017-2364 | suse_vex | SUSE CVE CVE-2017-2364 | known affected: 0 known not affected: 275 recommended: 915 | 2026-10-17T02:21:23+00:00 | Vulnerability · Source |
| CVE-2017-2365 | suse_vex | SUSE CVE CVE-2017-2365 | known affected: 0 known not affected: 275 recommended: 927 | 2026-10-17T02:21:22+00:00 | Vulnerability · Source |
| CVE-2017-2371 | suse_vex | SUSE CVE CVE-2017-2371 | known affected: 0 known not affected: 275 recommended: 927 | 2026-10-17T02:21:20+00:00 | Vulnerability · Source |
| CVE-2017-2373 | suse_vex | SUSE CVE CVE-2017-2373 | known affected: 0 known not affected: 275 recommended: 927 | 2026-10-17T02:21:19+00:00 | Vulnerability · Source |
| CVE-2017-2539 | suse_vex | SUSE CVE CVE-2017-2539 | known affected: 98 known not affected: 187 recommended: 915 | 2026-10-17T02:21:17+00:00 | Vulnerability · Source |
| CVE-2017-2591 | suse_vex | SUSE CVE CVE-2017-2591 | known affected: 0 known not affected: 203 | 2026-10-17T02:21:16+00:00 | Vulnerability · Source |
| CVE-2017-2616 | suse_vex | SUSE CVE CVE-2017-2616 | known affected: 320 known not affected: 97 recommended: 1688 | 2026-10-17T02:21:14+00:00 | Vulnerability · Source |
| CVE-2017-2620 | suse_vex | SUSE CVE CVE-2017-2620 | known affected: 360 known not affected: 195 recommended: 2408 | 2026-10-17T02:21:12+00:00 | Vulnerability · Source |
| CVE-2017-2635 | suse_vex | SUSE CVE CVE-2017-2635 | known affected: 394 known not affected: 426 recommended: 1889 | 2026-10-17T02:21:10+00:00 | Vulnerability · Source |
| CVE-2017-3137 | suse_vex | SUSE CVE CVE-2017-3137 | known affected: 58 known not affected: 405 recommended: 890 | 2026-10-17T02:21:09+00:00 | Vulnerability · Source |
| CVE-2017-3144 | suse_vex | SUSE CVE CVE-2017-3144 | known affected: 344 known not affected: 105 recommended: 401 | 2026-10-17T02:21:07+00:00 | Vulnerability · Source |
| CVE-2017-3145 | suse_vex | SUSE CVE CVE-2017-3145 | known affected: 320 known not affected: 434 recommended: 939 | 2026-10-17T02:21:06+00:00 | Vulnerability · Source |
| CVE-2017-3244 | suse_vex | SUSE CVE CVE-2017-3244 | known affected: 0 known not affected: 93 recommended: 675 | 2026-10-17T02:21:04+00:00 | Vulnerability · Source |
| CVE-2017-3302 | suse_vex | SUSE CVE CVE-2017-3302 | known affected: 35 known not affected: 116 recommended: 665 | 2026-10-17T02:21:02+00:00 | Vulnerability · Source |
| CVE-2017-3318 | suse_vex | SUSE CVE CVE-2017-3318 | known affected: 0 known not affected: 93 recommended: 685 | 2026-10-17T02:21:01+00:00 | Vulnerability · Source |
| CVE-2017-3586 | suse_vex | SUSE CVE CVE-2017-3586 | recommended: 19 | 2026-10-17T02:20:59+00:00 | Vulnerability · Source |
| CVE-2017-3604 | suse_vex | SUSE CVE CVE-2017-3604 | No product status | 2026-10-17T02:20:58+00:00 | Vulnerability · Source |
| CVE-2017-3605 | suse_vex | SUSE CVE CVE-2017-3605 | No product status | 2026-10-17T02:20:57+00:00 | Vulnerability · Source |
| CVE-2017-3611 | suse_vex | SUSE CVE CVE-2017-3611 | No product status | 2026-10-17T02:20:55+00:00 | Vulnerability · Source |
| CVE-2017-3612 | suse_vex | SUSE CVE CVE-2017-3612 | No product status | 2026-10-17T02:20:54+00:00 | Vulnerability · Source |
| CVE-2017-3613 | suse_vex | SUSE CVE CVE-2017-3613 | No product status | 2026-10-17T02:20:52+00:00 | Vulnerability · Source |
| CVE-2017-3616 | suse_vex | SUSE CVE CVE-2017-3616 | No product status | 2026-10-17T02:20:50+00:00 | Vulnerability · Source |
| CVE-2017-3653 | suse_vex | SUSE CVE CVE-2017-3653 | known affected: 35 known not affected: 116 recommended: 617 | 2026-10-17T02:20:48+00:00 | Vulnerability · Source |
| CVE-2017-3731 | suse_vex | SUSE CVE CVE-2017-3731 | known affected: 392 known not affected: 356 recommended: 1049 | 2026-10-17T02:20:46+00:00 | Vulnerability · Source |
| CVE-2017-5031 | suse_vex | SUSE CVE CVE-2017-5031 | known affected: 0 known not affected: 110 recommended: 243 | 2026-10-17T02:20:45+00:00 | Vulnerability · Source |
| CVE-2017-5339 | suse_vex | SUSE CVE CVE-2017-5339 | recommended: 151 | 2026-10-17T02:20:43+00:00 | Vulnerability · Source |
| CVE-2017-5373 | suse_vex | SUSE CVE CVE-2017-5373 | known affected: 1 recommended: 416 | 2026-10-17T02:20:42+00:00 | Vulnerability · Source |
| CVE-2017-5376 | suse_vex | SUSE CVE CVE-2017-5376 | known affected: 1 recommended: 416 | 2026-10-17T02:20:41+00:00 | Vulnerability · Source |
| CVE-2017-5384 | suse_vex | SUSE CVE CVE-2017-5384 | known affected: 1 known not affected: 43 recommended: 249 | 2026-10-17T02:20:39+00:00 | Vulnerability · Source |
| CVE-2017-5385 | suse_vex | SUSE CVE CVE-2017-5385 | known affected: 1 known not affected: 43 recommended: 249 | 2026-10-17T02:20:38+00:00 | Vulnerability · Source |
| CVE-2017-5387 | suse_vex | SUSE CVE CVE-2017-5387 | known affected: 1 known not affected: 43 recommended: 249 | 2026-10-17T02:20:36+00:00 | Vulnerability · Source |
| CVE-2017-5388 | suse_vex | SUSE CVE CVE-2017-5388 | known affected: 1 known not affected: 43 recommended: 249 | 2026-10-17T02:20:35+00:00 | Vulnerability · Source |
| CVE-2017-5392 | suse_vex | SUSE CVE CVE-2017-5392 | known affected: 1 known not affected: 43 recommended: 249 | 2026-10-17T02:20:34+00:00 | Vulnerability · Source |
| CVE-2017-5398 | suse_vex | SUSE CVE CVE-2017-5398 | known affected: 1 recommended: 416 | 2026-10-17T02:20:32+00:00 | Vulnerability · Source |
| CVE-2017-5399 | suse_vex | SUSE CVE CVE-2017-5399 | known affected: 1 recommended: 333 | 2026-10-17T02:20:31+00:00 | Vulnerability · Source |
| CVE-2017-5401 | suse_vex | SUSE CVE CVE-2017-5401 | known affected: 1 recommended: 416 | 2026-10-17T02:20:30+00:00 | Vulnerability · Source |
| CVE-2017-5412 | suse_vex | SUSE CVE CVE-2017-5412 | known affected: 1 recommended: 333 | 2026-10-17T02:20:28+00:00 | Vulnerability · Source |
| CVE-2017-5422 | suse_vex | SUSE CVE CVE-2017-5422 | known affected: 1 recommended: 333 | 2026-10-17T02:20:27+00:00 | Vulnerability · Source |
| CVE-2017-5426 | suse_vex | SUSE CVE CVE-2017-5426 | known affected: 1 recommended: 333 | 2026-10-17T02:20:25+00:00 | Vulnerability · Source |
| CVE-2017-5429 | suse_vex | SUSE CVE CVE-2017-5429 | known affected: 0 known not affected: 50 recommended: 770 | 2026-10-17T02:20:24+00:00 | Vulnerability · Source |