VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305179 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-50007 | suse_vex | SUSE CVE CVE-2024-50007 | known affected: 489 known not affected: 21 recommended: 676 | 2026-10-03T16:44:48+00:00 | Vulnerability · Source |
| CVE-2024-50016 | suse_vex | SUSE CVE CVE-2024-50016 | known affected: 398 known not affected: 493 recommended: 286 | 2026-10-03T16:44:46+00:00 | Vulnerability · Source |
| CVE-2024-50051 | suse_vex | SUSE CVE CVE-2024-50051 | known affected: 364 known not affected: 335 recommended: 459 | 2026-10-03T16:44:43+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-03T16:44:41+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-03T16:44:38+00:00 | Vulnerability · Source |
| CVE-2024-50202 | suse_vex | SUSE CVE CVE-2024-50202 | known affected: 692 known not affected: 72 recommended: 390 | 2026-10-03T16:44:35+00:00 | Vulnerability · Source |
| CVE-2024-50203 | suse_vex | SUSE CVE CVE-2024-50203 | known affected: 398 known not affected: 473 recommended: 280 | 2026-10-03T16:44:33+00:00 | Vulnerability · Source |
| CVE-2024-50262 | suse_vex | SUSE CVE CVE-2024-50262 | known affected: 627 known not affected: 134 recommended: 422 | 2026-10-03T16:44:30+00:00 | Vulnerability · Source |
| CVE-2024-50349 | suse_vex | SUSE CVE CVE-2024-50349 | known affected: 208 known not affected: 126 recommended: 423 | 2026-10-03T16:44:27+00:00 | Vulnerability · Source |
| CVE-2024-52006 | suse_vex | SUSE CVE CVE-2024-52006 | known affected: 208 known not affected: 126 recommended: 409 | 2026-10-03T16:44:25+00:00 | Vulnerability · Source |
| CVE-2024-52532 | suse_vex | SUSE CVE CVE-2024-52532 | known affected: 106 recommended: 278 | 2026-10-03T16:44:23+00:00 | Vulnerability · Source |
| CVE-2024-53056 | suse_vex | SUSE CVE CVE-2024-53056 | known affected: 408 known not affected: 344 recommended: 390 | 2026-10-03T16:44:21+00:00 | Vulnerability · Source |
| CVE-2024-53064 | suse_vex | SUSE CVE CVE-2024-53064 | known affected: 324 known not affected: 332 recommended: 532 | 2026-10-03T16:44:18+00:00 | Vulnerability · Source |
| CVE-2024-53095 | suse_vex | SUSE CVE CVE-2024-53095 | known affected: 604 known not affected: 117 recommended: 570 | 2026-10-03T16:44:15+00:00 | Vulnerability · Source |
| CVE-2024-53099 | suse_vex | SUSE CVE CVE-2024-53099 | known affected: 585 known not affected: 276 recommended: 280 | 2026-10-03T16:44:11+00:00 | Vulnerability · Source |
| CVE-2024-53113 | suse_vex | SUSE CVE CVE-2024-53113 | known affected: 485 known not affected: 319 recommended: 434 | 2026-10-03T16:44:08+00:00 | Vulnerability · Source |
| CVE-2024-53118 | suse_vex | SUSE CVE CVE-2024-53118 | known affected: 398 known not affected: 473 recommended: 323 | 2026-10-03T16:44:05+00:00 | Vulnerability · Source |
| CVE-2024-53119 | suse_vex | SUSE CVE CVE-2024-53119 | known affected: 485 known not affected: 319 recommended: 431 | 2026-10-03T16:44:02+00:00 | Vulnerability · Source |
| CVE-2024-53129 | suse_vex | SUSE CVE CVE-2024-53129 | known affected: 431 known not affected: 330 recommended: 381 | 2026-10-03T16:44:00+00:00 | Vulnerability · Source |
| CVE-2024-53133 | suse_vex | SUSE CVE CVE-2024-53133 | known affected: 398 known not affected: 512 recommended: 280 | 2026-10-03T16:43:58+00:00 | Vulnerability · Source |
| CVE-2024-53134 | suse_vex | SUSE CVE CVE-2024-53134 | known affected: 418 known not affected: 494 recommended: 323 | 2026-10-03T16:43:56+00:00 | Vulnerability · Source |
| CVE-2024-53136 | suse_vex | SUSE CVE CVE-2024-53136 | known not affected: 393 recommended: 363 | 2026-10-03T16:43:53+00:00 | Vulnerability · Source |
| CVE-2024-53164 | suse_vex | SUSE CVE CVE-2024-53164 | known affected: 513 known not affected: 191 recommended: 828 | 2026-10-03T16:43:48+00:00 | Vulnerability · Source |
| CVE-2024-53185 | suse_vex | SUSE CVE CVE-2024-53185 | known affected: 700 known not affected: 167 recommended: 384 | 2026-10-03T16:43:45+00:00 | Vulnerability · Source |
| CVE-2024-53191 | suse_vex | SUSE CVE CVE-2024-53191 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-03T16:43:42+00:00 | Vulnerability · Source |
| CVE-2024-53195 | suse_vex | SUSE CVE CVE-2024-53195 | known affected: 684 known not affected: 231 recommended: 358 | 2026-10-03T16:43:40+00:00 | Vulnerability · Source |
| CVE-2024-53196 | suse_vex | SUSE CVE CVE-2024-53196 | known affected: 600 known not affected: 321 recommended: 358 | 2026-10-03T16:43:38+00:00 | Vulnerability · Source |
| CVE-2024-53202 | suse_vex | SUSE CVE CVE-2024-53202 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-03T16:43:35+00:00 | Vulnerability · Source |
| CVE-2024-53222 | suse_vex | SUSE CVE CVE-2024-53222 | known affected: 398 known not affected: 511 recommended: 443 | 2026-10-03T16:43:33+00:00 | Vulnerability · Source |
| CVE-2024-53232 | suse_vex | SUSE CVE CVE-2024-53232 | known affected: 410 known not affected: 512 recommended: 401 | 2026-10-03T16:43:31+00:00 | Vulnerability · Source |
| CVE-2024-53234 | suse_vex | SUSE CVE CVE-2024-53234 | known affected: 398 known not affected: 512 recommended: 358 | 2026-10-03T16:43:29+00:00 | Vulnerability · Source |
| CVE-2024-53237 | suse_vex | SUSE CVE CVE-2024-53237 | known affected: 394 known not affected: 482 recommended: 423 | 2026-10-03T16:43:27+00:00 | Vulnerability · Source |
| CVE-2024-53241 | suse_vex | SUSE CVE CVE-2024-53241 | known affected: 324 known not affected: 300 recommended: 775 | 2026-10-03T16:43:24+00:00 | Vulnerability · Source |
| CVE-2024-53685 | suse_vex | SUSE CVE CVE-2024-53685 | known affected: 394 known not affected: 398 recommended: 358 | 2026-10-03T16:43:22+00:00 | Vulnerability · Source |
| CVE-2024-53690 | suse_vex | SUSE CVE CVE-2024-53690 | known affected: 364 known not affected: 441 recommended: 381 | 2026-10-03T16:43:20+00:00 | Vulnerability · Source |
| CVE-2024-54680 | suse_vex | SUSE CVE CVE-2024-54680 | known affected: 4 known not affected: 292 recommended: 565 | 2026-10-03T16:43:18+00:00 | Vulnerability · Source |
| CVE-2024-54683 | suse_vex | SUSE CVE CVE-2024-54683 | known affected: 767 recommended: 424 | 2026-10-03T16:43:15+00:00 | Vulnerability · Source |
| CVE-2024-55881 | suse_vex | SUSE CVE CVE-2024-55881 | known affected: 540 known not affected: 298 recommended: 358 | 2026-10-03T16:43:13+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-03T16:43:11+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-03T16:43:08+00:00 | Vulnerability · Source |
| CVE-2024-56545 | suse_vex | SUSE CVE CVE-2024-56545 | known not affected: 547 recommended: 78 | 2026-10-03T16:43:06+00:00 | Vulnerability · Source |
| CVE-2024-56548 | suse_vex | SUSE CVE CVE-2024-56548 | known affected: 519 known not affected: 73 recommended: 680 | 2026-10-03T16:43:04+00:00 | Vulnerability · Source |
| CVE-2024-56557 | suse_vex | SUSE CVE CVE-2024-56557 | known affected: 423 known not affected: 399 recommended: 459 | 2026-10-03T16:43:01+00:00 | Vulnerability · Source |
| CVE-2024-56589 | suse_vex | SUSE CVE CVE-2024-56589 | known affected: 600 known not affected: 321 recommended: 358 | 2026-10-03T16:42:58+00:00 | Vulnerability · Source |
| CVE-2024-56608 | suse_vex | SUSE CVE CVE-2024-56608 | known affected: 394 known not affected: 469 recommended: 358 | 2026-10-03T16:42:53+00:00 | Vulnerability · Source |
| CVE-2024-56620 | suse_vex | SUSE CVE CVE-2024-56620 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-03T16:42:51+00:00 | Vulnerability · Source |
| CVE-2024-56625 | suse_vex | SUSE CVE CVE-2024-56625 | known affected: 394 known not affected: 494 recommended: 358 | 2026-10-03T16:42:48+00:00 | Vulnerability · Source |
| CVE-2024-56632 | suse_vex | SUSE CVE CVE-2024-56632 | known affected: 410 known not affected: 499 recommended: 358 | 2026-10-03T16:42:45+00:00 | Vulnerability · Source |
| CVE-2024-56634 | suse_vex | SUSE CVE CVE-2024-56634 | known affected: 656 known not affected: 207 recommended: 358 | 2026-10-03T16:42:43+00:00 | Vulnerability · Source |
| CVE-2024-56635 | suse_vex | SUSE CVE CVE-2024-56635 | known affected: 410 known not affected: 499 recommended: 358 | 2026-10-03T16:42:41+00:00 | Vulnerability · Source |