VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-12599 | suse_vex | SUSE CVE CVE-2018-12599 | known not affected: 35 recommended: 739 | 2026-07-26T00:16:49+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-12891 | suse_vex | SUSE CVE CVE-2018-12891 | known affected: 352 known not affected: 42 recommended: 534 | 2026-07-26T00:16:42+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-14342 | suse_vex | SUSE CVE CVE-2018-14342 | known affected: 118 recommended: 1022 | 2026-07-26T00:16:23+00:00 | Vulnerability · Source |
| CVE-2018-14469 | suse_vex | SUSE CVE CVE-2018-14469 | known affected: 333 recommended: 145 | 2026-07-26T00:16:19+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-16802 | suse_vex | SUSE CVE CVE-2018-16802 | known affected: 17 known not affected: 8 recommended: 370 | 2026-07-26T00:16:11+00:00 | Vulnerability · Source |
| CVE-2018-16982 | suse_vex | SUSE CVE CVE-2018-16982 | known affected: 185 known not affected: 4 recommended: 56 | 2026-07-26T00:16:07+00:00 | Vulnerability · Source |
| CVE-2018-18455 | suse_vex | SUSE CVE CVE-2018-18455 | known not affected: 381 | 2026-07-26T00:16:04+00:00 | Vulnerability · Source |
| CVE-2018-18605 | suse_vex | SUSE CVE CVE-2018-18605 | known affected: 448 recommended: 485 | 2026-07-26T00:16:02+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-19624 | suse_vex | SUSE CVE CVE-2018-19624 | known affected: 111 known not affected: 37 recommended: 922 | 2026-07-26T00:15:58+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-1000135 | suse_vex | SUSE CVE CVE-2018-1000135 | known affected: 394 known not affected: 257 recommended: 345 | 2026-07-26T00:15:49+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-3860 | suse_vex | SUSE CVE CVE-2019-3860 | known affected: 456 known not affected: 76 recommended: 272 | 2026-07-26T00:15:38+00:00 | Vulnerability · Source |
| CVE-2019-6476 | suse_vex | SUSE CVE CVE-2019-6476 | known affected: 346 known not affected: 779 recommended: 384 | 2026-07-26T00:15:36+00:00 | Vulnerability · Source |
| CVE-2019-7221 | suse_vex | SUSE CVE CVE-2019-7221 | known not affected: 168 recommended: 818 | 2026-07-26T00:15:34+00:00 | Vulnerability · Source |
| CVE-2019-8536 | suse_vex | SUSE CVE CVE-2019-8536 | known affected: 154 known not affected: 82 recommended: 1095 | 2026-07-26T00:15:31+00:00 | Vulnerability · Source |
| CVE-2019-8595 | suse_vex | SUSE CVE CVE-2019-8595 | known affected: 153 known not affected: 82 recommended: 1136 | 2026-07-26T00:15:29+00:00 | Vulnerability · Source |
| CVE-2019-8683 | suse_vex | SUSE CVE CVE-2019-8683 | known affected: 107 known not affected: 82 recommended: 1022 | 2026-07-26T00:15:26+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-11599 | suse_vex | SUSE CVE CVE-2019-11599 | known affected: 129 known not affected: 138 recommended: 835 | 2026-07-26T00:15:07+00:00 | Vulnerability · Source |
| CVE-2019-11759 | suse_vex | SUSE CVE CVE-2019-11759 | known not affected: 160 recommended: 587 | 2026-07-26T00:15:01+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-16254 | suse_vex | SUSE CVE CVE-2019-16254 | known affected: 322 known not affected: 60 recommended: 489 | 2026-07-26T00:14:44+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-2019-19227 | suse_vex | SUSE CVE CVE-2019-19227 | known affected: 100 known not affected: 61 recommended: 634 | 2026-07-26T00:14:34+00:00 | Vulnerability · Source |
| CVE-2019-19602 | suse_vex | SUSE CVE CVE-2019-19602 | known affected: 334 known not affected: 392 recommended: 801 | 2026-07-26T00:14:32+00:00 | Vulnerability · Source |
| CVE-2019-20908 | suse_vex | SUSE CVE CVE-2019-20908 | known affected: 96 known not affected: 193 recommended: 462 | 2026-07-26T00:14:29+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-2773 | suse_vex | SUSE CVE CVE-2020-2773 | known affected: 454 recommended: 773 | 2026-07-26T00:14:22+00:00 | Vulnerability · Source |
| CVE-2020-6822 | suse_vex | SUSE CVE CVE-2020-6822 | recommended: 380 | 2026-07-26T00:14:19+00:00 | Vulnerability · Source |
| CVE-2020-8013 | suse_vex | SUSE CVE CVE-2020-8013 | known affected: 326 known not affected: 21 recommended: 236 | 2026-07-26T00:14:16+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-8648 | suse_vex | SUSE CVE CVE-2020-8648 | known affected: 444 known not affected: 69 recommended: 1537 | 2026-07-26T00:14:10+00:00 | Vulnerability · Source |
| CVE-2020-8696 | suse_vex | SUSE CVE CVE-2020-8696 | known affected: 8 recommended: 100 | 2026-07-26T00:14:08+00:00 | Vulnerability · Source |
| CVE-2020-8835 | suse_vex | SUSE CVE CVE-2020-8835 | known affected: 320 known not affected: 397 recommended: 781 | 2026-07-26T00:14:06+00:00 | Vulnerability · Source |