VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286572 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-53130 | suse_vex | SUSE CVE CVE-2024-53130 | known affected: 629 known not affected: 82 recommended: 420 | 2026-07-31T01:25:18+00:00 | Vulnerability · Source |
| CVE-2024-53140 | suse_vex | SUSE CVE CVE-2024-53140 | known affected: 720 known not affected: 6 recommended: 382 | 2026-07-31T01:25:16+00:00 | Vulnerability · Source |
| CVE-2024-53174 | suse_vex | SUSE CVE CVE-2024-53174 | known affected: 629 known not affected: 76 recommended: 507 | 2026-07-31T01:25:11+00:00 | Vulnerability · Source |
| CVE-2024-53182 | suse_vex | SUSE CVE CVE-2024-53182 | known not affected: 437 recommended: 53 | 2026-07-31T01:25:09+00:00 | Vulnerability · Source |
| CVE-2024-53351 | suse_vex | SUSE CVE CVE-2024-53351 | recommended: 3 | 2026-07-31T01:25:03+00:00 | Vulnerability · Source |
| CVE-2024-53412 | suse_vex | SUSE CVE CVE-2024-53412 | No product status | 2026-07-31T01:25:01+00:00 | Vulnerability · Source |
| CVE-2024-53680 | suse_vex | SUSE CVE CVE-2024-53680 | known affected: 669 recommended: 476 | 2026-07-31T01:24:59+00:00 | Vulnerability · Source |
| CVE-2024-53687 | suse_vex | SUSE CVE CVE-2024-53687 | known not affected: 275 | 2026-07-31T01:24:57+00:00 | Vulnerability · Source |
| CVE-2024-53690 | suse_vex | SUSE CVE CVE-2024-53690 | known affected: 364 known not affected: 333 recommended: 411 | 2026-07-31T01:24:55+00:00 | Vulnerability · Source |
| CVE-2024-54551 | suse_vex | SUSE CVE CVE-2024-54551 | known affected: 88 recommended: 592 | 2026-07-31T01:24:54+00:00 | Vulnerability · Source |
| CVE-2024-54683 | suse_vex | SUSE CVE CVE-2024-54683 | known affected: 669 recommended: 435 | 2026-07-31T01:24:52+00:00 | Vulnerability · Source |
| CVE-2024-56557 | suse_vex | SUSE CVE CVE-2024-56557 | known affected: 423 known not affected: 295 recommended: 464 | 2026-07-31T01:24:47+00:00 | Vulnerability · Source |
| CVE-2024-56558 | suse_vex | SUSE CVE CVE-2024-56558 | known affected: 439 known not affected: 167 recommended: 763 | 2026-07-31T01:24:45+00:00 | Vulnerability · Source |
| CVE-2024-56559 | suse_vex | SUSE CVE CVE-2024-56559 | known not affected: 545 | 2026-07-31T01:24:44+00:00 | Vulnerability · Source |
| CVE-2024-56564 | suse_vex | SUSE CVE CVE-2024-56564 | known not affected: 545 | 2026-07-31T01:24:43+00:00 | Vulnerability · Source |
| CVE-2024-56565 | suse_vex | SUSE CVE CVE-2024-56565 | known not affected: 545 | 2026-07-31T01:24:41+00:00 | Vulnerability · Source |
| CVE-2024-56581 | suse_vex | SUSE CVE CVE-2024-56581 | known affected: 267 known not affected: 300 | 2026-07-31T01:24:39+00:00 | Vulnerability · Source |
| CVE-2024-56585 | suse_vex | SUSE CVE CVE-2024-56585 | known not affected: 545 | 2026-07-31T01:24:37+00:00 | Vulnerability · Source |
| CVE-2024-56586 | suse_vex | SUSE CVE CVE-2024-56586 | known not affected: 545 | 2026-07-31T01:24:35+00:00 | Vulnerability · Source |
| CVE-2024-56592 | suse_vex | SUSE CVE CVE-2024-56592 | known affected: 695 known not affected: 112 recommended: 363 | 2026-07-31T01:24:33+00:00 | Vulnerability · Source |
| CVE-2024-56595 | suse_vex | SUSE CVE CVE-2024-56595 | known affected: 597 known not affected: 182 recommended: 411 | 2026-07-31T01:24:31+00:00 | Vulnerability · Source |
| CVE-2024-56596 | suse_vex | SUSE CVE CVE-2024-56596 | known affected: 545 known not affected: 224 recommended: 411 | 2026-07-31T01:24:29+00:00 | Vulnerability · Source |
| CVE-2024-56598 | suse_vex | SUSE CVE CVE-2024-56598 | known affected: 405 known not affected: 286 recommended: 557 | 2026-07-31T01:24:27+00:00 | Vulnerability · Source |
| CVE-2024-56619 | suse_vex | SUSE CVE CVE-2024-56619 | known affected: 405 known not affected: 274 recommended: 557 | 2026-07-31T01:24:23+00:00 | Vulnerability · Source |
| CVE-2024-56626 | suse_vex | SUSE CVE CVE-2024-56626 | known not affected: 534 | 2026-07-31T01:24:20+00:00 | Vulnerability · Source |
| CVE-2024-56628 | suse_vex | SUSE CVE CVE-2024-56628 | known not affected: 534 | 2026-07-31T01:24:18+00:00 | Vulnerability · Source |
| CVE-2024-56640 | suse_vex | SUSE CVE CVE-2024-56640 | known affected: 721 known not affected: 24 recommended: 421 | 2026-07-31T01:24:14+00:00 | Vulnerability · Source |
| CVE-2024-56673 | suse_vex | SUSE CVE CVE-2024-56673 | known not affected: 545 | 2026-07-31T01:24:07+00:00 | Vulnerability · Source |
| CVE-2024-56688 | suse_vex | SUSE CVE CVE-2024-56688 | known affected: 677 known not affected: 68 recommended: 432 | 2026-07-31T01:24:01+00:00 | Vulnerability · Source |
| CVE-2024-56710 | suse_vex | SUSE CVE CVE-2024-56710 | known not affected: 532 | 2026-07-31T01:23:58+00:00 | Vulnerability · Source |
| CVE-2024-56746 | suse_vex | SUSE CVE CVE-2024-56746 | known affected: 394 known not affected: 365 recommended: 363 | 2026-07-31T01:23:52+00:00 | Vulnerability · Source |
| CVE-2024-56768 | suse_vex | SUSE CVE CVE-2024-56768 | known not affected: 474 | 2026-07-31T01:23:49+00:00 | Vulnerability · Source |
| CVE-2024-56770 | suse_vex | SUSE CVE CVE-2024-56770 | known affected: 537 known not affected: 6 recommended: 720 | 2026-07-31T01:23:47+00:00 | Vulnerability · Source |
| CVE-2024-56785 | suse_vex | SUSE CVE CVE-2024-56785 | known not affected: 474 | 2026-07-31T01:23:44+00:00 | Vulnerability · Source |
| CVE-2024-57843 | suse_vex | SUSE CVE CVE-2024-57843 | known not affected: 453 recommended: 43 | 2026-07-31T01:23:39+00:00 | Vulnerability · Source |
| CVE-2024-57850 | suse_vex | SUSE CVE CVE-2024-57850 | known affected: 366 known not affected: 292 recommended: 425 | 2026-07-31T01:23:38+00:00 | Vulnerability · Source |
| CVE-2024-57872 | suse_vex | SUSE CVE CVE-2024-57872 | known affected: 167 known not affected: 6 | 2026-07-31T01:23:36+00:00 | Vulnerability · Source |
| CVE-2024-57885 | suse_vex | SUSE CVE CVE-2024-57885 | known not affected: 453 recommended: 43 | 2026-07-31T01:23:34+00:00 | Vulnerability · Source |
| CVE-2024-57886 | suse_vex | SUSE CVE CVE-2024-57886 | known not affected: 453 | 2026-07-31T01:23:33+00:00 | Vulnerability · Source |
| CVE-2024-57895 | suse_vex | SUSE CVE CVE-2024-57895 | known not affected: 453 | 2026-07-31T01:23:30+00:00 | Vulnerability · Source |
| CVE-2024-57924 | suse_vex | SUSE CVE CVE-2024-57924 | known affected: 705 recommended: 421 | 2026-07-31T01:23:27+00:00 | Vulnerability · Source |
| CVE-2024-57925 | suse_vex | SUSE CVE CVE-2024-57925 | known not affected: 453 | 2026-07-31T01:23:25+00:00 | Vulnerability · Source |
| CVE-2024-57939 | suse_vex | SUSE CVE CVE-2024-57939 | known not affected: 453 | 2026-07-31T01:23:22+00:00 | Vulnerability · Source |
| CVE-2024-57945 | suse_vex | SUSE CVE CVE-2024-57945 | known not affected: 453 | 2026-07-31T01:23:20+00:00 | Vulnerability · Source |
| CVE-2024-57948 | suse_vex | SUSE CVE CVE-2024-57948 | known affected: 381 known not affected: 153 recommended: 588 | 2026-07-31T01:23:18+00:00 | Vulnerability · Source |
| CVE-2024-57977 | suse_vex | SUSE CVE CVE-2024-57977 | known not affected: 459 recommended: 42 | 2026-07-31T01:23:16+00:00 | Vulnerability · Source |
| CVE-2024-58010 | suse_vex | SUSE CVE CVE-2024-58010 | known not affected: 461 | 2026-07-31T01:23:14+00:00 | Vulnerability · Source |
| CVE-2024-58015 | suse_vex | SUSE CVE CVE-2024-58015 | known affected: 579 known not affected: 234 recommended: 247 | 2026-07-31T01:23:13+00:00 | Vulnerability · Source |
| CVE-2024-58016 | suse_vex | SUSE CVE CVE-2024-58016 | known not affected: 461 | 2026-07-31T01:23:11+00:00 | Vulnerability · Source |
| CVE-2024-58058 | suse_vex | SUSE CVE CVE-2024-58058 | known affected: 533 known not affected: 257 recommended: 309 | 2026-07-31T01:23:09+00:00 | Vulnerability · Source |