VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288944 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2018-20783 | suse_vex | SUSE CVE CVE-2018-20783 | known affected: 550 known not affected: 853 recommended: 3916 | 2026-08-04T00:05:14+00:00 | Vulnerability · Source |
| CVE-2019-3813 | suse_vex | SUSE CVE CVE-2019-3813 | known affected: 28 known not affected: 174 recommended: 134 | 2026-08-04T00:05:08+00:00 | Vulnerability · Source |
| CVE-2019-6974 | suse_vex | SUSE CVE CVE-2019-6974 | known affected: 66 known not affected: 221 recommended: 806 | 2026-08-04T00:05:04+00:00 | Vulnerability · Source |
| CVE-2019-8673 | suse_vex | SUSE CVE CVE-2019-8673 | known affected: 107 known not affected: 82 recommended: 1124 | 2026-08-04T00:05:01+00:00 | Vulnerability · Source |
| CVE-2019-8819 | suse_vex | SUSE CVE CVE-2019-8819 | known not affected: 10 recommended: 1090 | 2026-08-04T00:04:58+00:00 | Vulnerability · Source |
| CVE-2019-10222 | suse_vex | SUSE CVE CVE-2019-10222 | known affected: 85 known not affected: 312 recommended: 968 | 2026-08-04T00:04:53+00:00 | Vulnerability · Source |
| CVE-2019-11719 | suse_vex | SUSE CVE CVE-2019-11719 | known affected: 21 recommended: 1459 | 2026-08-04T00:04:49+00:00 | Vulnerability · Source |
| CVE-2019-12209 | suse_vex | SUSE CVE CVE-2019-12209 | recommended: 182 | 2026-08-04T00:04:46+00:00 | Vulnerability · Source |
| CVE-2019-12210 | suse_vex | SUSE CVE CVE-2019-12210 | recommended: 182 | 2026-08-04T00:04:44+00:00 | Vulnerability · Source |
| CVE-2019-12519 | suse_vex | SUSE CVE CVE-2019-12519 | known affected: 394 recommended: 76 | 2026-08-04T00:04:42+00:00 | Vulnerability · Source |
| CVE-2019-12983 | suse_vex | SUSE CVE CVE-2019-12983 | known affected: 89 known not affected: 122 | 2026-08-04T00:04:39+00:00 | Vulnerability · Source |
| CVE-2019-12984 | suse_vex | SUSE CVE CVE-2019-12984 | known affected: 48 known not affected: 359 recommended: 14 | 2026-08-04T00:04:37+00:00 | Vulnerability · Source |
| CVE-2019-14368 | suse_vex | SUSE CVE CVE-2019-14368 | known not affected: 76 | 2026-08-04T00:04:34+00:00 | Vulnerability · Source |
| CVE-2019-14560 | suse_vex | SUSE CVE CVE-2019-14560 | known affected: 9 known not affected: 16 recommended: 200 | 2026-08-04T00:04:32+00:00 | Vulnerability · Source |
| CVE-2019-14834 | suse_vex | SUSE CVE CVE-2019-14834 | known affected: 2 known not affected: 1 recommended: 96 | 2026-08-04T00:04:30+00:00 | Vulnerability · Source |
| CVE-2019-15219 | suse_vex | SUSE CVE CVE-2019-15219 | known affected: 133 known not affected: 84 recommended: 914 | 2026-08-04T00:04:27+00:00 | Vulnerability · Source |
| CVE-2019-17371 | suse_vex | SUSE CVE CVE-2019-17371 | known affected: 6 known not affected: 270 | 2026-08-04T00:04:21+00:00 | Vulnerability · Source |
| CVE-2019-17498 | suse_vex | SUSE CVE CVE-2019-17498 | known affected: 450 recommended: 296 | 2026-08-04T00:04:19+00:00 | Vulnerability · Source |
| CVE-2020-0432 | suse_vex | SUSE CVE CVE-2020-0432 | known affected: 449 known not affected: 56 recommended: 1519 | 2026-08-04T00:04:08+00:00 | Vulnerability · Source |
| CVE-2020-6096 | suse_vex | SUSE CVE CVE-2020-6096 | known not affected: 384 recommended: 216 | 2026-08-04T00:04:04+00:00 | Vulnerability · Source |
| CVE-2020-8623 | suse_vex | SUSE CVE CVE-2020-8623 | known affected: 320 known not affected: 150 recommended: 995 | 2026-08-04T00:03:58+00:00 | Vulnerability · Source |
| CVE-2020-10700 | suse_vex | SUSE CVE CVE-2020-10700 | known affected: 320 known not affected: 1677 recommended: 2493 | 2026-08-04T00:03:55+00:00 | Vulnerability · Source |
| CVE-2020-12362 | suse_vex | SUSE CVE CVE-2020-12362 | known affected: 304 known not affected: 359 recommended: 948 | 2026-08-04T00:03:50+00:00 | Vulnerability · Source |
| CVE-2020-14339 | suse_vex | SUSE CVE CVE-2020-14339 | known affected: 555 known not affected: 473 recommended: 1554 | 2026-08-04T00:03:45+00:00 | Vulnerability · Source |
| CVE-2020-14387 | suse_vex | SUSE CVE CVE-2020-14387 | known not affected: 48 recommended: 50 | 2026-08-04T00:03:42+00:00 | Vulnerability · Source |
| CVE-2020-19131 | suse_vex | SUSE CVE CVE-2020-19131 | known affected: 395 known not affected: 15 recommended: 278 | 2026-08-04T00:03:38+00:00 | Vulnerability · Source |
| CVE-2020-24165 | suse_vex | SUSE CVE CVE-2020-24165 | known not affected: 895 | 2026-08-04T00:03:34+00:00 | Vulnerability · Source |
| CVE-2020-25643 | suse_vex | SUSE CVE CVE-2020-25643 | known affected: 320 known not affected: 112 recommended: 1621 | 2026-08-04T00:03:31+00:00 | Vulnerability · Source |
| CVE-2020-25674 | suse_vex | SUSE CVE CVE-2020-25674 | known not affected: 4 recommended: 762 | 2026-08-04T00:03:28+00:00 | Vulnerability · Source |
| CVE-2020-27067 | suse_vex | SUSE CVE CVE-2020-27067 | known not affected: 353 | 2026-08-04T00:03:25+00:00 | Vulnerability · Source |
| CVE-2020-27619 | suse_vex | SUSE CVE CVE-2020-27619 | known affected: 299 known not affected: 235 recommended: 899 | 2026-08-04T00:03:22+00:00 | Vulnerability · Source |