VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-50299 | suse_vex | SUSE CVE CVE-2024-50299 | known affected: 394 known not affected: 398 recommended: 477 | 2026-10-16T01:28:10+00:00 | Vulnerability · Source |
| CVE-2024-50301 | suse_vex | SUSE CVE CVE-2024-50301 | known affected: 460 known not affected: 39 recommended: 991 | 2026-10-16T01:28:08+00:00 | Vulnerability · Source |
| CVE-2024-50302 | suse_vex | SUSE CVE CVE-2024-50302 | known affected: 447 known not affected: 92 recommended: 1062 | 2026-10-16T01:28:06+00:00 | Vulnerability · Source |
| CVE-2024-50304 | suse_vex | SUSE CVE CVE-2024-50304 | known affected: 791 known not affected: 38 recommended: 406 | 2026-10-16T01:28:04+00:00 | Vulnerability · Source |
| CVE-2024-50349 | suse_vex | SUSE CVE CVE-2024-50349 | known affected: 208 known not affected: 126 recommended: 450 | 2026-10-16T01:28:02+00:00 | Vulnerability · Source |
| CVE-2024-50379 | suse_vex | SUSE CVE CVE-2024-50379 | known affected: 639 recommended: 387 | 2026-10-16T01:28:00+00:00 | Vulnerability · Source |
| CVE-2024-50602 | suse_vex | SUSE CVE CVE-2024-50602 | known affected: 657 known not affected: 10296 recommended: 290 | 2026-10-16T01:27:57+00:00 | Vulnerability · Source |
| CVE-2024-50612 | suse_vex | SUSE CVE CVE-2024-50612 | known not affected: 192 recommended: 15 | 2026-10-16T01:27:55+00:00 | Vulnerability · Source |
| CVE-2024-50948 | suse_vex | SUSE CVE CVE-2024-50948 | recommended: 4 | 2026-10-16T01:27:54+00:00 | Vulnerability · Source |
| CVE-2024-51491 | suse_vex | SUSE CVE CVE-2024-51491 | recommended: 5 | 2026-10-16T01:27:52+00:00 | Vulnerability · Source |
| CVE-2024-51735 | suse_vex | SUSE CVE CVE-2024-51735 | recommended: 4 | 2026-10-16T01:27:50+00:00 | Vulnerability · Source |
| CVE-2024-51741 | suse_vex | SUSE CVE CVE-2024-51741 | known affected: 4 known not affected: 26 recommended: 45 | 2026-10-16T01:27:48+00:00 | Vulnerability · Source |
| CVE-2024-51744 | suse_vex | SUSE CVE CVE-2024-51744 | known affected: 475 known not affected: 504 recommended: 168 | 2026-10-16T01:27:46+00:00 | Vulnerability · Source |
| CVE-2024-52003 | suse_vex | SUSE CVE CVE-2024-52003 | recommended: 4 | 2026-10-16T01:27:45+00:00 | Vulnerability · Source |
| CVE-2024-52006 | suse_vex | SUSE CVE CVE-2024-52006 | known affected: 208 known not affected: 126 recommended: 436 | 2026-10-16T01:27:43+00:00 | Vulnerability · Source |
| CVE-2024-52010 | suse_vex | SUSE CVE CVE-2024-52010 | recommended: 4 | 2026-10-16T01:27:42+00:00 | Vulnerability · Source |
| CVE-2024-52011 | suse_vex | SUSE CVE CVE-2024-52011 | known affected: 0 known not affected: 9 | 2026-10-16T01:27:40+00:00 | Vulnerability · Source |
| CVE-2024-52280 | suse_vex | SUSE CVE CVE-2024-52280 | recommended: 4 | 2026-10-16T01:27:38+00:00 | Vulnerability · Source |
| CVE-2024-52281 | suse_vex | SUSE CVE CVE-2024-52281 | recommended: 5 | 2026-10-16T01:27:37+00:00 | Vulnerability · Source |
| CVE-2024-52282 | suse_vex | SUSE CVE CVE-2024-52282 | recommended: 4 | 2026-10-16T01:27:35+00:00 | Vulnerability · Source |
| CVE-2024-52303 | suse_vex | SUSE CVE CVE-2024-52303 | known not affected: 61 recommended: 7 | 2026-10-16T01:27:33+00:00 | Vulnerability · Source |
| CVE-2024-52304 | suse_vex | SUSE CVE CVE-2024-52304 | known affected: 406 recommended: 71 | 2026-10-16T01:27:31+00:00 | Vulnerability · Source |
| CVE-2024-52308 | suse_vex | SUSE CVE CVE-2024-52308 | recommended: 20 | 2026-10-16T01:27:29+00:00 | Vulnerability · Source |
| CVE-2024-52309 | suse_vex | SUSE CVE CVE-2024-52309 | recommended: 4 | 2026-10-16T01:27:28+00:00 | Vulnerability · Source |
| CVE-2024-52316 | suse_vex | SUSE CVE CVE-2024-52316 | known affected: 486 recommended: 426 | 2026-10-16T01:27:26+00:00 | Vulnerability · Source |
| CVE-2024-52319 | suse_vex | SUSE CVE CVE-2024-52319 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-16T01:27:24+00:00 | Vulnerability · Source |
| CVE-2024-52332 | suse_vex | SUSE CVE CVE-2024-52332 | known affected: 747 known not affected: 48 recommended: 512 | 2026-10-16T01:27:22+00:00 | Vulnerability · Source |
| CVE-2024-52336 | suse_vex | SUSE CVE CVE-2024-52336 | known not affected: 68 recommended: 73 | 2026-10-16T01:27:20+00:00 | Vulnerability · Source |
| CVE-2024-52522 | suse_vex | SUSE CVE CVE-2024-52522 | recommended: 19 | 2026-10-16T01:27:19+00:00 | Vulnerability · Source |
| CVE-2024-52529 | suse_vex | SUSE CVE CVE-2024-52529 | recommended: 4 | 2026-10-16T01:27:17+00:00 | Vulnerability · Source |
| CVE-2024-52531 | suse_vex | SUSE CVE CVE-2024-52531 | known affected: 106 recommended: 280 | 2026-10-16T01:27:15+00:00 | Vulnerability · Source |
| CVE-2024-52533 | suse_vex | SUSE CVE CVE-2024-52533 | known affected: 555 known not affected: 7 recommended: 660 | 2026-10-16T01:27:13+00:00 | Vulnerability · Source |
| CVE-2024-52594 | suse_vex | SUSE CVE CVE-2024-52594 | recommended: 5 | 2026-10-16T01:27:12+00:00 | Vulnerability · Source |
| CVE-2024-52602 | suse_vex | SUSE CVE CVE-2024-52602 | recommended: 5 | 2026-10-16T01:27:10+00:00 | Vulnerability · Source |
| CVE-2024-52791 | suse_vex | SUSE CVE CVE-2024-52791 | recommended: 5 | 2026-10-16T01:27:05+00:00 | Vulnerability · Source |
| CVE-2024-52801 | suse_vex | SUSE CVE CVE-2024-52801 | recommended: 4 | 2026-10-16T01:27:03+00:00 | Vulnerability · Source |
| CVE-2024-52804 | suse_vex | SUSE CVE CVE-2024-52804 | known affected: 12 known not affected: 12 recommended: 31 | 2026-10-16T01:27:02+00:00 | Vulnerability · Source |
| CVE-2024-53042 | suse_vex | SUSE CVE CVE-2024-53042 | known affected: 430 known not affected: 457 recommended: 384 | 2026-10-16T01:27:00+00:00 | Vulnerability · Source |
| CVE-2024-53044 | suse_vex | SUSE CVE CVE-2024-53044 | known not affected: 477 recommended: 86 | 2026-10-16T01:26:58+00:00 | Vulnerability · Source |
| CVE-2024-53047 | suse_vex | SUSE CVE CVE-2024-53047 | known not affected: 477 recommended: 86 | 2026-10-16T01:26:56+00:00 | Vulnerability · Source |
| CVE-2024-53056 | suse_vex | SUSE CVE CVE-2024-53056 | known affected: 408 known not affected: 344 recommended: 390 | 2026-10-16T01:26:54+00:00 | Vulnerability · Source |
| CVE-2024-53057 | suse_vex | SUSE CVE CVE-2024-53057 | known affected: 583 known not affected: 16 recommended: 732 | 2026-10-16T01:26:52+00:00 | Vulnerability · Source |
| CVE-2024-53059 | suse_vex | SUSE CVE CVE-2024-53059 | known affected: 387 known not affected: 327 recommended: 635 | 2026-10-16T01:26:50+00:00 | Vulnerability · Source |
| CVE-2024-53063 | suse_vex | SUSE CVE CVE-2024-53063 | known affected: 445 known not affected: 94 recommended: 966 | 2026-10-16T01:26:48+00:00 | Vulnerability · Source |
| CVE-2024-53070 | suse_vex | SUSE CVE CVE-2024-53070 | known affected: 394 known not affected: 450 recommended: 298 | 2026-10-16T01:26:46+00:00 | Vulnerability · Source |
| CVE-2024-53073 | suse_vex | SUSE CVE CVE-2024-53073 | known not affected: 477 | 2026-10-16T01:26:44+00:00 | Vulnerability · Source |
| CVE-2024-53076 | suse_vex | SUSE CVE CVE-2024-53076 | known affected: 394 known not affected: 422 recommended: 280 | 2026-10-16T01:26:42+00:00 | Vulnerability · Source |
| CVE-2024-53088 | suse_vex | SUSE CVE CVE-2024-53088 | known affected: 623 known not affected: 74 recommended: 669 | 2026-10-16T01:26:40+00:00 | Vulnerability · Source |
| CVE-2024-53089 | suse_vex | SUSE CVE CVE-2024-53089 | known not affected: 477 | 2026-10-16T01:26:38+00:00 | Vulnerability · Source |
| CVE-2024-53090 | suse_vex | SUSE CVE CVE-2024-53090 | known affected: 702 known not affected: 102 recommended: 431 | 2026-10-16T01:26:36+00:00 | Vulnerability · Source |