VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284520 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-8619 | suse_vex | SUSE CVE CVE-2020-8619 | known affected: 320 known not affected: 143 recommended: 859 | 2026-07-26T00:14:12+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 |
| 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-13754 | suse_vex | SUSE CVE CVE-2020-13754 | known affected: 461 known not affected: 1307 recommended: 478 | 2026-07-26T00:13:54+00:00 | Vulnerability · Source |
| CVE-2020-14154 | suse_vex | SUSE CVE CVE-2020-14154 | known affected: 9 recommended: 219 | 2026-07-26T00:13:52+00:00 | Vulnerability · Source |
| CVE-2020-14310 | suse_vex | SUSE CVE CVE-2020-14310 | known affected: 94 recommended: 779 | 2026-07-26T00:13:50+00:00 | Vulnerability · Source |
| CVE-2020-14342 | suse_vex | SUSE CVE CVE-2020-14342 | known affected: 343 known not affected: 56 recommended: 216 | 2026-07-26T00:13:48+00:00 | Vulnerability · Source |
| CVE-2020-14374 | suse_vex | SUSE CVE CVE-2020-14374 | known affected: 26 known not affected: 29 recommended: 314 | 2026-07-26T00:13:46+00:00 | Vulnerability · Source |
| CVE-2020-16156 | suse_vex | SUSE CVE CVE-2020-16156 | known affected: 12 known not affected: 8 recommended: 1 | 2026-07-26T00:13:43+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-16592 | suse_vex | SUSE CVE CVE-2020-16592 | known affected: 398 known not affected: 23 recommended: 540 | 2026-07-26T00:13:39+00:00 | Vulnerability · Source |
| CVE-2020-18899 | suse_vex | SUSE CVE CVE-2020-18899 | known not affected: 114 recommended: 91 | 2026-07-26T00:13:37+00:00 | Vulnerability · Source |
| CVE-2020-21913 | suse_vex | SUSE CVE CVE-2020-21913 | known affected: 509 known not affected: 8 recommended: 623 | 2026-07-26T00:13:35+00:00 | Vulnerability · Source |
| CVE-2020-24342 | suse_vex | SUSE CVE CVE-2020-24342 | known not affected: 492 recommended: 19 | 2026-07-26T00:13:33+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-25669 | suse_vex | SUSE CVE CVE-2020-25669 | known affected: 292 known not affected: 108 recommended: 1616 | 2026-07-26T00:13:25+00:00 | Vulnerability · Source |
| CVE-2020-25687 | suse_vex | SUSE CVE CVE-2020-25687 | recommended: 109 | 2026-07-26T00:13:23+00:00 | Vulnerability · Source |
| CVE-2020-27560 | suse_vex | SUSE CVE CVE-2020-27560 | known affected: 111 recommended: 615 | 2026-07-26T00:13:20+00:00 | Vulnerability · Source |
| CVE-2020-27758 | suse_vex | SUSE CVE CVE-2020-27758 | known not affected: 155 recommended: 636 | 2026-07-26T00:13:18+00:00 | Vulnerability · Source |
| CVE-2020-36023 | suse_vex | SUSE CVE CVE-2020-36023 | known not affected: 127 recommended: 93 | 2026-07-26T00:13:15+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-2020-36788 | suse_vex | SUSE CVE CVE-2020-36788 | known affected: 348 known not affected: 181 recommended: 464 | 2026-07-26T00:13:11+00:00 | Vulnerability · Source |
| CVE-2021-0072 | suse_vex | SUSE CVE CVE-2021-0072 | known not affected: 71 recommended: 130 | 2026-07-26T00:13:09+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-0174 | suse_vex | SUSE CVE CVE-2021-0174 | known not affected: 71 recommended: 130 | 2026-07-26T00:13:05+00:00 | Vulnerability · Source |
| CVE-2021-1801 | suse_vex | SUSE CVE CVE-2021-1801 | recommended: 1020 | 2026-07-26T00:13:03+00:00 | Vulnerability · Source |
| CVE-2021-3347 | suse_vex | SUSE CVE CVE-2021-3347 | known affected: 441 known not affected: 124 recommended: 1704 | 2026-07-26T00:13:00+00:00 | Vulnerability · Source |
| CVE-2021-3449 | suse_vex | SUSE CVE CVE-2021-3449 | known affected: 328 known not affected: 566 recommended: 685 | 2026-07-26T00:12:58+00:00 | Vulnerability · Source |
| CVE-2021-3474 | suse_vex | SUSE CVE CVE-2021-3474 | known not affected: 61 recommended: 152 | 2026-07-26T00:12:56+00:00 | Vulnerability · Source |
| CVE-2021-3518 | suse_vex | SUSE CVE CVE-2021-3518 | known affected: 253 known not affected: 51 recommended: 646 | 2026-07-26T00:12:54+00:00 | Vulnerability · Source |
| CVE-2021-3573 | suse_vex | SUSE CVE CVE-2021-3573 | known affected: 305 known not affected: 345 recommended: 1311 | 2026-07-26T00:12:52+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-4009 | suse_vex | SUSE CVE CVE-2021-4009 | known affected: 395 known not affected: 14 recommended: 291 | 2026-07-26T00:12:45+00:00 | Vulnerability · Source |
| CVE-2021-4158 | suse_vex | SUSE CVE CVE-2021-4158 | known not affected: 1338 recommended: 779 | 2026-07-26T00:12:42+00:00 | Vulnerability · Source |
| CVE-2021-20225 | suse_vex | SUSE CVE CVE-2021-20225 | known affected: 293 recommended: 869 | 2026-07-26T00:12:40+00:00 | Vulnerability · Source |
| CVE-2021-20311 | suse_vex | SUSE CVE CVE-2021-20311 | known not affected: 87 recommended: 568 | 2026-07-26T00:12:38+00:00 | Vulnerability · Source |
| CVE-2021-22600 | suse_vex | SUSE CVE CVE-2021-22600 | known affected: 347 known not affected: 289 recommended: 1170 | 2026-07-26T00:12:35+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-28091 | suse_vex | SUSE CVE CVE-2021-28091 | recommended: 38 | 2026-07-26T00:12:30+00:00 | Vulnerability · Source |