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-14463 | suse_vex | SUSE CVE CVE-2018-14463 | known affected: 333 recommended: 145 | 2026-07-26T23:43:37+00:00 | Vulnerability · Source |
| CVE-2018-15469 | suse_vex | SUSE CVE CVE-2018-15469 | known affected: 320 known not affected: 97 recommended: 425 | 2026-07-26T23:43:35+00:00 | Vulnerability · Source |
| CVE-2018-15686 | suse_vex | SUSE CVE CVE-2018-15686 | known affected: 320 recommended: 1300 | 2026-07-26T23:43:33+00:00 | Vulnerability · Source |
| CVE-2018-19824 | suse_vex | SUSE CVE CVE-2018-19824 | known affected: 74 known not affected: 235 recommended: 788 | 2026-07-26T23:43:28+00:00 | Vulnerability · Source |
| CVE-2018-20030 | suse_vex | SUSE CVE CVE-2018-20030 | known affected: 27 recommended: 208 | 2026-07-26T23:43:26+00:00 | Vulnerability · Source |
| CVE-2019-2968 | suse_vex | SUSE CVE CVE-2019-2968 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-26T23:43:20+00:00 | Vulnerability · Source |
| CVE-2019-4473 | suse_vex | SUSE CVE CVE-2019-4473 | known affected: 88 known not affected: 9 recommended: 434 | 2026-07-26T23:43:15+00:00 | Vulnerability · Source |
| CVE-2019-5736 | suse_vex | SUSE CVE CVE-2019-5736 | known affected: 347 known not affected: 179 recommended: 1109 | 2026-07-26T23:43:13+00:00 | Vulnerability · Source |
| CVE-2019-8597 | suse_vex | SUSE CVE CVE-2019-8597 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-26T23:43:10+00:00 | Vulnerability · Source |
| CVE-2019-9162 | suse_vex | SUSE CVE CVE-2019-9162 | known not affected: 495 | 2026-07-26T23:43:08+00:00 | Vulnerability · Source |
| CVE-2019-9444 | suse_vex | SUSE CVE CVE-2019-9444 | known not affected: 52 | 2026-07-26T23:43:06+00:00 | Vulnerability · Source |
| CVE-2019-9446 | suse_vex | SUSE CVE CVE-2019-9446 | known not affected: 215 | 2026-07-26T23:43:05+00:00 | Vulnerability · Source |
| CVE-2019-9810 | suse_vex | SUSE CVE CVE-2019-9810 | known affected: 21 recommended: 420 | 2026-07-26T23:43:03+00:00 | Vulnerability · Source |
| CVE-2019-10072 | suse_vex | SUSE CVE CVE-2019-10072 | known affected: 484 known not affected: 129 recommended: 215 | 2026-07-26T23:43:01+00:00 | Vulnerability · Source |
| CVE-2019-11709 | suse_vex | SUSE CVE CVE-2019-11709 | known affected: 21 recommended: 1422 | 2026-07-26T23:42:56+00:00 | Vulnerability · Source |
| CVE-2019-12083 | suse_vex | SUSE CVE CVE-2019-12083 | known not affected: 44 recommended: 520 | 2026-07-26T23:42:54+00:00 | Vulnerability · Source |
| CVE-2019-12447 | suse_vex | SUSE CVE CVE-2019-12447 | known not affected: 150 recommended: 503 | 2026-07-26T23:42:51+00:00 | Vulnerability · Source |
| CVE-2019-12454 | suse_vex | SUSE CVE CVE-2019-12454 | known not affected: 332 | 2026-07-26T23:42:50+00:00 | Vulnerability · Source |
| CVE-2019-13109 | suse_vex | SUSE CVE CVE-2019-13109 | known affected: 32 known not affected: 55 recommended: 92 | 2026-07-26T23:42:48+00:00 | Vulnerability · Source |
| CVE-2019-13112 | suse_vex | SUSE CVE CVE-2019-13112 | known affected: 7 known not affected: 83 recommended: 27 | 2026-07-26T23:42:47+00:00 | Vulnerability · Source |
| CVE-2019-13309 | suse_vex | SUSE CVE CVE-2019-13309 | known affected: 45 known not affected: 371 recommended: 622 | 2026-07-26T23:42:45+00:00 | Vulnerability · Source |
| CVE-2019-14287 | suse_vex | SUSE CVE CVE-2019-14287 | known affected: 334 known not affected: 3 recommended: 340 | 2026-07-26T23:42:43+00:00 | Vulnerability · Source |
| CVE-2019-15118 | suse_vex | SUSE CVE CVE-2019-15118 | known not affected: 35 recommended: 914 | 2026-07-26T23:42:39+00:00 | Vulnerability · Source |
| CVE-2019-15163 | suse_vex | SUSE CVE CVE-2019-15163 | known affected: 12 known not affected: 8 recommended: 77 | 2026-07-26T23:42:38+00:00 | Vulnerability · Source |
| CVE-2019-15845 | suse_vex | SUSE CVE CVE-2019-15845 | known affected: 322 known not affected: 60 recommended: 489 | 2026-07-26T23:42:34+00:00 | Vulnerability · Source |
| CVE-2019-17013 | suse_vex | SUSE CVE CVE-2019-17013 | known not affected: 108 recommended: 9 | 2026-07-26T23:42:32+00:00 | Vulnerability · Source |
| CVE-2019-17567 | suse_vex | SUSE CVE CVE-2019-17567 | known affected: 18 known not affected: 218 | 2026-07-26T23:42:30+00:00 | Vulnerability · Source |
| CVE-2019-18424 | suse_vex | SUSE CVE CVE-2019-18424 | known not affected: 169 recommended: 257 | 2026-07-26T23:42:29+00:00 | Vulnerability · Source |
| CVE-2019-18807 | suse_vex | SUSE CVE CVE-2019-18807 | known not affected: 223 | 2026-07-26T23:42:27+00:00 | Vulnerability · Source |
| CVE-2019-19045 | suse_vex | SUSE CVE CVE-2019-19045 | known affected: 320 known not affected: 347 recommended: 1302 | 2026-07-26T23:42:25+00:00 | Vulnerability · Source |
| CVE-2019-19046 | suse_vex | SUSE CVE CVE-2019-19046 | known affected: 371 known not affected: 297 recommended: 1177 | 2026-07-26T23:42:24+00:00 | Vulnerability · Source |
| CVE-2019-19060 | suse_vex | SUSE CVE CVE-2019-19060 | known affected: 428 known not affected: 215 recommended: 1334 | 2026-07-26T23:42:22+00:00 | Vulnerability · Source |
| CVE-2019-19076 | suse_vex | SUSE CVE CVE-2019-19076 | known not affected: 365 | 2026-07-26T23:42:21+00:00 | Vulnerability · Source |
| CVE-2019-19083 | suse_vex | SUSE CVE CVE-2019-19083 | known affected: 371 known not affected: 299 recommended: 1322 | 2026-07-26T23:42:19+00:00 | Vulnerability · Source |
| CVE-2019-19252 | suse_vex | SUSE CVE CVE-2019-19252 | known affected: 320 known not affected: 358 recommended: 787 | 2026-07-26T23:42:17+00:00 | Vulnerability · Source |
| CVE-2019-19525 | suse_vex | SUSE CVE CVE-2019-19525 | known affected: 452 known not affected: 79 recommended: 1489 | 2026-07-26T23:42:16+00:00 | Vulnerability · Source |
| CVE-2019-19534 | suse_vex | SUSE CVE CVE-2019-19534 | known affected: 132 known not affected: 81 recommended: 1448 | 2026-07-26T23:42:14+00:00 | Vulnerability · Source |
| CVE-2019-19922 | suse_vex | SUSE CVE CVE-2019-19922 | known affected: 320 known not affected: 320 recommended: 801 | 2026-07-26T23:42:12+00:00 | Vulnerability · Source |
| CVE-2019-20503 | suse_vex | SUSE CVE CVE-2019-20503 | recommended: 393 | 2026-07-26T23:42:10+00:00 | Vulnerability · Source |
| CVE-2019-20795 | suse_vex | SUSE CVE CVE-2019-20795 | known affected: 398 known not affected: 168 recommended: 6 | 2026-07-26T23:42:09+00:00 | Vulnerability · Source |
| CVE-2020-0431 | suse_vex | SUSE CVE CVE-2020-0431 | known affected: 320 known not affected: 112 recommended: 1706 | 2026-07-26T23:42:05+00:00 | Vulnerability · Source |
| CVE-2020-1752 | suse_vex | SUSE CVE CVE-2020-1752 | known affected: 320 known not affected: 174 recommended: 1420 | 2026-07-26T23:42:03+00:00 | Vulnerability · Source |
| CVE-2020-3865 | suse_vex | SUSE CVE CVE-2020-3865 | known affected: 46 known not affected: 264 recommended: 1090 | 2026-07-26T23:42:00+00:00 | Vulnerability · Source |
| CVE-2020-3898 | suse_vex | SUSE CVE CVE-2020-3898 | known affected: 412 recommended: 913 | 2026-07-26T23:41:58+00:00 | Vulnerability · Source |
| CVE-2020-6514 | suse_vex | SUSE CVE CVE-2020-6514 | known affected: 24 recommended: 536 | 2026-07-26T23:41:56+00:00 | Vulnerability · Source |
| CVE-2020-8517 | suse_vex | SUSE CVE CVE-2020-8517 | known affected: 395 recommended: 70 | 2026-07-26T23:41:51+00:00 | Vulnerability · Source |
| CVE-2020-12108 | suse_vex | SUSE CVE CVE-2020-12108 | known affected: 9 recommended: 32 | 2026-07-26T23:41:44+00:00 | Vulnerability · Source |
| CVE-2020-14314 | suse_vex | SUSE CVE CVE-2020-14314 | known affected: 423 known not affected: 144 recommended: 1552 | 2026-07-26T23:41:39+00:00 | Vulnerability · Source |
| CVE-2020-14345 | suse_vex | SUSE CVE CVE-2020-14345 | known affected: 426 recommended: 353 | 2026-07-26T23:41:37+00:00 | Vulnerability · Source |
| CVE-2020-14363 | suse_vex | SUSE CVE CVE-2020-14363 | known affected: 472 recommended: 570 | 2026-07-26T23:41:36+00:00 | Vulnerability · Source |