VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288925 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9239 | suse_vex | SUSE CVE CVE-2017-9239 | known affected: 21 recommended: 164 | 2026-08-04T00:07:31+00:00 | Vulnerability · Source |
| CVE-2017-9747 | suse_vex | SUSE CVE CVE-2017-9747 | known affected: 394 known not affected: 345 recommended: 340 | 2026-08-04T00:07:28+00:00 | Vulnerability · Source |
| CVE-2017-9751 | suse_vex | SUSE CVE CVE-2017-9751 | known affected: 8 known not affected: 42 | 2026-08-04T00:07:26+00:00 | Vulnerability · Source |
| CVE-2017-10662 | suse_vex | SUSE CVE CVE-2017-10662 | known not affected: 28 | 2026-08-04T00:07:22+00:00 | Vulnerability · Source |
| CVE-2017-10922 | suse_vex | SUSE CVE CVE-2017-10922 | recommended: 35 | 2026-08-04T00:07:19+00:00 | Vulnerability · Source |
| CVE-2017-11536 | suse_vex | SUSE CVE CVE-2017-11536 | known affected: 10 known not affected: 144 | 2026-08-04T00:07:16+00:00 | Vulnerability · Source |
| CVE-2017-11600 | suse_vex | SUSE CVE CVE-2017-11600 | known affected: 46 known not affected: 284 recommended: 657 | 2026-08-04T00:07:13+00:00 | Vulnerability · Source |
| CVE-2017-11641 | suse_vex | SUSE CVE CVE-2017-11641 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-04T00:07:11+00:00 | Vulnerability · Source |
| CVE-2017-12188 | suse_vex | SUSE CVE CVE-2017-12188 | known not affected: 357 recommended: 26 | 2026-08-04T00:07:09+00:00 | Vulnerability · Source |
| CVE-2017-12193 | suse_vex | SUSE CVE CVE-2017-12193 | known not affected: 182 recommended: 499 | 2026-08-04T00:07:07+00:00 | Vulnerability · Source |
| CVE-2017-12430 | suse_vex | SUSE CVE CVE-2017-12430 | known affected: 94 recommended: 186 | 2026-08-04T00:07:05+00:00 | Vulnerability · Source |
| CVE-2017-12940 | suse_vex | SUSE CVE CVE-2017-12940 | known affected: 5 recommended: 28 | 2026-08-04T00:07:03+00:00 | Vulnerability · Source |
| CVE-2017-12941 | suse_vex | SUSE CVE CVE-2017-12941 | known affected: 5 recommended: 28 | 2026-08-04T00:07:02+00:00 | Vulnerability · Source |
| CVE-2017-13686 | suse_vex | SUSE CVE CVE-2017-13686 | known not affected: 28 | 2026-08-04T00:06:59+00:00 | Vulnerability · Source |
| CVE-2017-13749 | suse_vex | SUSE CVE CVE-2017-13749 | known affected: 6 known not affected: 56 | 2026-08-04T00:06:57+00:00 | Vulnerability · Source |
| CVE-2017-13751 | suse_vex | SUSE CVE CVE-2017-13751 | known affected: 6 known not affected: 56 recommended: 24 | 2026-08-04T00:06:55+00:00 | Vulnerability · Source |
| CVE-2017-14041 | suse_vex | SUSE CVE CVE-2017-14041 | known not affected: 65 recommended: 205 | 2026-08-04T00:06:53+00:00 | Vulnerability · Source |
| CVE-2017-14314 | suse_vex | SUSE CVE CVE-2017-14314 | known affected: 94 recommended: 186 | 2026-08-04T00:06:50+00:00 | Vulnerability · Source |
| CVE-2017-16530 | suse_vex | SUSE CVE CVE-2017-16530 | known affected: 14 known not affected: 596 | 2026-08-04T00:06:46+00:00 | Vulnerability · Source |
| CVE-2017-16545 | suse_vex | SUSE CVE CVE-2017-16545 | known affected: 94 recommended: 186 | 2026-08-04T00:06:43+00:00 | Vulnerability · Source |
| CVE-2017-16649 | suse_vex | SUSE CVE CVE-2017-16649 | known not affected: 519 recommended: 504 | 2026-08-04T00:06:41+00:00 | Vulnerability · Source |
| CVE-2017-17381 | suse_vex | SUSE CVE CVE-2017-17381 | known affected: 69 known not affected: 5 recommended: 218 | 2026-08-04T00:06:38+00:00 | Vulnerability · Source |
| CVE-2017-17450 | suse_vex | SUSE CVE CVE-2017-17450 | known affected: 38 known not affected: 558 recommended: 622 | 2026-08-04T00:06:36+00:00 | Vulnerability · Source |
| CVE-2017-17484 | suse_vex | SUSE CVE CVE-2017-17484 | recommended: 136 | 2026-08-04T00:06:34+00:00 | Vulnerability · Source |
| CVE-2017-17688 | suse_vex | SUSE CVE CVE-2017-17688 | known not affected: 220 recommended: 23 | 2026-08-04T00:06:31+00:00 | Vulnerability · Source |
| CVE-2017-17935 | suse_vex | SUSE CVE CVE-2017-17935 | known affected: 86 recommended: 145 | 2026-08-04T00:06:27+00:00 | Vulnerability · Source |
| CVE-2017-18208 | suse_vex | SUSE CVE CVE-2017-18208 | known affected: 36 known not affected: 393 recommended: 622 | 2026-08-04T00:06:25+00:00 | Vulnerability · Source |
| CVE-2017-18594 | suse_vex | SUSE CVE CVE-2017-18594 | known not affected: 22 recommended: 92 | 2026-08-04T00:06:22+00:00 | Vulnerability · Source |
| CVE-2018-0734 | suse_vex | SUSE CVE CVE-2018-0734 | known affected: 540 known not affected: 297 recommended: 1088 | 2026-08-04T00:06:18+00:00 | Vulnerability · Source |
| CVE-2018-1092 | suse_vex | SUSE CVE CVE-2018-1092 | known affected: 40 known not affected: 279 recommended: 255 | 2026-08-04T00:06:15+00:00 | Vulnerability · Source |
| CVE-2018-2638 | suse_vex | SUSE CVE CVE-2018-2638 | known affected: 12 known not affected: 279 recommended: 232 | 2026-08-04T00:06:11+00:00 | Vulnerability · Source |
| CVE-2018-3691 | suse_vex | SUSE CVE CVE-2018-3691 | known affected: 110 known not affected: 212 | 2026-08-04T00:06:05+00:00 | Vulnerability · Source |
| CVE-2018-4209 | suse_vex | SUSE CVE CVE-2018-4209 | known affected: 108 known not affected: 82 recommended: 959 | 2026-08-04T00:06:01+00:00 | Vulnerability · Source |
| CVE-2018-4273 | suse_vex | SUSE CVE CVE-2018-4273 | known affected: 108 known not affected: 82 recommended: 957 | 2026-08-04T00:05:58+00:00 | Vulnerability · Source |
| CVE-2018-5153 | suse_vex | SUSE CVE CVE-2018-5153 | known affected: 26 recommended: 83 | 2026-08-04T00:05:55+00:00 | Vulnerability · Source |
| CVE-2018-5248 | suse_vex | SUSE CVE CVE-2018-5248 | known affected: 10 known not affected: 130 | 2026-08-04T00:05:53+00:00 | Vulnerability · Source |
| CVE-2018-5950 | suse_vex | SUSE CVE CVE-2018-5950 | known affected: 16 recommended: 27 | 2026-08-04T00:05:50+00:00 | Vulnerability · Source |
| CVE-2018-6079 | suse_vex | SUSE CVE CVE-2018-6079 | recommended: 10 | 2026-08-04T00:05:48+00:00 | Vulnerability · Source |
| CVE-2018-6553 | suse_vex | SUSE CVE CVE-2018-6553 | known not affected: 123 | 2026-08-04T00:05:46+00:00 | Vulnerability · Source |
| CVE-2018-7184 | suse_vex | SUSE CVE CVE-2018-7184 | known affected: 27 known not affected: 20 recommended: 100 | 2026-08-04T00:05:42+00:00 | Vulnerability · Source |
| CVE-2018-7320 | suse_vex | SUSE CVE CVE-2018-7320 | known affected: 1 known not affected: 115 recommended: 589 | 2026-08-04T00:05:40+00:00 | Vulnerability · Source |
| CVE-2018-7336 | suse_vex | SUSE CVE CVE-2018-7336 | known affected: 1 known not affected: 115 recommended: 589 | 2026-08-04T00:05:37+00:00 | Vulnerability · Source |
| CVE-2018-8019 | suse_vex | SUSE CVE CVE-2018-8019 | known not affected: 75 recommended: 16 | 2026-08-04T00:05:35+00:00 | Vulnerability · Source |
| CVE-2018-9265 | suse_vex | SUSE CVE CVE-2018-9265 | known affected: 89 known not affected: 115 recommended: 555 | 2026-08-04T00:05:34+00:00 | Vulnerability · Source |
| CVE-2018-11410 | suse_vex | SUSE CVE CVE-2018-11410 | known not affected: 73 recommended: 255 | 2026-08-04T00:05:31+00:00 | Vulnerability · Source |
| CVE-2018-14434 | suse_vex | SUSE CVE CVE-2018-14434 | known not affected: 14 recommended: 755 | 2026-08-04T00:05:28+00:00 | Vulnerability · Source |
| CVE-2018-14722 | suse_vex | SUSE CVE CVE-2018-14722 | known not affected: 78 recommended: 64 | 2026-08-04T00:05:26+00:00 | Vulnerability · Source |
| CVE-2018-14880 | suse_vex | SUSE CVE CVE-2018-14880 | known affected: 333 recommended: 141 | 2026-08-04T00:05:24+00:00 | Vulnerability · Source |
| CVE-2018-16419 | suse_vex | SUSE CVE CVE-2018-16419 | known affected: 16 known not affected: 19 recommended: 106 | 2026-08-04T00:05:21+00:00 | Vulnerability · Source |
| CVE-2018-17098 | suse_vex | SUSE CVE CVE-2018-17098 | known affected: 16 recommended: 189 | 2026-08-04T00:05:19+00:00 | Vulnerability · Source |