VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-32545 | suse_vex | SUSE CVE CVE-2022-32545 | recommended: 513 | 2026-07-17T13:53:34+00:00 | Vulnerability · Source |
| CVE-2022-36359 | suse_vex | SUSE CVE CVE-2022-36359 | known not affected: 5 recommended: 19 | 2026-07-17T13:53:05+00:00 | Vulnerability · Source |
| CVE-2022-37865 | suse_vex | SUSE CVE CVE-2022-37865 | recommended: 150 | 2026-07-17T13:53:01+00:00 | Vulnerability · Source |
| CVE-2022-38533 | suse_vex | SUSE CVE CVE-2022-38533 | known affected: 394 recommended: 445 | 2026-07-17T13:52:58+00:00 | Vulnerability · Source |
| CVE-2022-39348 | suse_vex | SUSE CVE CVE-2022-39348 | known affected: 9 recommended: 138 | 2026-07-17T13:52:50+00:00 | Vulnerability · Source |
| CVE-2022-41704 | suse_vex | SUSE CVE CVE-2022-41704 | recommended: 71 | 2026-07-17T13:52:42+00:00 | Vulnerability · Source |
| CVE-2022-41742 | suse_vex | SUSE CVE CVE-2022-41742 | recommended: 88 | 2026-07-17T13:52:40+00:00 | Vulnerability · Source |
| CVE-2022-44571 | suse_vex | SUSE CVE CVE-2022-44571 | known affected: 394 recommended: 28 | 2026-07-17T13:52:21+00:00 | Vulnerability · Source |
| CVE-2022-45157 | suse_vex | SUSE CVE CVE-2022-45157 | recommended: 3 | 2026-07-17T13:52:17+00:00 | Vulnerability · Source |
| CVE-2022-49980 | suse_vex | SUSE CVE CVE-2022-49980 | known affected: 436 known not affected: 193 recommended: 323 | 2026-07-17T13:51:39+00:00 | Vulnerability · Source |
| CVE-2023-0804 | suse_vex | SUSE CVE CVE-2023-0804 | known affected: 488 known not affected: 1 recommended: 155 | 2026-07-17T13:51:00+00:00 | Vulnerability · Source |
| CVE-2023-0996 | suse_vex | SUSE CVE CVE-2023-0996 | recommended: 67 | 2026-07-17T13:50:58+00:00 | Vulnerability · Source |
| CVE-2023-3961 | suse_vex | SUSE CVE CVE-2023-3961 | known affected: 270 known not affected: 1622 recommended: 603 | 2026-07-17T13:50:15+00:00 | Vulnerability · Source |
| CVE-2023-5129 | suse_vex | SUSE CVE CVE-2023-5129 | known not affected: 162 recommended: 13 | 2026-07-17T13:49:28+00:00 | Vulnerability · Source |
| CVE-2023-6135 | suse_vex | SUSE CVE CVE-2023-6135 | known affected: 28 recommended: 31 | 2026-07-17T13:49:03+00:00 | Vulnerability · Source |
| CVE-2023-6704 | suse_vex | SUSE CVE CVE-2023-6704 | known affected: 18 recommended: 56 | 2026-07-17T13:48:44+00:00 | Vulnerability · Source |
| CVE-2023-25153 | suse_vex | SUSE CVE CVE-2023-25153 | known affected: 333 known not affected: 35 recommended: 195 | 2026-07-17T13:47:47+00:00 | Vulnerability · Source |
| CVE-2023-25733 | suse_vex | SUSE CVE CVE-2023-25733 | known affected: 1 recommended: 9 | 2026-07-17T13:47:31+00:00 | Vulnerability · Source |
| CVE-2023-27530 | suse_vex | SUSE CVE CVE-2023-27530 | known affected: 394 known not affected: 4 recommended: 157 | 2026-07-17T13:47:17+00:00 | Vulnerability · Source |
| CVE-2023-30589 | suse_vex | SUSE CVE CVE-2023-30589 | known not affected: 1 recommended: 385 | 2026-07-17T13:46:38+00:00 | Vulnerability · Source |
| CVE-2023-31047 | suse_vex | SUSE CVE CVE-2023-31047 | recommended: 17 | 2026-07-17T13:46:36+00:00 | Vulnerability · Source |
| CVE-2023-37206 | suse_vex | SUSE CVE CVE-2023-37206 | recommended: 252 | 2026-07-17T13:46:06+00:00 | Vulnerability · Source |
| CVE-2023-39418 | suse_vex | SUSE CVE CVE-2023-39418 | known affected: 394 known not affected: 1366 recommended: 329 | 2026-07-17T13:45:36+00:00 | Vulnerability · Source |
| CVE-2023-40575 | suse_vex | SUSE CVE CVE-2023-40575 | recommended: 190 | 2026-07-17T13:45:22+00:00 | Vulnerability · Source |
| CVE-2023-40890 | suse_vex | SUSE CVE CVE-2023-40890 | known affected: 18 recommended: 67 | 2026-07-17T13:45:21+00:00 | Vulnerability · Source |
| CVE-2023-42365 | suse_vex | SUSE CVE CVE-2023-42365 | known affected: 63 recommended: 116 | 2026-07-17T13:45:14+00:00 | Vulnerability · Source |
| CVE-2023-46136 | suse_vex | SUSE CVE CVE-2023-46136 | known not affected: 97 recommended: 31 | 2026-07-17T13:44:48+00:00 | Vulnerability · Source |
| CVE-2023-46753 | suse_vex | SUSE CVE CVE-2023-46753 | known not affected: 282 recommended: 280 | 2026-07-17T13:44:40+00:00 | Vulnerability · Source |
| CVE-2023-49288 | suse_vex | SUSE CVE CVE-2023-49288 | known not affected: 42 recommended: 8 | 2026-07-17T13:44:24+00:00 | Vulnerability · Source |
| CVE-2023-51794 | suse_vex | SUSE CVE CVE-2023-51794 | known affected: 112 recommended: 747 | 2026-07-17T13:44:04+00:00 | Vulnerability · Source |
| CVE-2023-52796 | suse_vex | SUSE CVE CVE-2023-52796 | known affected: 488 known not affected: 33 recommended: 783 | 2026-07-17T13:42:00+00:00 | Vulnerability · Source |
| CVE-2023-53781 | suse_vex | SUSE CVE CVE-2023-53781 | known affected: 449 known not affected: 204 recommended: 318 | 2026-07-17T13:40:55+00:00 | Vulnerability · Source |
| CVE-2024-1454 | suse_vex | SUSE CVE CVE-2024-1454 | known not affected: 49 recommended: 6 | 2026-07-17T13:40:19+00:00 | Vulnerability · Source |
| CVE-2024-1556 | suse_vex | SUSE CVE CVE-2024-1556 | known affected: 42 recommended: 9 | 2026-07-17T13:40:14+00:00 | Vulnerability · Source |
| CVE-2024-2757 | suse_vex | SUSE CVE CVE-2024-2757 | known not affected: 3905 recommended: 153 | 2026-07-17T13:39:59+00:00 | Vulnerability · Source |
| CVE-2024-3856 | suse_vex | SUSE CVE CVE-2024-3856 | known affected: 32 recommended: 9 | 2026-07-17T13:39:48+00:00 | Vulnerability · Source |
| CVE-2024-5321 | suse_vex | SUSE CVE CVE-2024-5321 | known not affected: 375 recommended: 3 | 2026-07-17T13:39:29+00:00 | Vulnerability · Source |
| CVE-2024-5695 | suse_vex | SUSE CVE CVE-2024-5695 | known affected: 33 recommended: 9 | 2026-07-17T13:39:21+00:00 | Vulnerability · Source |
| CVE-2024-6156 | suse_vex | SUSE CVE CVE-2024-6156 | recommended: 3 | 2026-07-17T13:39:17+00:00 | Vulnerability · Source |
| CVE-2024-6174 | suse_vex | SUSE CVE CVE-2024-6174 | known affected: 398 recommended: 163 | 2026-07-17T13:39:16+00:00 | Vulnerability · Source |
| CVE-2024-7383 | suse_vex | SUSE CVE CVE-2024-7383 | recommended: 59 | 2026-07-17T13:38:58+00:00 | Vulnerability · Source |
| CVE-2024-9312 | suse_vex | SUSE CVE CVE-2024-9312 | recommended: 3 | 2026-07-17T13:38:29+00:00 | Vulnerability · Source |
| CVE-2024-9313 | suse_vex | SUSE CVE CVE-2024-9313 | recommended: 3 | 2026-07-17T13:38:28+00:00 | Vulnerability · Source |
| CVE-2024-9341 | suse_vex | SUSE CVE CVE-2024-9341 | known affected: 400 known not affected: 58 recommended: 184 | 2026-07-17T13:38:26+00:00 | Vulnerability · Source |
| CVE-2024-9594 | suse_vex | SUSE CVE CVE-2024-9594 | recommended: 3 | 2026-07-17T13:38:12+00:00 | Vulnerability · Source |
| CVE-2024-10389 | suse_vex | SUSE CVE CVE-2024-10389 | recommended: 3 | 2026-07-17T13:38:05+00:00 | Vulnerability · Source |
| CVE-2024-11079 | suse_vex | SUSE CVE CVE-2024-11079 | known not affected: 8 recommended: 14 | 2026-07-17T13:37:54+00:00 | Vulnerability · Source |
| CVE-2024-11584 | suse_vex | SUSE CVE CVE-2024-11584 | known affected: 378 known not affected: 20 recommended: 161 | 2026-07-17T13:37:48+00:00 | Vulnerability · Source |
| CVE-2024-12401 | suse_vex | SUSE CVE CVE-2024-12401 | recommended: 3 | 2026-07-17T13:37:34+00:00 | Vulnerability · Source |
| CVE-2024-21503 | suse_vex | SUSE CVE CVE-2024-21503 | recommended: 8 | 2026-07-17T13:37:19+00:00 | Vulnerability · Source |