VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292142 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-35653 | suse_vex | SUSE CVE CVE-2020-35653 | known affected: 5 recommended: 40 | 2026-07-19T18:18:19+00:00 | Vulnerability · Source |
| CVE-2021-0127 | suse_vex | SUSE CVE CVE-2021-0127 | recommended: 83 | 2026-07-19T18:18:10+00:00 | Vulnerability · Source |
| CVE-2021-3520 | suse_vex | SUSE CVE CVE-2021-3520 | known affected: 296 known not affected: 24 recommended: 356 | 2026-07-19T18:17:41+00:00 | Vulnerability · Source |
| CVE-2021-3623 | suse_vex | SUSE CVE CVE-2021-3623 | recommended: 65 | 2026-07-19T18:17:31+00:00 | Vulnerability · Source |
| CVE-2021-20199 | suse_vex | SUSE CVE CVE-2021-20199 | recommended: 326 | 2026-07-19T18:17:09+00:00 | Vulnerability · Source |
| CVE-2021-21236 | suse_vex | SUSE CVE CVE-2021-21236 | recommended: 14 | 2026-07-19T18:17:04+00:00 | Vulnerability · Source |
| CVE-2021-21240 | suse_vex | SUSE CVE CVE-2021-21240 | known affected: 428 recommended: 85 | 2026-07-19T18:17:02+00:00 | Vulnerability · Source |
| CVE-2021-21285 | suse_vex | SUSE CVE CVE-2021-21285 | recommended: 561 | 2026-07-19T18:17:01+00:00 | Vulnerability · Source |
| CVE-2021-21411 | suse_vex | SUSE CVE CVE-2021-21411 | recommended: 3 | 2026-07-19T18:17:00+00:00 | Vulnerability · Source |
| CVE-2021-25293 | suse_vex | SUSE CVE CVE-2021-25293 | known affected: 2 known not affected: 52 recommended: 42 | 2026-07-19T18:16:35+00:00 | Vulnerability · Source |
| CVE-2021-27922 | suse_vex | SUSE CVE CVE-2021-27922 | known affected: 5 known not affected: 48 recommended: 30 | 2026-07-19T18:16:17+00:00 | Vulnerability · Source |
| CVE-2021-29983 | suse_vex | SUSE CVE CVE-2021-29983 | known affected: 12 recommended: 383 | 2026-07-19T18:16:07+00:00 | Vulnerability · Source |
| CVE-2021-33289 | suse_vex | SUSE CVE CVE-2021-33289 | recommended: 149 | 2026-07-19T18:15:35+00:00 | Vulnerability · Source |
| CVE-2021-33571 | suse_vex | SUSE CVE CVE-2021-33571 | recommended: 276 | 2026-07-19T18:15:33+00:00 | Vulnerability · Source |
| CVE-2021-34552 | suse_vex | SUSE CVE CVE-2021-34552 | known not affected: 48 recommended: 46 | 2026-07-19T18:15:30+00:00 | Vulnerability · Source |
| CVE-2021-38191 | suse_vex | SUSE CVE CVE-2021-38191 | recommended: 18 | 2026-07-19T18:15:16+00:00 | Vulnerability · Source |
| CVE-2021-41133 | suse_vex | SUSE CVE CVE-2021-41133 | known not affected: 48 recommended: 361 | 2026-07-19T18:15:05+00:00 | Vulnerability · Source |
| CVE-2022-0485 | suse_vex | SUSE CVE CVE-2022-0485 | recommended: 43 | 2026-07-19T18:14:24+00:00 | Vulnerability · Source |
| CVE-2022-0544 | suse_vex | SUSE CVE CVE-2022-0544 | recommended: 16 | 2026-07-19T18:14:23+00:00 | Vulnerability · Source |
| CVE-2022-0546 | suse_vex | SUSE CVE CVE-2022-0546 | recommended: 16 | 2026-07-19T18:14:22+00:00 | Vulnerability · Source |
| CVE-2022-2207 | suse_vex | SUSE CVE CVE-2022-2207 | known affected: 237 known not affected: 23 recommended: 489 | 2026-07-19T18:13:48+00:00 | Vulnerability · Source |
| CVE-2022-2881 | suse_vex | SUSE CVE CVE-2022-2881 | known not affected: 487 recommended: 25 | 2026-07-19T18:13:27+00:00 | Vulnerability · Source |
| CVE-2022-4806 | suse_vex | SUSE CVE CVE-2022-4806 | recommended: 26 | 2026-07-19T18:13:08+00:00 | Vulnerability · Source |
| CVE-2022-22624 | suse_vex | SUSE CVE CVE-2022-22624 | known affected: 24 known not affected: 344 recommended: 923 | 2026-07-19T18:12:51+00:00 | Vulnerability · Source |
| CVE-2022-22817 | suse_vex | SUSE CVE CVE-2022-22817 | recommended: 138 | 2026-07-19T18:12:40+00:00 | Vulnerability · Source |
| CVE-2022-23649 | suse_vex | SUSE CVE CVE-2022-23649 | known not affected: 8 recommended: 39 | 2026-07-19T18:12:33+00:00 | Vulnerability · Source |
| CVE-2022-23949 | suse_vex | SUSE CVE CVE-2022-23949 | known not affected: 72 recommended: 201 | 2026-07-19T18:12:29+00:00 | Vulnerability · Source |
| CVE-2022-24439 | suse_vex | SUSE CVE CVE-2022-24439 | known not affected: 3 recommended: 14 | 2026-07-19T18:12:24+00:00 | Vulnerability · Source |
| CVE-2022-26354 | suse_vex | SUSE CVE CVE-2022-26354 | known affected: 530 known not affected: 291 recommended: 1424 | 2026-07-19T18:12:14+00:00 | Vulnerability · Source |
| CVE-2022-28347 | suse_vex | SUSE CVE CVE-2022-28347 | known not affected: 5 recommended: 17 | 2026-07-19T18:11:50+00:00 | Vulnerability · Source |
| CVE-2022-30785 | suse_vex | SUSE CVE CVE-2022-30785 | recommended: 124 | 2026-07-19T18:11:43+00:00 | Vulnerability · Source |
| CVE-2022-30788 | suse_vex | SUSE CVE CVE-2022-30788 | recommended: 252 | 2026-07-19T18:11:42+00:00 | Vulnerability · Source |
| CVE-2022-31625 | suse_vex | SUSE CVE CVE-2022-31625 | recommended: 4470 | 2026-07-19T18:11:38+00:00 | Vulnerability · Source |
| CVE-2022-34265 | suse_vex | SUSE CVE CVE-2022-34265 | recommended: 106 | 2026-07-19T18:11:11+00:00 | Vulnerability · Source |
| CVE-2022-34303 | suse_vex | SUSE CVE CVE-2022-34303 | known not affected: 56 recommended: 3 | 2026-07-19T18:11:10+00:00 | Vulnerability · Source |
| CVE-2022-36033 | suse_vex | SUSE CVE CVE-2022-36033 | known affected: 5 recommended: 46 | 2026-07-19T18:10:56+00:00 | Vulnerability · Source |
| CVE-2022-37035 | suse_vex | SUSE CVE CVE-2022-37035 | recommended: 276 | 2026-07-19T18:10:53+00:00 | Vulnerability · Source |
| CVE-2022-38648 | suse_vex | SUSE CVE CVE-2022-38648 | recommended: 114 | 2026-07-19T18:10:43+00:00 | Vulnerability · Source |
| CVE-2022-40146 | suse_vex | SUSE CVE CVE-2022-40146 | recommended: 114 | 2026-07-19T18:10:32+00:00 | Vulnerability · Source |
| CVE-2022-42003 | suse_vex | SUSE CVE CVE-2022-42003 | known affected: 394 recommended: 68 | 2026-07-19T18:10:18+00:00 | Vulnerability · Source |
| CVE-2022-45421 | suse_vex | SUSE CVE CVE-2022-45421 | known affected: 1 recommended: 393 | 2026-07-19T18:09:58+00:00 | Vulnerability · Source |
| CVE-2022-49345 | suse_vex | SUSE CVE CVE-2022-49345 | known affected: 490 known not affected: 249 recommended: 250 | 2026-07-19T18:09:36+00:00 | Vulnerability · Source |
| CVE-2023-5215 | suse_vex | SUSE CVE CVE-2023-5215 | recommended: 46 | 2026-07-19T18:08:18+00:00 | Vulnerability · Source |
| CVE-2023-5871 | suse_vex | SUSE CVE CVE-2023-5871 | recommended: 46 | 2026-07-19T18:08:13+00:00 | Vulnerability · Source |
| CVE-2023-25744 | suse_vex | SUSE CVE CVE-2023-25744 | known affected: 1 recommended: 233 | 2026-07-19T18:07:27+00:00 | Vulnerability · Source |
| CVE-2023-44271 | suse_vex | SUSE CVE CVE-2023-44271 | recommended: 91 | 2026-07-19T18:06:10+00:00 | Vulnerability · Source |
| CVE-2023-46853 | suse_vex | SUSE CVE CVE-2023-46853 | known not affected: 86 recommended: 6 | 2026-07-19T18:05:54+00:00 | Vulnerability · Source |
| CVE-2023-49092 | suse_vex | SUSE CVE CVE-2023-49092 | known affected: 28 known not affected: 63 recommended: 3 | 2026-07-19T18:05:46+00:00 | Vulnerability · Source |
| CVE-2023-49993 | suse_vex | SUSE CVE CVE-2023-49993 | known affected: 110 recommended: 100 | 2026-07-19T18:05:44+00:00 | Vulnerability · Source |
| CVE-2023-50471 | suse_vex | SUSE CVE CVE-2023-50471 | recommended: 8 | 2026-07-19T18:05:40+00:00 | Vulnerability · Source |