VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305209 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-56636 | suse_vex | SUSE CVE CVE-2024-56636 | known affected: 674 known not affected: 235 recommended: 358 | 2026-10-03T16:42:39+00:00 | Vulnerability · Source |
| CVE-2024-56648 | suse_vex | SUSE CVE CVE-2024-56648 | known affected: 409 known not affected: 321 recommended: 658 | 2026-10-03T16:42:36+00:00 | Vulnerability · Source |
| CVE-2024-56656 | suse_vex | SUSE CVE CVE-2024-56656 | known affected: 410 known not affected: 512 recommended: 358 | 2026-10-03T16:42:34+00:00 | Vulnerability · Source |
| CVE-2024-56659 | suse_vex | SUSE CVE CVE-2024-56659 | known affected: 819 known not affected: 32 recommended: 358 | 2026-10-03T16:42:31+00:00 | Vulnerability · Source |
| CVE-2024-56670 | suse_vex | SUSE CVE CVE-2024-56670 | known affected: 791 known not affected: 86 recommended: 358 | 2026-10-03T16:42:28+00:00 | Vulnerability · Source |
| CVE-2024-56675 | suse_vex | SUSE CVE CVE-2024-56675 | known affected: 410 known not affected: 499 recommended: 441 | 2026-10-03T16:42:25+00:00 | Vulnerability · Source |
| CVE-2024-56679 | suse_vex | SUSE CVE CVE-2024-56679 | known affected: 590 known not affected: 319 recommended: 358 | 2026-10-03T16:42:22+00:00 | Vulnerability · Source |
| CVE-2024-56687 | suse_vex | SUSE CVE CVE-2024-56687 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-03T16:42:19+00:00 | Vulnerability · Source |
| CVE-2024-56691 | suse_vex | SUSE CVE CVE-2024-56691 | known affected: 767 known not affected: 118 recommended: 358 | 2026-10-03T16:42:16+00:00 | Vulnerability · Source |
| CVE-2024-56729 | suse_vex | SUSE CVE CVE-2024-56729 | known affected: 590 known not affected: 319 recommended: 401 | 2026-10-03T16:42:12+00:00 | Vulnerability · Source |
| CVE-2024-56741 | suse_vex | SUSE CVE CVE-2024-56741 | known affected: 572 known not affected: 303 recommended: 358 | 2026-10-03T16:42:09+00:00 | Vulnerability · Source |
| CVE-2024-56745 | suse_vex | SUSE CVE CVE-2024-56745 | known affected: 431 known not affected: 338 recommended: 459 | 2026-10-03T16:42:06+00:00 | Vulnerability · Source |
| CVE-2024-56755 | suse_vex | SUSE CVE CVE-2024-56755 | known affected: 418 known not affected: 389 recommended: 468 | 2026-10-03T16:42:04+00:00 | Vulnerability · Source |
| CVE-2024-56766 | suse_vex | SUSE CVE CVE-2024-56766 | known affected: 394 known not affected: 423 recommended: 358 | 2026-10-03T16:41:59+00:00 | Vulnerability · Source |
| CVE-2024-56777 | suse_vex | SUSE CVE CVE-2024-56777 | known affected: 587 known not affected: 157 recommended: 459 | 2026-10-03T16:41:57+00:00 | Vulnerability · Source |
| CVE-2024-56780 | suse_vex | SUSE CVE CVE-2024-56780 | known affected: 539 known not affected: 294 recommended: 358 | 2026-10-03T16:41:54+00:00 | Vulnerability · Source |
| CVE-2024-56787 | suse_vex | SUSE CVE CVE-2024-56787 | known affected: 606 known not affected: 213 recommended: 358 | 2026-10-03T16:41:51+00:00 | Vulnerability · Source |
| CVE-2024-57793 | suse_vex | SUSE CVE CVE-2024-57793 | known affected: 384 known not affected: 359 recommended: 491 | 2026-10-03T16:41:48+00:00 | Vulnerability · Source |
| CVE-2024-57798 | suse_vex | SUSE CVE CVE-2024-57798 | known affected: 356 known not affected: 251 recommended: 709 | 2026-10-03T16:41:46+00:00 | Vulnerability · Source |
| CVE-2024-57809 | suse_vex | SUSE CVE CVE-2024-57809 | known affected: 751 known not affected: 102 recommended: 401 | 2026-10-03T16:41:43+00:00 | Vulnerability · Source |
| CVE-2024-57841 | suse_vex | SUSE CVE CVE-2024-57841 | known affected: 459 known not affected: 390 recommended: 292 | 2026-10-03T16:41:40+00:00 | Vulnerability · Source |
| CVE-2024-57850 | suse_vex | SUSE CVE CVE-2024-57850 | known affected: 366 known not affected: 394 recommended: 395 | 2026-10-03T16:41:36+00:00 | Vulnerability · Source |
| CVE-2024-57876 | suse_vex | SUSE CVE CVE-2024-57876 | known affected: 368 known not affected: 355 recommended: 508 | 2026-10-03T16:41:34+00:00 | Vulnerability · Source |
| CVE-2024-57890 | suse_vex | SUSE CVE CVE-2024-57890 | known affected: 736 known not affected: 28 recommended: 441 | 2026-10-03T16:41:30+00:00 | Vulnerability · Source |
| CVE-2024-57897 | suse_vex | SUSE CVE CVE-2024-57897 | known affected: 346 known not affected: 282 recommended: 582 | 2026-10-03T16:41:27+00:00 | Vulnerability · Source |
| CVE-2024-57913 | suse_vex | SUSE CVE CVE-2024-57913 | known affected: 565 known not affected: 227 recommended: 358 | 2026-10-03T16:41:25+00:00 | Vulnerability · Source |
| CVE-2024-57946 | suse_vex | SUSE CVE CVE-2024-57946 | known affected: 479 known not affected: 359 recommended: 358 | 2026-10-03T16:41:22+00:00 | Vulnerability · Source |
| CVE-2024-58093 | suse_vex | SUSE CVE CVE-2024-58093 | known affected: 522 known not affected: 224 recommended: 433 | 2026-10-03T16:41:19+00:00 | Vulnerability · Source |
| CVE-2025-0395 | suse_vex | SUSE CVE CVE-2025-0395 | known affected: 587 known not affected: 13 recommended: 1043 | 2026-10-03T16:41:16+00:00 | Vulnerability · Source |
| CVE-2025-1149 | suse_vex | SUSE CVE CVE-2025-1149 | known affected: 520 known not affected: 93 recommended: 489 | 2026-10-03T16:41:11+00:00 | Vulnerability · Source |
| CVE-2025-1151 | suse_vex | SUSE CVE CVE-2025-1151 | known affected: 520 known not affected: 93 recommended: 489 | 2026-10-03T16:41:09+00:00 | Vulnerability · Source |
| CVE-2025-6199 | suse_vex | SUSE CVE CVE-2025-6199 | known affected: 464 known not affected: 169 recommended: 294 | 2026-10-03T16:41:03+00:00 | Vulnerability · Source |
| CVE-2025-7345 | suse_vex | SUSE CVE CVE-2025-7345 | known affected: 593 known not affected: 1303 recommended: 331 | 2026-10-03T16:40:59+00:00 | Vulnerability · Source |
| CVE-2025-8194 | suse_vex | SUSE CVE CVE-2025-8194 | known affected: 713 recommended: 879 | 2026-10-03T16:40:57+00:00 | Vulnerability · Source |
| CVE-2025-8714 | suse_vex | SUSE CVE CVE-2025-8714 | known affected: 615 known not affected: 524 recommended: 1349 | 2026-10-03T16:40:55+00:00 | Vulnerability · Source |
| CVE-2025-8961 | suse_vex | SUSE CVE CVE-2025-8961 | known affected: 571 known not affected: 8 recommended: 88 | 2026-10-03T16:40:53+00:00 | Vulnerability · Source |
| CVE-2025-11563 | suse_vex | SUSE CVE CVE-2025-11563 | known affected: 459 known not affected: 79 recommended: 129 | 2026-10-03T16:40:48+00:00 | Vulnerability · Source |
| CVE-2025-11710 | suse_vex | SUSE CVE CVE-2025-11710 | known affected: 73 recommended: 177 | 2026-10-03T16:40:46+00:00 | Vulnerability · Source |
| CVE-2025-14017 | suse_vex | SUSE CVE CVE-2025-14017 | known affected: 528 recommended: 123 | 2026-10-03T16:40:41+00:00 | Vulnerability · Source |
| CVE-2025-15366 | suse_vex | SUSE CVE CVE-2025-15366 | known affected: 506 known not affected: 40 recommended: 883 | 2026-10-03T16:40:37+00:00 | Vulnerability · Source |
| CVE-2025-21649 | suse_vex | SUSE CVE CVE-2025-21649 | known affected: 540 known not affected: 298 recommended: 358 | 2026-10-03T16:40:33+00:00 | Vulnerability · Source |
| CVE-2025-21662 | suse_vex | SUSE CVE CVE-2025-21662 | known affected: 479 known not affected: 359 recommended: 358 | 2026-10-03T16:40:29+00:00 | Vulnerability · Source |
| CVE-2025-21759 | suse_vex | SUSE CVE CVE-2025-21759 | known affected: 752 recommended: 487 | 2026-10-03T16:40:26+00:00 | Vulnerability · Source |
| CVE-2025-30258 | suse_vex | SUSE CVE CVE-2025-30258 | known affected: 446 known not affected: 28 recommended: 93 | 2026-10-03T16:40:18+00:00 | Vulnerability · Source |
| CVE-2025-38072 | suse_vex | SUSE CVE CVE-2025-38072 | known affected: 746 known not affected: 36 recommended: 419 | 2026-10-03T16:40:12+00:00 | Vulnerability · Source |
| CVE-2025-38349 | suse_vex | SUSE CVE CVE-2025-38349 | known affected: 444 known not affected: 405 recommended: 555 | 2026-10-03T16:40:05+00:00 | Vulnerability · Source |
| CVE-2025-38491 | suse_vex | SUSE CVE CVE-2025-38491 | known affected: 460 known not affected: 405 recommended: 472 | 2026-10-03T16:40:01+00:00 | Vulnerability · Source |
| CVE-2025-38499 | suse_vex | SUSE CVE CVE-2025-38499 | known affected: 577 known not affected: 6 recommended: 991 | 2026-10-03T16:39:59+00:00 | Vulnerability · Source |
| CVE-2025-39807 | suse_vex | SUSE CVE CVE-2025-39807 | known affected: 401 known not affected: 490 recommended: 247 | 2026-10-03T16:39:51+00:00 | Vulnerability · Source |
| CVE-2025-39866 | suse_vex | SUSE CVE CVE-2025-39866 | known affected: 731 recommended: 501 | 2026-10-03T16:39:47+00:00 | Vulnerability · Source |