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-2019-14195 | suse_vex | SUSE CVE CVE-2019-14195 | known affected: 19 recommended: 46 | 2026-07-26T16:55:41+00:00 | Vulnerability · Source |
| CVE-2019-14196 | suse_vex | SUSE CVE CVE-2019-14196 | known affected: 19 recommended: 46 | 2026-07-26T16:55:40+00:00 | Vulnerability · Source |
| CVE-2019-14198 | suse_vex | SUSE CVE CVE-2019-14198 | known affected: 19 recommended: 46 | 2026-07-26T16:55:38+00:00 | Vulnerability · Source |
| CVE-2019-14607 | suse_vex | SUSE CVE CVE-2019-14607 | known not affected: 28 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-14444 | suse_vex | SUSE CVE CVE-2019-14444 | known affected: 428 recommended: 553 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-15791 | suse_vex | SUSE CVE CVE-2019-15791 | known not affected: 208 | 2026-07-26T16:55:31+00:00 | Vulnerability · Source |
| CVE-2019-17040 | suse_vex | SUSE CVE CVE-2019-17040 | known affected: 22 known not affected: 241 | 2026-07-26T16:55:27+00:00 | Vulnerability · Source |
| CVE-2019-17347 | suse_vex | SUSE CVE CVE-2019-17347 | known affected: 18 known not affected: 166 recommended: 207 | 2026-07-26T16:55:26+00:00 | Vulnerability · Source |
| CVE-2019-17571 | suse_vex | SUSE CVE CVE-2019-17571 | known affected: 405 known not affected: 28 recommended: 305 | 2026-07-26T16:55:24+00:00 | Vulnerability · Source |
| CVE-2019-17582 | suse_vex | SUSE CVE CVE-2019-17582 | known not affected: 131 | 2026-07-26T16:55:23+00:00 | Vulnerability · Source |
| CVE-2019-19055 | suse_vex | SUSE CVE CVE-2019-19055 | known affected: 320 known not affected: 381 recommended: 814 | 2026-07-26T16:55:20+00:00 | Vulnerability · Source |
| CVE-2019-19242 | suse_vex | SUSE CVE CVE-2019-19242 | known not affected: 358 | 2026-07-26T16:55:19+00:00 | Vulnerability · Source |
| CVE-2019-19815 | suse_vex | SUSE CVE CVE-2019-19815 | known not affected: 257 | 2026-07-26T16:55:17+00:00 | Vulnerability · Source |
| CVE-2019-20422 | suse_vex | SUSE CVE CVE-2019-20422 | known affected: 320 known not affected: 314 recommended: 781 | 2026-07-26T16:55:10+00:00 | Vulnerability · Source |
| CVE-2019-20808 | suse_vex | SUSE CVE CVE-2019-20808 | known not affected: 715 | 2026-07-26T16:55:07+00:00 | Vulnerability · Source |
| CVE-2019-1010190 | suse_vex | SUSE CVE CVE-2019-1010190 | known affected: 23 known not affected: 23 recommended: 129 | 2026-07-26T16:55:04+00:00 | Vulnerability · Source |
| CVE-2019-1010238 | suse_vex | SUSE CVE CVE-2019-1010238 | known not affected: 156 recommended: 8 | 2026-07-26T16:55:02+00:00 | Vulnerability · Source |
| CVE-2020-1699 | suse_vex | SUSE CVE CVE-2020-1699 | known affected: 85 known not affected: 317 recommended: 214 | 2026-07-26T16:54:59+00:00 | Vulnerability · Source |
| CVE-2020-2585 | suse_vex | SUSE CVE CVE-2020-2585 | known affected: 160 | 2026-07-26T16:54:57+00:00 | Vulnerability · Source |
| CVE-2020-6800 | suse_vex | SUSE CVE CVE-2020-6800 | known affected: 20 recommended: 402 | 2026-07-26T16:54:54+00:00 | Vulnerability · Source |
| CVE-2020-10135 | suse_vex | SUSE CVE CVE-2020-10135 | known affected: 407 known not affected: 21 recommended: 1647 | 2026-07-26T16:54:49+00:00 | Vulnerability · Source |
| CVE-2020-11655 | suse_vex | SUSE CVE CVE-2020-11655 | known not affected: 445 | 2026-07-26T16:54:44+00:00 | Vulnerability · Source |
| CVE-2020-11931 | suse_vex | SUSE CVE CVE-2020-11931 | known not affected: 428 | 2026-07-26T16:54:43+00:00 | Vulnerability · Source |
| CVE-2020-12319 | suse_vex | SUSE CVE CVE-2020-12319 | known not affected: 154 | 2026-07-26T16:54:41+00:00 | Vulnerability · Source |
| CVE-2020-13379 | suse_vex | SUSE CVE CVE-2020-13379 | known affected: 1 recommended: 886 | 2026-07-26T16:54:37+00:00 | Vulnerability · Source |
| CVE-2020-14797 | suse_vex | SUSE CVE CVE-2020-14797 | known affected: 484 recommended: 1235 | 2026-07-26T16:54:32+00:00 | Vulnerability · Source |
| CVE-2020-14812 | suse_vex | SUSE CVE CVE-2020-14812 | known not affected: 90 recommended: 664 | 2026-07-26T16:54:31+00:00 | Vulnerability · Source |
| CVE-2020-15802 | suse_vex | SUSE CVE CVE-2020-15802 | known affected: 2 | 2026-07-26T16:54:29+00:00 | Vulnerability · Source |
| CVE-2020-16287 | suse_vex | SUSE CVE CVE-2020-16287 | known not affected: 172 recommended: 8 | 2026-07-26T16:54:24+00:00 | Vulnerability · Source |
| CVE-2020-16298 | suse_vex | SUSE CVE CVE-2020-16298 | known not affected: 172 recommended: 8 | 2026-07-26T16:54:23+00:00 | Vulnerability · Source |
| CVE-2020-18898 | suse_vex | SUSE CVE CVE-2020-18898 | known not affected: 128 recommended: 96 | 2026-07-26T16:54:21+00:00 | Vulnerability · Source |
| CVE-2020-21678 | suse_vex | SUSE CVE CVE-2020-21678 | known not affected: 30 | 2026-07-26T16:54:19+00:00 | Vulnerability · Source |
| CVE-2020-25275 | suse_vex | SUSE CVE CVE-2020-25275 | known not affected: 82 recommended: 446 | 2026-07-26T16:54:15+00:00 | Vulnerability · Source |
| CVE-2020-25637 | suse_vex | SUSE CVE CVE-2020-25637 | known affected: 855 known not affected: 4 recommended: 2370 | 2026-07-26T16:54:13+00:00 | Vulnerability · Source |
| CVE-2020-25712 | suse_vex | SUSE CVE CVE-2020-25712 | known affected: 437 recommended: 353 | 2026-07-26T16:54:11+00:00 | Vulnerability · Source |
| CVE-2020-25743 | suse_vex | SUSE CVE CVE-2020-25743 | known affected: 42 known not affected: 729 | 2026-07-26T16:54:07+00:00 | Vulnerability · Source |
| CVE-2020-26420 | suse_vex | SUSE CVE CVE-2020-26420 | known affected: 44 known not affected: 63 recommended: 650 | 2026-07-26T16:54:02+00:00 | Vulnerability · Source |
| CVE-2020-26952 | suse_vex | SUSE CVE CVE-2020-26952 | known affected: 59 recommended: 9 | 2026-07-26T16:53:59+00:00 | Vulnerability · Source |
| CVE-2020-27837 | suse_vex | SUSE CVE CVE-2020-27837 | known affected: 239 known not affected: 315 recommended: 213 | 2026-07-26T16:53:55+00:00 | Vulnerability · Source |
| CVE-2020-35506 | suse_vex | SUSE CVE CVE-2020-35506 | known affected: 388 known not affected: 649 recommended: 1081 | 2026-07-26T16:53:52+00:00 | Vulnerability · Source |
| CVE-2020-35513 | suse_vex | SUSE CVE CVE-2020-35513 | known not affected: 409 recommended: 13 | 2026-07-26T16:53:48+00:00 | Vulnerability · Source |
| CVE-2020-35517 | suse_vex | SUSE CVE CVE-2020-35517 | known not affected: 1180 | 2026-07-26T16:53:47+00:00 | Vulnerability · Source |
| CVE-2020-36221 | suse_vex | SUSE CVE CVE-2020-36221 | known affected: 298 recommended: 854 | 2026-07-26T16:53:45+00:00 | Vulnerability · Source |
| CVE-2020-36775 | suse_vex | SUSE CVE CVE-2020-36775 | known not affected: 304 | 2026-07-26T16:53:43+00:00 | Vulnerability · Source |
| CVE-2020-37127 | suse_vex | SUSE CVE CVE-2020-37127 | known not affected: 36 | 2026-07-26T16:53:42+00:00 | Vulnerability · Source |
| CVE-2021-0938 | suse_vex | SUSE CVE CVE-2021-0938 | known not affected: 316 | 2026-07-26T16:53:39+00:00 | Vulnerability · Source |
| CVE-2021-3658 | suse_vex | SUSE CVE CVE-2021-3658 | known affected: 6 known not affected: 42 recommended: 109 | 2026-07-26T16:53:31+00:00 | Vulnerability · Source |
| CVE-2021-4166 | suse_vex | SUSE CVE CVE-2021-4166 | known affected: 363 known not affected: 7 recommended: 366 | 2026-07-26T16:53:27+00:00 | Vulnerability · Source |
| CVE-2021-26376 | suse_vex | SUSE CVE CVE-2021-26376 | known affected: 11 known not affected: 1 recommended: 1292 | 2026-07-26T16:53:16+00:00 | Vulnerability · Source |
| CVE-2021-28662 | suse_vex | SUSE CVE CVE-2021-28662 | known affected: 394 known not affected: 72 recommended: 52 | 2026-07-26T16:53:14+00:00 | Vulnerability · Source |