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-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-14310 | suse_vex | SUSE CVE CVE-2020-14310 | known affected: 94 recommended: 779 | 2026-07-26T00:13:50+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-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-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-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-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-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-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-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-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-23983 | suse_vex | SUSE CVE CVE-2021-23983 | recommended: 9 | 2026-07-26T00:12:33+00:00 | Vulnerability · Source |
| CVE-2021-28714 | suse_vex | SUSE CVE CVE-2021-28714 | known affected: 332 known not affected: 70 recommended: 1227 | 2026-07-26T00:12:28+00:00 | Vulnerability · Source |
| CVE-2021-33430 | suse_vex | SUSE CVE CVE-2021-33430 | known affected: 409 known not affected: 11 recommended: 420 | 2026-07-26T00:12:20+00:00 | Vulnerability · Source |
| CVE-2021-41079 | suse_vex | SUSE CVE CVE-2021-41079 | known affected: 394 known not affected: 129 recommended: 536 | 2026-07-26T00:12:12+00:00 | Vulnerability · Source |
| CVE-2021-41617 | suse_vex | SUSE CVE CVE-2021-41617 | known affected: 331 recommended: 549 | 2026-07-26T00:12:09+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-47158 | suse_vex | SUSE CVE CVE-2021-47158 | known affected: 55 known not affected: 298 | 2026-07-26T00:12:01+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-1508 | suse_vex | SUSE CVE CVE-2022-1508 | known affected: 257 known not affected: 343 recommended: 615 | 2026-07-26T00:11:30+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 122 recommended: 1474 | 2026-07-26T00:11:14+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-34473 | suse_vex | SUSE CVE CVE-2022-34473 | known affected: 1 recommended: 365 | 2026-07-26T00:10:38+00:00 | Vulnerability · Source |
| CVE-2022-38177 | suse_vex | SUSE CVE CVE-2022-38177 | known affected: 254 known not affected: 1 recommended: 1064 | 2026-07-26T00:10:35+00:00 | Vulnerability · Source |
| CVE-2022-38235 | suse_vex | SUSE CVE CVE-2022-38235 | known not affected: 330 | 2026-07-26T00:10:32+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-42310 | suse_vex | SUSE CVE CVE-2022-42310 | known affected: 253 recommended: 518 | 2026-07-26T00:10:25+00:00 | Vulnerability · Source |
| CVE-2022-42824 | suse_vex | SUSE CVE CVE-2022-42824 | known affected: 1 known not affected: 164 recommended: 976 | 2026-07-26T00:10:23+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-48655 | suse_vex | SUSE CVE CVE-2022-48655 | known affected: 265 known not affected: 225 recommended: 462 | 2026-07-26T00:10:15+00:00 | Vulnerability · Source |
| CVE-2022-48750 | suse_vex | SUSE CVE CVE-2022-48750 | known not affected: 318 | 2026-07-26T00:10:11+00:00 | Vulnerability · Source |
| CVE-2022-48857 | suse_vex | SUSE CVE CVE-2022-48857 | known affected: 377 known not affected: 98 recommended: 595 | 2026-07-26T00:10:03+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-48894 | suse_vex | SUSE CVE CVE-2022-48894 | known not affected: 310 | 2026-07-26T00:09:56+00:00 | Vulnerability · Source |