VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-46752 | suse_vex | SUSE CVE CVE-2024-46752 | known affected: 573 known not affected: 32 recommended: 682 | 2026-07-25T16:53:38+00:00 | Vulnerability · Source |
| CVE-2024-46863 | suse_vex | SUSE CVE CVE-2024-46863 | known not affected: 324 recommended: 59 | 2026-07-25T16:53:32+00:00 | Vulnerability · Source |
| CVE-2024-47850 | suse_vex | SUSE CVE CVE-2024-47850 | known affected: 33 recommended: 146 | 2026-07-25T16:53:27+00:00 | Vulnerability · Source |
| CVE-2024-49876 | suse_vex | SUSE CVE CVE-2024-49876 | known not affected: 379 recommended: 65 | 2026-07-25T16:53:25+00:00 | Vulnerability · Source |
| CVE-2024-49893 | suse_vex | SUSE CVE CVE-2024-49893 | known not affected: 402 recommended: 65 | 2026-07-25T16:53:23+00:00 | Vulnerability · Source |
| CVE-2024-49988 | suse_vex | SUSE CVE CVE-2024-49988 | known not affected: 379 recommended: 6 | 2026-07-25T16:53:21+00:00 | Vulnerability · Source |
| CVE-2024-50030 | suse_vex | SUSE CVE CVE-2024-50030 | known not affected: 379 recommended: 65 | 2026-07-25T16:53:19+00:00 | Vulnerability · Source |
| CVE-2024-50097 | suse_vex | SUSE CVE CVE-2024-50097 | known not affected: 370 recommended: 6 | 2026-07-25T16:53:17+00:00 | Vulnerability · Source |
| CVE-2024-50104 | suse_vex | SUSE CVE CVE-2024-50104 | known not affected: 370 recommended: 65 | 2026-07-25T16:53:15+00:00 | Vulnerability · Source |
| CVE-2024-50107 | suse_vex | SUSE CVE CVE-2024-50107 | known not affected: 370 recommended: 108 | 2026-07-25T16:53:14+00:00 | Vulnerability · Source |
| CVE-2024-50253 | suse_vex | SUSE CVE CVE-2024-50253 | known not affected: 378 recommended: 6 | 2026-07-25T16:53:11+00:00 | Vulnerability · Source |
| CVE-2024-50383 | suse_vex | SUSE CVE CVE-2024-50383 | known not affected: 61 recommended: 36 | 2026-07-25T16:53:07+00:00 | Vulnerability · Source |
| CVE-2024-52533 | suse_vex | SUSE CVE CVE-2024-52533 | known affected: 451 known not affected: 7 recommended: 658 | 2026-07-25T16:53:04+00:00 | Vulnerability · Source |
| CVE-2024-53073 | suse_vex | SUSE CVE CVE-2024-53073 | known not affected: 372 | 2026-07-25T16:53:02+00:00 | Vulnerability · Source |
| CVE-2024-53092 | suse_vex | SUSE CVE CVE-2024-53092 | known not affected: 372 | 2026-07-25T16:53:01+00:00 | Vulnerability · Source |
| CVE-2024-53225 | suse_vex | SUSE CVE CVE-2024-53225 | known not affected: 438 recommended: 112 | 2026-07-25T16:52:58+00:00 | Vulnerability · Source |
| CVE-2024-53589 | suse_vex | SUSE CVE CVE-2024-53589 | known not affected: 191 | 2026-07-25T16:52:56+00:00 | Vulnerability · Source |
| CVE-2024-54191 | suse_vex | SUSE CVE CVE-2024-54191 | known not affected: 346 recommended: 53 | 2026-07-25T16:52:55+00:00 | Vulnerability · Source |
| CVE-2024-54467 | suse_vex | SUSE CVE CVE-2024-54467 | known affected: 107 recommended: 592 | 2026-07-25T16:52:53+00:00 | Vulnerability · Source |
| CVE-2024-56555 | suse_vex | SUSE CVE CVE-2024-56555 | known not affected: 438 | 2026-07-25T16:52:50+00:00 | Vulnerability · Source |
| CVE-2024-56680 | suse_vex | SUSE CVE CVE-2024-56680 | known not affected: 425 recommended: 112 | 2026-07-25T16:52:46+00:00 | Vulnerability · Source |
| CVE-2024-57806 | suse_vex | SUSE CVE CVE-2024-57806 | known not affected: 346 recommended: 53 | 2026-07-25T16:52:41+00:00 | Vulnerability · Source |
| CVE-2024-57875 | suse_vex | SUSE CVE CVE-2024-57875 | known not affected: 346 recommended: 53 | 2026-07-25T16:52:38+00:00 | Vulnerability · Source |
| CVE-2024-58022 | suse_vex | SUSE CVE CVE-2024-58022 | known not affected: 352 | 2026-07-25T16:52:33+00:00 | Vulnerability · Source |
| CVE-2025-0306 | suse_vex | SUSE CVE CVE-2025-0306 | known affected: 26 known not affected: 806 | 2026-07-25T16:52:28+00:00 | Vulnerability · Source |
| CVE-2025-0577 | suse_vex | SUSE CVE CVE-2025-0577 | known not affected: 455 | 2026-07-25T16:52:27+00:00 | Vulnerability · Source |
| CVE-2025-0689 | suse_vex | SUSE CVE CVE-2025-0689 | known affected: 424 recommended: 408 | 2026-07-25T16:52:24+00:00 | Vulnerability · Source |
| CVE-2025-1371 | suse_vex | SUSE CVE CVE-2025-1371 | known not affected: 428 | 2026-07-25T16:52:19+00:00 | Vulnerability · Source |
| CVE-2025-1376 | suse_vex | SUSE CVE CVE-2025-1376 | known affected: 241 known not affected: 68 recommended: 308 | 2026-07-25T16:52:17+00:00 | Vulnerability · Source |
| CVE-2025-1390 | suse_vex | SUSE CVE CVE-2025-1390 | known not affected: 209 | 2026-07-25T16:52:16+00:00 | Vulnerability · Source |
| CVE-2025-3549 | suse_vex | SUSE CVE CVE-2025-3549 | known affected: 1031 known not affected: 5 | 2026-07-25T16:52:11+00:00 | Vulnerability · Source |
| CVE-2025-5473 | suse_vex | SUSE CVE CVE-2025-5473 | known affected: 4 recommended: 80 | 2026-07-25T16:52:03+00:00 | Vulnerability · Source |
| CVE-2025-7546 | suse_vex | SUSE CVE CVE-2025-7546 | known affected: 457 recommended: 527 | 2026-07-25T16:51:56+00:00 | Vulnerability · Source |
| CVE-2025-8129 | suse_vex | SUSE CVE CVE-2025-8129 | known not affected: 274 | 2026-07-25T16:51:55+00:00 | Vulnerability · Source |
| CVE-2025-8534 | suse_vex | SUSE CVE CVE-2025-8534 | known affected: 516 recommended: 98 | 2026-07-25T16:51:53+00:00 | Vulnerability · Source |
| CVE-2025-8732 | suse_vex | SUSE CVE CVE-2025-8732 | known affected: 557 known not affected: 405 recommended: 166 | 2026-07-25T16:51:51+00:00 | Vulnerability · Source |
| CVE-2025-9165 | suse_vex | SUSE CVE CVE-2025-9165 | known affected: 516 known not affected: 49 recommended: 100 | 2026-07-25T16:51:50+00:00 | Vulnerability · Source |
| CVE-2025-9389 | suse_vex | SUSE CVE CVE-2025-9389 | known not affected: 241 | 2026-07-25T16:51:48+00:00 | Vulnerability · Source |
| CVE-2025-11021 | suse_vex | SUSE CVE CVE-2025-11021 | known not affected: 251 recommended: 122 | 2026-07-25T16:51:46+00:00 | Vulnerability · Source |
| CVE-2025-11709 | suse_vex | SUSE CVE CVE-2025-11709 | known affected: 70 recommended: 185 | 2026-07-25T16:51:44+00:00 | Vulnerability · Source |
| CVE-2025-12200 | suse_vex | SUSE CVE CVE-2025-12200 | known not affected: 53 | 2026-07-25T16:51:43+00:00 | Vulnerability · Source |
| CVE-2025-15281 | suse_vex | SUSE CVE CVE-2025-15281 | first fixed: 1 known affected: 492 known not affected: 64 recommended: 778 | 2026-07-25T16:51:35+00:00 | Vulnerability · Source |
| CVE-2025-20012 | suse_vex | SUSE CVE CVE-2025-20012 | known affected: 10 recommended: 46 | 2026-07-25T16:51:33+00:00 | Vulnerability · Source |
| CVE-2025-21816 | suse_vex | SUSE CVE CVE-2025-21816 | first fixed: 2 known affected: 453 known not affected: 331 recommended: 154 | 2026-07-25T16:51:28+00:00 | Vulnerability · Source |
| CVE-2025-22134 | suse_vex | SUSE CVE CVE-2025-22134 | known affected: 474 known not affected: 3 recommended: 162 | 2026-07-25T16:51:23+00:00 | Vulnerability · Source |
| CVE-2025-37762 | suse_vex | SUSE CVE CVE-2025-37762 | known not affected: 397 | 2026-07-25T16:51:12+00:00 | Vulnerability · Source |
| CVE-2025-37878 | suse_vex | SUSE CVE CVE-2025-37878 | known not affected: 442 recommended: 53 | 2026-07-25T16:51:08+00:00 | Vulnerability · Source |
| CVE-2025-38196 | suse_vex | SUSE CVE CVE-2025-38196 | known not affected: 416 | 2026-07-25T16:50:59+00:00 | Vulnerability · Source |
| CVE-2025-38309 | suse_vex | SUSE CVE CVE-2025-38309 | known not affected: 416 | 2026-07-25T16:50:56+00:00 | Vulnerability · Source |
| CVE-2025-38368 | suse_vex | SUSE CVE CVE-2025-38368 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T16:50:54+00:00 | Vulnerability · Source |