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-50022 | suse_vex | SUSE CVE CVE-2024-50022 | known affected: 398 known not affected: 467 recommended: 484 | 2026-10-16T01:31:33+00:00 | Vulnerability · Source |
| CVE-2024-50023 | suse_vex | SUSE CVE CVE-2024-50023 | known affected: 394 known not affected: 426 recommended: 453 | 2026-10-16T01:31:31+00:00 | Vulnerability · Source |
| CVE-2024-50025 | suse_vex | SUSE CVE CVE-2024-50025 | known affected: 354 known not affected: 368 recommended: 636 | 2026-10-16T01:31:29+00:00 | Vulnerability · Source |
| CVE-2024-50027 | suse_vex | SUSE CVE CVE-2024-50027 | known affected: 398 known not affected: 474 recommended: 453 | 2026-10-16T01:31:27+00:00 | Vulnerability · Source |
| CVE-2024-50028 | suse_vex | SUSE CVE CVE-2024-50028 | known affected: 432 known not affected: 328 recommended: 724 | 2026-10-16T01:31:25+00:00 | Vulnerability · Source |
| CVE-2024-50033 | suse_vex | SUSE CVE CVE-2024-50033 | known affected: 649 known not affected: 38 recommended: 764 | 2026-10-16T01:31:23+00:00 | Vulnerability · Source |
| CVE-2024-50034 | suse_vex | SUSE CVE CVE-2024-50034 | known affected: 394 known not affected: 477 recommended: 99 | 2026-10-16T01:31:21+00:00 | Vulnerability · Source |
| CVE-2024-50035 | suse_vex | SUSE CVE CVE-2024-50035 | known affected: 671 known not affected: 32 recommended: 764 | 2026-10-16T01:31:19+00:00 | Vulnerability · Source |
| CVE-2024-50038 | suse_vex | SUSE CVE CVE-2024-50038 | known affected: 690 recommended: 533 | 2026-10-16T01:31:17+00:00 | Vulnerability · Source |
| CVE-2024-50039 | suse_vex | SUSE CVE CVE-2024-50039 | known affected: 738 known not affected: 32 recommended: 412 | 2026-10-16T01:31:15+00:00 | Vulnerability · Source |
| CVE-2024-50040 | suse_vex | SUSE CVE CVE-2024-50040 | known affected: 398 known not affected: 432 recommended: 404 | 2026-10-16T01:31:13+00:00 | Vulnerability · Source |
| CVE-2024-50044 | suse_vex | SUSE CVE CVE-2024-50044 | known affected: 644 known not affected: 11 recommended: 762 | 2026-10-16T01:31:11+00:00 | Vulnerability · Source |
| CVE-2024-50045 | suse_vex | SUSE CVE CVE-2024-50045 | known affected: 613 known not affected: 74 recommended: 664 | 2026-10-16T01:31:08+00:00 | Vulnerability · Source |
| CVE-2024-50046 | suse_vex | SUSE CVE CVE-2024-50046 | known affected: 432 known not affected: 328 recommended: 724 | 2026-10-16T01:31:06+00:00 | Vulnerability · Source |
| CVE-2024-50047 | suse_vex | SUSE CVE CVE-2024-50047 | known affected: 449 known not affected: 98 recommended: 1009 | 2026-10-16T01:31:04+00:00 | Vulnerability · Source |
| CVE-2024-50048 | suse_vex | SUSE CVE CVE-2024-50048 | known affected: 354 known not affected: 361 recommended: 638 | 2026-10-16T01:31:02+00:00 | Vulnerability · Source |
| CVE-2024-50049 | suse_vex | SUSE CVE CVE-2024-50049 | known affected: 471 known not affected: 251 recommended: 638 | 2026-10-16T01:31:00+00:00 | Vulnerability · Source |
| CVE-2024-50051 | suse_vex | SUSE CVE CVE-2024-50051 | known affected: 364 known not affected: 331 recommended: 490 | 2026-10-16T01:30:58+00:00 | Vulnerability · Source |
| CVE-2024-50052 | suse_vex | SUSE CVE CVE-2024-50052 | recommended: 5 | 2026-10-16T01:30:56+00:00 | Vulnerability · Source |
| CVE-2024-50055 | suse_vex | SUSE CVE CVE-2024-50055 | known affected: 619 known not affected: 4 recommended: 721 | 2026-10-16T01:30:55+00:00 | Vulnerability · Source |
| CVE-2024-50057 | suse_vex | SUSE CVE CVE-2024-50057 | known not affected: 498 recommended: 92 | 2026-10-16T01:30:53+00:00 | Vulnerability · Source |
| CVE-2024-50058 | suse_vex | SUSE CVE CVE-2024-50058 | known affected: 609 known not affected: 46 recommended: 764 | 2026-10-16T01:30:51+00:00 | Vulnerability · Source |
| CVE-2024-50059 | suse_vex | SUSE CVE CVE-2024-50059 | known affected: 365 known not affected: 395 recommended: 638 | 2026-10-16T01:30:49+00:00 | Vulnerability · Source |
| CVE-2024-50060 | suse_vex | SUSE CVE CVE-2024-50060 | known affected: 477 known not affected: 344 recommended: 408 | 2026-10-16T01:30:47+00:00 | Vulnerability · Source |
| CVE-2024-50061 | suse_vex | SUSE CVE CVE-2024-50061 | known affected: 504 known not affected: 218 recommended: 638 | 2026-10-16T01:30:45+00:00 | Vulnerability · Source |
| CVE-2024-50062 | suse_vex | SUSE CVE CVE-2024-50062 | known affected: 464 known not affected: 258 recommended: 636 | 2026-10-16T01:30:43+00:00 | Vulnerability · Source |
| CVE-2024-50063 | suse_vex | SUSE CVE CVE-2024-50063 | known affected: 514 known not affected: 213 recommended: 638 | 2026-10-16T01:30:40+00:00 | Vulnerability · Source |
| CVE-2024-50066 | suse_vex | SUSE CVE CVE-2024-50066 | known not affected: 495 recommended: 6 | 2026-10-16T01:30:39+00:00 | Vulnerability · Source |
| CVE-2024-50070 | suse_vex | SUSE CVE CVE-2024-50070 | known not affected: 477 recommended: 6 | 2026-10-16T01:30:37+00:00 | Vulnerability · Source |
| CVE-2024-50075 | suse_vex | SUSE CVE CVE-2024-50075 | known affected: 394 known not affected: 426 recommended: 453 | 2026-10-16T01:30:35+00:00 | Vulnerability · Source |
| CVE-2024-50076 | suse_vex | SUSE CVE CVE-2024-50076 | known affected: 394 known not affected: 426 recommended: 407 | 2026-10-16T01:30:33+00:00 | Vulnerability · Source |
| CVE-2024-50078 | suse_vex | SUSE CVE CVE-2024-50078 | known affected: 354 known not affected: 368 recommended: 722 | 2026-10-16T01:30:31+00:00 | Vulnerability · Source |
| CVE-2024-50080 | suse_vex | SUSE CVE CVE-2024-50080 | known affected: 398 known not affected: 474 recommended: 366 | 2026-10-16T01:30:28+00:00 | Vulnerability · Source |
| CVE-2024-50081 | suse_vex | SUSE CVE CVE-2024-50081 | known affected: 365 known not affected: 328 recommended: 723 | 2026-10-16T01:30:26+00:00 | Vulnerability · Source |
| CVE-2024-50082 | suse_vex | SUSE CVE CVE-2024-50082 | known affected: 474 known not affected: 42 recommended: 719 | 2026-10-16T01:30:24+00:00 | Vulnerability · Source |
| CVE-2024-50083 | suse_vex | SUSE CVE CVE-2024-50083 | known affected: 520 known not affected: 312 recommended: 335 | 2026-10-16T01:30:22+00:00 | Vulnerability · Source |
| CVE-2024-50089 | suse_vex | SUSE CVE CVE-2024-50089 | known affected: 331 known not affected: 231 recommended: 806 | 2026-10-16T01:30:20+00:00 | Vulnerability · Source |
| CVE-2024-50095 | suse_vex | SUSE CVE CVE-2024-50095 | known affected: 650 known not affected: 52 recommended: 595 | 2026-10-16T01:30:18+00:00 | Vulnerability · Source |
| CVE-2024-50098 | suse_vex | SUSE CVE CVE-2024-50098 | known affected: 456 known not affected: 319 recommended: 555 | 2026-10-16T01:30:16+00:00 | Vulnerability · Source |
| CVE-2024-50108 | suse_vex | SUSE CVE CVE-2024-50108 | known affected: 354 known not affected: 359 recommended: 555 | 2026-10-16T01:30:14+00:00 | Vulnerability · Source |
| CVE-2024-50110 | suse_vex | SUSE CVE CVE-2024-50110 | known affected: 456 known not affected: 319 recommended: 575 | 2026-10-16T01:30:12+00:00 | Vulnerability · Source |
| CVE-2024-50115 | suse_vex | SUSE CVE CVE-2024-50115 | known affected: 445 known not affected: 334 recommended: 1062 | 2026-10-16T01:30:10+00:00 | Vulnerability · Source |
| CVE-2024-50121 | suse_vex | SUSE CVE CVE-2024-50121 | known affected: 394 known not affected: 417 recommended: 372 | 2026-10-16T01:30:08+00:00 | Vulnerability · Source |
| CVE-2024-50127 | suse_vex | SUSE CVE CVE-2024-50127 | known affected: 356 known not affected: 237 recommended: 1008 | 2026-10-16T01:30:06+00:00 | Vulnerability · Source |
| CVE-2024-50128 | suse_vex | SUSE CVE CVE-2024-50128 | known affected: 352 known not affected: 319 recommended: 764 | 2026-10-16T01:30:04+00:00 | Vulnerability · Source |
| CVE-2024-50130 | suse_vex | SUSE CVE CVE-2024-50130 | known affected: 398 known not affected: 465 recommended: 450 | 2026-10-16T01:30:02+00:00 | Vulnerability · Source |
| CVE-2024-50131 | suse_vex | SUSE CVE CVE-2024-50131 | known affected: 497 known not affected: 216 recommended: 555 | 2026-10-16T01:30:00+00:00 | Vulnerability · Source |
| CVE-2024-50134 | suse_vex | SUSE CVE CVE-2024-50134 | known affected: 504 known not affected: 209 recommended: 555 | 2026-10-16T01:29:58+00:00 | Vulnerability · Source |
| CVE-2024-50139 | suse_vex | SUSE CVE CVE-2024-50139 | known affected: 398 known not affected: 470 recommended: 364 | 2026-10-16T01:29:56+00:00 | Vulnerability · Source |
| CVE-2024-50141 | suse_vex | SUSE CVE CVE-2024-50141 | known affected: 354 known not affected: 292 recommended: 641 | 2026-10-16T01:29:54+00:00 | Vulnerability · Source |