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-54661 | suse_vex | SUSE CVE CVE-2024-54661 | known affected: 369 recommended: 107 | 2026-10-16T01:23:18+00:00 | Vulnerability · Source |
| CVE-2024-54677 | suse_vex | SUSE CVE CVE-2024-54677 | known affected: 639 recommended: 379 | 2026-10-16T01:23:16+00:00 | Vulnerability · Source |
| CVE-2024-54680 | suse_vex | SUSE CVE CVE-2024-54680 | known affected: 4 known not affected: 288 recommended: 639 | 2026-10-16T01:23:14+00:00 | Vulnerability · Source |
| CVE-2024-54683 | suse_vex | SUSE CVE CVE-2024-54683 | known affected: 763 recommended: 455 | 2026-10-16T01:23:11+00:00 | Vulnerability · Source |
| CVE-2024-55196 | suse_vex | SUSE CVE CVE-2024-55196 | recommended: 5 | 2026-10-16T01:23:10+00:00 | Vulnerability · Source |
| CVE-2024-55549 | suse_vex | SUSE CVE CVE-2024-55549 | known affected: 475 known not affected: 14 recommended: 147 | 2026-10-16T01:23:08+00:00 | Vulnerability · Source |
| CVE-2024-55639 | suse_vex | SUSE CVE CVE-2024-55639 | known affected: 410 known not affected: 424 recommended: 389 | 2026-10-16T01:23:06+00:00 | Vulnerability · Source |
| CVE-2024-55641 | suse_vex | SUSE CVE CVE-2024-55641 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-16T01:23:04+00:00 | Vulnerability · Source |
| CVE-2024-55642 | suse_vex | SUSE CVE CVE-2024-55642 | known affected: 0 known not affected: 456 recommended: 109 | 2026-10-16T01:23:03+00:00 | Vulnerability · Source |
| CVE-2024-55658 | suse_vex | SUSE CVE CVE-2024-55658 | recommended: 4 | 2026-10-16T01:23:01+00:00 | Vulnerability · Source |
| CVE-2024-55659 | suse_vex | SUSE CVE CVE-2024-55659 | recommended: 4 | 2026-10-16T01:23:00+00:00 | Vulnerability · Source |
| CVE-2024-55885 | suse_vex | SUSE CVE CVE-2024-55885 | recommended: 4 | 2026-10-16T01:22:58+00:00 | Vulnerability · Source |
| CVE-2024-55947 | suse_vex | SUSE CVE CVE-2024-55947 | recommended: 5 | 2026-10-16T01:22:56+00:00 | Vulnerability · Source |
| CVE-2024-56138 | suse_vex | SUSE CVE CVE-2024-56138 | recommended: 5 | 2026-10-16T01:22:54+00:00 | Vulnerability · Source |
| CVE-2024-56171 | suse_vex | SUSE CVE CVE-2024-56171 | known affected: 468 known not affected: 21 recommended: 293 | 2026-10-16T01:22:53+00:00 | Vulnerability · Source |
| CVE-2024-56201 | suse_vex | SUSE CVE CVE-2024-56201 | known affected: 404 known not affected: 108 recommended: 134 | 2026-10-16T01:22:51+00:00 | Vulnerability · Source |
| CVE-2024-56323 | suse_vex | SUSE CVE CVE-2024-56323 | recommended: 5 | 2026-10-16T01:22:49+00:00 | Vulnerability · Source |
| CVE-2024-56369 | suse_vex | SUSE CVE CVE-2024-56369 | known affected: 747 known not affected: 62 recommended: 415 | 2026-10-16T01:22:47+00:00 | Vulnerability · Source |
| CVE-2024-56372 | suse_vex | SUSE CVE CVE-2024-56372 | known affected: 410 known not affected: 424 recommended: 389 | 2026-10-16T01:22:45+00:00 | Vulnerability · Source |
| CVE-2024-56378 | suse_vex | SUSE CVE CVE-2024-56378 | known affected: 373 recommended: 178 | 2026-10-16T01:22:43+00:00 | Vulnerability · Source |
| CVE-2024-56406 | suse_vex | SUSE CVE CVE-2024-56406 | known affected: 394 known not affected: 256 recommended: 21 | 2026-10-16T01:22:42+00:00 | Vulnerability · Source |
| CVE-2024-56431 | suse_vex | SUSE CVE CVE-2024-56431 | known affected: 553 known not affected: 386 recommended: 81 | 2026-10-16T01:22:40+00:00 | Vulnerability · Source |
| CVE-2024-56433 | suse_vex | SUSE CVE CVE-2024-56433 | recommended: 6 | 2026-10-16T01:22:38+00:00 | Vulnerability · Source |
| CVE-2024-56513 | suse_vex | SUSE CVE CVE-2024-56513 | recommended: 5 | 2026-10-16T01:22:36+00:00 | Vulnerability · Source |
| CVE-2024-56514 | suse_vex | SUSE CVE CVE-2024-56514 | recommended: 5 | 2026-10-16T01:22:34+00:00 | Vulnerability · Source |
| CVE-2024-56515 | suse_vex | SUSE CVE CVE-2024-56515 | recommended: 5 | 2026-10-16T01:22:33+00:00 | Vulnerability · Source |
| CVE-2024-56534 | suse_vex | SUSE CVE CVE-2024-56534 | known not affected: 547 recommended: 78 | 2026-10-16T01:22:31+00:00 | Vulnerability · Source |
| CVE-2024-56535 | suse_vex | SUSE CVE CVE-2024-56535 | known not affected: 547 recommended: 164 | 2026-10-16T01:22:29+00:00 | Vulnerability · Source |
| CVE-2024-56536 | suse_vex | SUSE CVE CVE-2024-56536 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-16T01:22:27+00:00 | Vulnerability · Source |
| CVE-2024-56537 | suse_vex | SUSE CVE CVE-2024-56537 | known not affected: 547 recommended: 125 | 2026-10-16T01:22:25+00:00 | Vulnerability · Source |
| CVE-2024-56539 | suse_vex | SUSE CVE CVE-2024-56539 | known affected: 519 known not affected: 73 recommended: 758 | 2026-10-16T01:22:23+00:00 | Vulnerability · Source |
| CVE-2024-56541 | suse_vex | SUSE CVE CVE-2024-56541 | known affected: 394 known not affected: 547 recommended: 171 | 2026-10-16T01:22:21+00:00 | Vulnerability · Source |
| CVE-2024-56543 | suse_vex | SUSE CVE CVE-2024-56543 | known affected: 394 known not affected: 482 recommended: 358 | 2026-10-16T01:22:19+00:00 | Vulnerability · Source |
| CVE-2024-56544 | suse_vex | SUSE CVE CVE-2024-56544 | known not affected: 547 recommended: 164 | 2026-10-16T01:22:17+00:00 | Vulnerability · Source |
| CVE-2024-56545 | suse_vex | SUSE CVE CVE-2024-56545 | known not affected: 547 recommended: 78 | 2026-10-16T01:22:16+00:00 | Vulnerability · Source |
| CVE-2024-56552 | suse_vex | SUSE CVE CVE-2024-56552 | known not affected: 547 recommended: 125 | 2026-10-16T01:22:14+00:00 | Vulnerability · Source |
| CVE-2024-56560 | suse_vex | SUSE CVE CVE-2024-56560 | known not affected: 547 recommended: 78 | 2026-10-16T01:22:12+00:00 | Vulnerability · Source |
| CVE-2024-56562 | suse_vex | SUSE CVE CVE-2024-56562 | known affected: 515 known not affected: 278 recommended: 545 | 2026-10-16T01:22:10+00:00 | Vulnerability · Source |
| CVE-2024-56563 | suse_vex | SUSE CVE CVE-2024-56563 | known not affected: 547 recommended: 78 | 2026-10-16T01:22:08+00:00 | Vulnerability · Source |
| CVE-2024-56564 | suse_vex | SUSE CVE CVE-2024-56564 | known not affected: 648 | 2026-10-16T01:22:06+00:00 | Vulnerability · Source |
| CVE-2024-56565 | suse_vex | SUSE CVE CVE-2024-56565 | known not affected: 648 | 2026-10-16T01:22:04+00:00 | Vulnerability · Source |
| CVE-2024-56567 | suse_vex | SUSE CVE CVE-2024-56567 | known affected: 515 known not affected: 278 recommended: 459 | 2026-10-16T01:22:02+00:00 | Vulnerability · Source |
| CVE-2024-56569 | suse_vex | SUSE CVE CVE-2024-56569 | known affected: 394 known not affected: 482 recommended: 384 | 2026-10-16T01:22:00+00:00 | Vulnerability · Source |
| CVE-2024-56570 | suse_vex | SUSE CVE CVE-2024-56570 | known affected: 639 known not affected: 38 recommended: 717 | 2026-10-16T01:21:58+00:00 | Vulnerability · Source |
| CVE-2024-56571 | suse_vex | SUSE CVE CVE-2024-56571 | known affected: 354 known not affected: 16 recommended: 468 | 2026-10-16T01:21:56+00:00 | Vulnerability · Source |
| CVE-2024-56572 | suse_vex | SUSE CVE CVE-2024-56572 | known affected: 666 known not affected: 221 recommended: 358 | 2026-10-16T01:21:54+00:00 | Vulnerability · Source |
| CVE-2024-56573 | suse_vex | SUSE CVE CVE-2024-56573 | known affected: 394 known not affected: 494 recommended: 358 | 2026-10-16T01:21:52+00:00 | Vulnerability · Source |
| CVE-2024-56574 | suse_vex | SUSE CVE CVE-2024-56574 | known affected: 813 known not affected: 34 recommended: 398 | 2026-10-16T01:21:50+00:00 | Vulnerability · Source |
| CVE-2024-56578 | suse_vex | SUSE CVE CVE-2024-56578 | known affected: 582 known not affected: 305 recommended: 358 | 2026-10-16T01:21:48+00:00 | Vulnerability · Source |
| CVE-2024-56579 | suse_vex | SUSE CVE CVE-2024-56579 | known affected: 394 known not affected: 494 recommended: 358 | 2026-10-16T01:21:46+00:00 | Vulnerability · Source |