VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294144 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-11656 | suse_vex | SUSE CVE CVE-2018-11656 | known not affected: 364 recommended: 100 | 2026-07-26T00:17:26+00:00 | Vulnerability · Source |
| CVE-2018-12179 | suse_vex | SUSE CVE CVE-2018-12179 | known not affected: 47 | 2026-07-26T00:17:17+00:00 | Vulnerability · Source |
| CVE-2018-12183 | suse_vex | SUSE CVE CVE-2018-12183 | known not affected: 47 | 2026-07-26T00:17:16+00:00 | Vulnerability · Source |
| CVE-2018-12293 | suse_vex | SUSE CVE CVE-2018-12293 | known affected: 162 known not affected: 82 | 2026-07-26T00:17:10+00:00 | Vulnerability · Source |
| CVE-2018-12294 | suse_vex | SUSE CVE CVE-2018-12294 | known affected: 162 known not affected: 82 | 2026-07-26T00:17:09+00:00 | Vulnerability · Source |
| CVE-2018-12437 | suse_vex | SUSE CVE CVE-2018-12437 | known not affected: 55 recommended: 4 | 2026-07-26T00:16:53+00:00 | Vulnerability · Source |
| CVE-2018-12886 | suse_vex | SUSE CVE CVE-2018-12886 | known not affected: 1106 | 2026-07-26T00:16:44+00:00 | Vulnerability · Source |
| CVE-2018-12930 | suse_vex | SUSE CVE CVE-2018-12930 | known not affected: 563 | 2026-07-26T00:16:40+00:00 | Vulnerability · Source |
| CVE-2018-12938 | suse_vex | SUSE CVE CVE-2018-12938 | known affected: 61 | 2026-07-26T00:16:38+00:00 | Vulnerability · Source |
| CVE-2018-13065 | suse_vex | SUSE CVE CVE-2018-13065 | known not affected: 25 | 2026-07-26T00:16:36+00:00 | Vulnerability · Source |
| CVE-2018-13440 | suse_vex | SUSE CVE CVE-2018-13440 | known affected: 1 known not affected: 4 recommended: 179 | 2026-07-26T00:16:34+00:00 | Vulnerability · Source |
| CVE-2018-13796 | suse_vex | SUSE CVE CVE-2018-13796 | known affected: 16 recommended: 28 | 2026-07-26T00:16:30+00:00 | Vulnerability · Source |
| CVE-2018-14338 | suse_vex | SUSE CVE CVE-2018-14338 | known not affected: 61 recommended: 8 | 2026-07-26T00:16:27+00:00 | Vulnerability · Source |
| CVE-2018-15518 | suse_vex | SUSE CVE CVE-2018-15518 | known affected: 211 recommended: 1441 | 2026-07-26T00:16:16+00:00 | Vulnerability · Source |
| CVE-2018-16648 | suse_vex | SUSE CVE CVE-2018-16648 | known not affected: 381 recommended: 2 | 2026-07-26T00:16:13+00:00 | Vulnerability · Source |
| CVE-2018-19107 | suse_vex | SUSE CVE CVE-2018-19107 | known not affected: 76 recommended: 12 | 2026-07-26T00:16:00+00:00 | Vulnerability · Source |
| CVE-2018-19871 | suse_vex | SUSE CVE CVE-2018-19871 | known affected: 28 known not affected: 121 recommended: 315 | 2026-07-26T00:15:54+00:00 | Vulnerability · Source |
| CVE-2018-1000204 | suse_vex | SUSE CVE CVE-2018-1000204 | known affected: 42 known not affected: 104 recommended: 672 | 2026-07-26T00:15:47+00:00 | Vulnerability · Source |
| CVE-2019-2766 | suse_vex | SUSE CVE CVE-2019-2766 | known affected: 500 known not affected: 9 recommended: 1094 | 2026-07-26T00:15:43+00:00 | Vulnerability · Source |
| CVE-2019-8684 | suse_vex | SUSE CVE CVE-2019-8684 | known affected: 107 known not affected: 82 recommended: 1096 | 2026-07-26T00:15:24+00:00 | Vulnerability · Source |
| CVE-2019-8956 | suse_vex | SUSE CVE CVE-2019-8956 | known not affected: 495 | 2026-07-26T00:15:18+00:00 | Vulnerability · Source |
| CVE-2019-13289 | suse_vex | SUSE CVE CVE-2019-13289 | known not affected: 466 | 2026-07-26T00:14:56+00:00 | Vulnerability · Source |
| CVE-2019-14370 | suse_vex | SUSE CVE CVE-2019-14370 | known not affected: 88 | 2026-07-26T00:14:54+00:00 | Vulnerability · Source |
| CVE-2019-15504 | suse_vex | SUSE CVE CVE-2019-15504 | known affected: 320 known not affected: 459 recommended: 787 | 2026-07-26T00:14:46+00:00 | Vulnerability · Source |
| CVE-2019-19056 | suse_vex | SUSE CVE CVE-2019-19056 | known affected: 428 known not affected: 199 recommended: 1354 | 2026-07-26T00:14:39+00:00 | Vulnerability · Source |
| CVE-2019-19070 | suse_vex | SUSE CVE CVE-2019-19070 | known affected: 320 known not affected: 430 recommended: 781 | 2026-07-26T00:14:36+00:00 | Vulnerability · Source |
| CVE-2020-0569 | suse_vex | SUSE CVE CVE-2020-0569 | known affected: 426 known not affected: 784 recommended: 2238 | 2026-07-26T00:14:25+00:00 | Vulnerability · Source |
| CVE-2020-8432 | suse_vex | SUSE CVE CVE-2020-8432 | known affected: 19 known not affected: 4 recommended: 197 | 2026-07-26T00:14:14+00:00 | Vulnerability · Source |
| CVE-2020-9805 | suse_vex | SUSE CVE CVE-2020-9805 | known affected: 97 recommended: 1240 | 2026-07-26T00:14:04+00:00 | Vulnerability · Source |
| CVE-2020-10736 | suse_vex | SUSE CVE CVE-2020-10736 | known not affected: 759 recommended: 791 | 2026-07-26T00:14:01+00:00 | Vulnerability · Source |
| CVE-2020-10769 | suse_vex | SUSE CVE CVE-2020-10769 | known affected: 88 known not affected: 206 recommended: 618 | 2026-07-26T00:13:59+00:00 | Vulnerability · Source |
| CVE-2020-16297 | suse_vex | SUSE CVE CVE-2020-16297 | known not affected: 172 recommended: 8 | 2026-07-26T00:13:41+00:00 | Vulnerability · Source |
| CVE-2020-25084 | suse_vex | SUSE CVE CVE-2020-25084 | known affected: 388 known not affected: 2 recommended: 850 | 2026-07-26T00:13:31+00:00 | Vulnerability · Source |
| CVE-2020-25603 | suse_vex | SUSE CVE CVE-2020-25603 | known affected: 431 known not affected: 2 recommended: 517 | 2026-07-26T00:13:29+00:00 | Vulnerability · Source |
| CVE-2020-25667 | suse_vex | SUSE CVE CVE-2020-25667 | known not affected: 338 | 2026-07-26T00:13:27+00:00 | Vulnerability · Source |
| CVE-2020-36786 | suse_vex | SUSE CVE CVE-2020-36786 | known not affected: 275 | 2026-07-26T00:13:13+00:00 | Vulnerability · Source |
| CVE-2021-0089 | suse_vex | SUSE CVE CVE-2021-0089 | known affected: 312 known not affected: 46 recommended: 503 | 2026-07-26T00:13:07+00:00 | Vulnerability · Source |
| CVE-2021-3927 | suse_vex | SUSE CVE CVE-2021-3927 | known affected: 352 recommended: 384 | 2026-07-26T00:12:49+00:00 | Vulnerability · Source |
| CVE-2021-3947 | suse_vex | SUSE CVE CVE-2021-3947 | known not affected: 1077 | 2026-07-26T00:12:47+00:00 | Vulnerability · Source |
| CVE-2021-23983 | suse_vex | SUSE CVE CVE-2021-23983 | recommended: 9 | 2026-07-26T00:12:33+00:00 | Vulnerability · Source |
| CVE-2021-47010 | suse_vex | SUSE CVE CVE-2021-47010 | known not affected: 292 | 2026-07-26T00:12:05+00:00 | Vulnerability · Source |
| CVE-2021-47241 | suse_vex | SUSE CVE CVE-2021-47241 | known affected: 388 known not affected: 294 recommended: 91 | 2026-07-26T00:11:54+00:00 | Vulnerability · Source |
| CVE-2022-23131 | suse_vex | SUSE CVE CVE-2022-23131 | known not affected: 37 | 2026-07-26T00:10:58+00:00 | Vulnerability · Source |
| CVE-2022-28391 | suse_vex | SUSE CVE CVE-2022-28391 | known affected: 5 known not affected: 63 | 2026-07-26T00:10:47+00:00 | Vulnerability · Source |
| CVE-2022-38349 | suse_vex | SUSE CVE CVE-2022-38349 | known affected: 80 known not affected: 5 recommended: 273 | 2026-07-26T00:10:31+00:00 | Vulnerability · Source |
| CVE-2022-47521 | suse_vex | SUSE CVE CVE-2022-47521 | known not affected: 362 | 2026-07-26T00:10:17+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 310 | 2026-07-26T00:10:01+00:00 | Vulnerability · Source |
| CVE-2022-49536 | suse_vex | SUSE CVE CVE-2022-49536 | known affected: 385 known not affected: 193 recommended: 361 | 2026-07-26T00:09:12+00:00 | Vulnerability · Source |
| CVE-2022-50278 | suse_vex | SUSE CVE CVE-2022-50278 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-26T00:08:23+00:00 | Vulnerability · Source |
| CVE-2023-25750 | suse_vex | SUSE CVE CVE-2023-25750 | known affected: 1 recommended: 214 | 2026-07-26T00:07:18+00:00 | Vulnerability · Source |