VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
97904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-42141 | suse_vex | SUSE CVE CVE-2024-42141 | known affected: 394 known not affected: 326 recommended: 355 | 2026-10-16T13:12:46+00:00 | Vulnerability · Source |
| CVE-2024-42148 | suse_vex | SUSE CVE CVE-2024-42148 | known affected: 592 recommended: 741 | 2026-10-16T13:12:44+00:00 | Vulnerability · Source |
| CVE-2024-42242 | suse_vex | SUSE CVE CVE-2024-42242 | known not affected: 371 | 2026-10-16T13:12:41+00:00 | Vulnerability · Source |
| CVE-2024-42250 | suse_vex | SUSE CVE CVE-2024-42250 | known affected: 394 known not affected: 316 recommended: 355 | 2026-10-16T13:12:39+00:00 | Vulnerability · Source |
| CVE-2024-42254 | suse_vex | SUSE CVE CVE-2024-42254 | known not affected: 371 recommended: 47 | 2026-10-16T13:12:37+00:00 | Vulnerability · Source |
| CVE-2024-42263 | suse_vex | SUSE CVE CVE-2024-42263 | known not affected: 371 recommended: 47 | 2026-10-16T13:12:35+00:00 | Vulnerability · Source |
| CVE-2024-42299 | suse_vex | SUSE CVE CVE-2024-42299 | known not affected: 604 | 2026-10-16T13:12:32+00:00 | Vulnerability · Source |
| CVE-2024-42315 | suse_vex | SUSE CVE CVE-2024-42315 | known affected: 340 known not affected: 260 recommended: 729 | 2026-10-16T13:12:30+00:00 | Vulnerability · Source |
| CVE-2024-43820 | suse_vex | SUSE CVE CVE-2024-43820 | known affected: 410 known not affected: 379 recommended: 349 | 2026-10-16T13:12:26+00:00 | Vulnerability · Source |
| CVE-2024-43821 | suse_vex | SUSE CVE CVE-2024-43821 | known affected: 450 known not affected: 176 recommended: 729 | 2026-10-16T13:12:24+00:00 | Vulnerability · Source |
| CVE-2024-43832 | suse_vex | SUSE CVE CVE-2024-43832 | known affected: 540 known not affected: 254 recommended: 352 | 2026-10-16T13:12:22+00:00 | Vulnerability · Source |
| CVE-2024-43857 | suse_vex | SUSE CVE CVE-2024-43857 | known not affected: 371 | 2026-10-16T13:12:19+00:00 | Vulnerability · Source |
| CVE-2024-43870 | suse_vex | SUSE CVE CVE-2024-43870 | known affected: 394 known not affected: 404 recommended: 352 | 2026-10-16T13:12:18+00:00 | Vulnerability · Source |
| CVE-2024-43874 | suse_vex | SUSE CVE CVE-2024-43874 | known affected: 394 known not affected: 322 recommended: 355 | 2026-10-16T13:12:16+00:00 | Vulnerability · Source |
| CVE-2024-43887 | suse_vex | SUSE CVE CVE-2024-43887 | known not affected: 371 | 2026-10-16T13:12:14+00:00 | Vulnerability · Source |
| CVE-2024-44949 | suse_vex | SUSE CVE CVE-2024-44949 | known not affected: 399 | 2026-10-16T13:12:11+00:00 | Vulnerability · Source |
| CVE-2024-44952 | suse_vex | SUSE CVE CVE-2024-44952 | known affected: 349 known not affected: 284 recommended: 810 | 2026-10-16T13:12:09+00:00 | Vulnerability · Source |
| CVE-2024-44962 | suse_vex | SUSE CVE CVE-2024-44962 | known affected: 394 known not affected: 350 recommended: 352 | 2026-10-16T13:12:07+00:00 | Vulnerability · Source |
| CVE-2024-44986 | suse_vex | SUSE CVE CVE-2024-44986 | known affected: 410 known not affected: 282 recommended: 640 | 2026-10-16T13:12:05+00:00 | Vulnerability · Source |
| CVE-2024-45005 | suse_vex | SUSE CVE CVE-2024-45005 | known affected: 394 known not affected: 350 recommended: 352 | 2026-10-16T13:12:03+00:00 | Vulnerability · Source |
| CVE-2024-45019 | suse_vex | SUSE CVE CVE-2024-45019 | known affected: 364 known not affected: 406 recommended: 453 | 2026-10-16T13:12:01+00:00 | Vulnerability · Source |
| CVE-2024-45022 | suse_vex | SUSE CVE CVE-2024-45022 | known affected: 394 known not affected: 432 recommended: 438 | 2026-10-16T13:11:58+00:00 | Vulnerability · Source |
| CVE-2024-45027 | suse_vex | SUSE CVE CVE-2024-45027 | known not affected: 399 recommended: 47 | 2026-10-16T13:11:56+00:00 | Vulnerability · Source |
| CVE-2024-45306 | suse_vex | SUSE CVE CVE-2024-45306 | known affected: 543 known not affected: 4 recommended: 158 | 2026-10-16T13:11:55+00:00 | Vulnerability · Source |
| CVE-2024-45506 | suse_vex | SUSE CVE CVE-2024-45506 | known not affected: 13 recommended: 3 | 2026-10-16T13:11:52+00:00 | Vulnerability · Source |
| CVE-2024-45618 | suse_vex | SUSE CVE CVE-2024-45618 | known affected: 435 recommended: 38 | 2026-10-16T13:11:50+00:00 | Vulnerability · Source |
| CVE-2024-45679 | suse_vex | SUSE CVE CVE-2024-45679 | recommended: 9 | 2026-10-16T13:11:49+00:00 | Vulnerability · Source |
| CVE-2024-45811 | suse_vex | SUSE CVE CVE-2024-45811 | recommended: 22 | 2026-10-16T13:11:46+00:00 | Vulnerability · Source |
| CVE-2024-46693 | suse_vex | SUSE CVE CVE-2024-46693 | known affected: 394 known not affected: 432 recommended: 352 | 2026-10-16T13:11:43+00:00 | Vulnerability · Source |
| CVE-2024-46700 | suse_vex | SUSE CVE CVE-2024-46700 | known not affected: 400 recommended: 47 | 2026-10-16T13:11:42+00:00 | Vulnerability · Source |
| CVE-2024-46707 | suse_vex | SUSE CVE CVE-2024-46707 | known affected: 648 known not affected: 43 recommended: 710 | 2026-10-16T13:11:40+00:00 | Vulnerability · Source |
| CVE-2024-46720 | suse_vex | SUSE CVE CVE-2024-46720 | known affected: 340 known not affected: 289 recommended: 652 | 2026-10-16T13:11:38+00:00 | Vulnerability · Source |
| CVE-2024-46721 | suse_vex | SUSE CVE CVE-2024-46721 | known affected: 598 known not affected: 38 recommended: 733 | 2026-10-16T13:11:36+00:00 | Vulnerability · Source |
| CVE-2024-46780 | suse_vex | SUSE CVE CVE-2024-46780 | known affected: 484 known not affected: 237 recommended: 640 | 2026-10-16T13:11:30+00:00 | Vulnerability · Source |
| CVE-2024-46788 | suse_vex | SUSE CVE CVE-2024-46788 | known affected: 394 known not affected: 344 recommended: 280 | 2026-10-16T13:11:28+00:00 | Vulnerability · Source |
| CVE-2024-46808 | suse_vex | SUSE CVE CVE-2024-46808 | known not affected: 307 recommended: 47 | 2026-10-16T13:11:25+00:00 | Vulnerability · Source |
| CVE-2024-46837 | suse_vex | SUSE CVE CVE-2024-46837 | known not affected: 399 recommended: 47 | 2026-10-16T13:11:23+00:00 | Vulnerability · Source |
| CVE-2024-46844 | suse_vex | SUSE CVE CVE-2024-46844 | known not affected: 610 | 2026-10-16T13:11:21+00:00 | Vulnerability · Source |
| CVE-2024-46845 | suse_vex | SUSE CVE CVE-2024-46845 | known affected: 394 known not affected: 345 recommended: 280 | 2026-10-16T13:11:19+00:00 | Vulnerability · Source |
| CVE-2024-46848 | suse_vex | SUSE CVE CVE-2024-46848 | known affected: 669 known not affected: 16 recommended: 672 | 2026-10-16T13:11:18+00:00 | Vulnerability · Source |
| CVE-2024-46851 | suse_vex | SUSE CVE CVE-2024-46851 | known affected: 394 known not affected: 345 recommended: 361 | 2026-10-16T13:11:16+00:00 | Vulnerability · Source |
| CVE-2024-46856 | suse_vex | SUSE CVE CVE-2024-46856 | known not affected: 400 | 2026-10-16T13:11:14+00:00 | Vulnerability · Source |
| CVE-2024-46863 | suse_vex | SUSE CVE CVE-2024-46863 | known not affected: 399 recommended: 47 | 2026-10-16T13:11:13+00:00 | Vulnerability · Source |
| CVE-2024-46864 | suse_vex | SUSE CVE CVE-2024-46864 | known affected: 354 known not affected: 282 recommended: 673 | 2026-10-16T13:11:11+00:00 | Vulnerability · Source |
| CVE-2024-46954 | suse_vex | SUSE CVE CVE-2024-46954 | known not affected: 157 recommended: 35 | 2026-10-16T13:11:09+00:00 | Vulnerability · Source |
| CVE-2024-47067 | suse_vex | SUSE CVE CVE-2024-47067 | recommended: 4 | 2026-10-16T13:11:08+00:00 | Vulnerability · Source |
| CVE-2024-47182 | suse_vex | SUSE CVE CVE-2024-47182 | recommended: 4 | 2026-10-16T13:11:06+00:00 | Vulnerability · Source |
| CVE-2024-47538 | suse_vex | SUSE CVE CVE-2024-47538 | known affected: 605 recommended: 1025 | 2026-10-16T13:11:05+00:00 | Vulnerability · Source |
| CVE-2024-47602 | suse_vex | SUSE CVE CVE-2024-47602 | known affected: 52 known not affected: 1 recommended: 102 | 2026-10-16T13:11:03+00:00 | Vulnerability · Source |
| CVE-2024-47603 | suse_vex | SUSE CVE CVE-2024-47603 | known affected: 52 known not affected: 1 recommended: 102 | 2026-10-16T13:11:01+00:00 | Vulnerability · Source |