VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
78859 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-42096 | suse_vex | SUSE CVE CVE-2024-42096 | known affected: 586 recommended: 786 | 2026-10-04T16:56:35+00:00 | Vulnerability · Source |
| CVE-2024-42286 | suse_vex | SUSE CVE CVE-2024-42286 | known affected: 502 known not affected: 13 recommended: 713 | 2026-10-04T16:56:32+00:00 | Vulnerability · Source |
| CVE-2024-44995 | suse_vex | SUSE CVE CVE-2024-44995 | known affected: 634 known not affected: 74 recommended: 575 | 2026-10-04T16:56:28+00:00 | Vulnerability · Source |
| CVE-2024-45769 | suse_vex | SUSE CVE CVE-2024-45769 | known affected: 492 recommended: 1372 | 2026-10-04T16:56:25+00:00 | Vulnerability · Source |
| CVE-2024-45770 | suse_vex | SUSE CVE CVE-2024-45770 | known affected: 657 recommended: 1372 | 2026-10-04T16:56:23+00:00 | Vulnerability · Source |
| CVE-2024-45774 | suse_vex | SUSE CVE CVE-2024-45774 | known affected: 567 recommended: 407 | 2026-10-04T16:56:20+00:00 | Vulnerability · Source |
| CVE-2024-46739 | suse_vex | SUSE CVE CVE-2024-46739 | known affected: 511 known not affected: 92 recommended: 710 | 2026-10-04T16:56:16+00:00 | Vulnerability · Source |
| CVE-2024-47672 | suse_vex | SUSE CVE CVE-2024-47672 | known affected: 615 known not affected: 74 recommended: 658 | 2026-10-04T16:56:12+00:00 | Vulnerability · Source |
| CVE-2024-49854 | suse_vex | SUSE CVE CVE-2024-49854 | known affected: 394 known not affected: 443 recommended: 286 | 2026-10-04T16:56:06+00:00 | Vulnerability · Source |
| CVE-2024-49890 | suse_vex | SUSE CVE CVE-2024-49890 | known affected: 603 known not affected: 108 recommended: 664 | 2026-10-04T16:56:03+00:00 | Vulnerability · Source |
| CVE-2024-49915 | suse_vex | SUSE CVE CVE-2024-49915 | known affected: 481 known not affected: 412 recommended: 286 | 2026-10-04T16:56:01+00:00 | Vulnerability · Source |
| CVE-2024-49951 | suse_vex | SUSE CVE CVE-2024-49951 | known affected: 489 known not affected: 395 recommended: 329 | 2026-10-04T16:55:58+00:00 | Vulnerability · Source |
| CVE-2024-49958 | suse_vex | SUSE CVE CVE-2024-49958 | known affected: 645 known not affected: 42 recommended: 678 | 2026-10-04T16:55:56+00:00 | Vulnerability · Source |
| CVE-2024-50106 | suse_vex | SUSE CVE CVE-2024-50106 | known affected: 811 known not affected: 33 recommended: 419 | 2026-10-04T16:55:51+00:00 | Vulnerability · Source |
| CVE-2024-50148 | suse_vex | SUSE CVE CVE-2024-50148 | known affected: 668 known not affected: 49 recommended: 595 | 2026-10-04T16:55:48+00:00 | Vulnerability · Source |
| CVE-2024-50195 | suse_vex | SUSE CVE CVE-2024-50195 | known affected: 676 known not affected: 32 recommended: 700 | 2026-10-04T16:55:45+00:00 | Vulnerability · Source |
| CVE-2024-50210 | suse_vex | SUSE CVE CVE-2024-50210 | known not affected: 359 recommended: 397 | 2026-10-04T16:55:42+00:00 | Vulnerability · Source |
| CVE-2024-50280 | suse_vex | SUSE CVE CVE-2024-50280 | known affected: 4 known not affected: 395 recommended: 390 | 2026-10-04T16:55:39+00:00 | Vulnerability · Source |
| CVE-2024-53050 | suse_vex | SUSE CVE CVE-2024-53050 | known affected: 674 known not affected: 32 recommended: 323 | 2026-10-04T16:55:36+00:00 | Vulnerability · Source |
| CVE-2024-53090 | suse_vex | SUSE CVE CVE-2024-53090 | known affected: 702 known not affected: 102 recommended: 431 | 2026-10-04T16:55:34+00:00 | Vulnerability · Source |
| CVE-2024-53111 | suse_vex | SUSE CVE CVE-2024-53111 | known affected: 398 known not affected: 473 recommended: 280 | 2026-10-04T16:55:32+00:00 | Vulnerability · Source |
| CVE-2024-53126 | suse_vex | SUSE CVE CVE-2024-53126 | known affected: 394 known not affected: 482 recommended: 280 | 2026-10-04T16:55:30+00:00 | Vulnerability · Source |
| CVE-2024-53130 | suse_vex | SUSE CVE CVE-2024-53130 | known affected: 711 known not affected: 108 recommended: 390 | 2026-10-04T16:55:28+00:00 | Vulnerability · Source |
| CVE-2024-53154 | suse_vex | SUSE CVE CVE-2024-53154 | known affected: 394 known not affected: 494 recommended: 358 | 2026-10-04T16:55:26+00:00 | Vulnerability · Source |
| CVE-2024-53160 | suse_vex | SUSE CVE CVE-2024-53160 | known affected: 398 known not affected: 539 recommended: 401 | 2026-10-04T16:55:24+00:00 | Vulnerability · Source |
| CVE-2024-53169 | suse_vex | SUSE CVE CVE-2024-53169 | known affected: 431 known not affected: 362 recommended: 459 | 2026-10-04T16:55:22+00:00 | Vulnerability · Source |
| CVE-2024-53174 | suse_vex | SUSE CVE CVE-2024-53174 | known affected: 711 known not affected: 102 recommended: 502 | 2026-10-04T16:55:19+00:00 | Vulnerability · Source |
| CVE-2024-53175 | suse_vex | SUSE CVE CVE-2024-53175 | known affected: 410 known not affected: 511 recommended: 358 | 2026-10-04T16:55:17+00:00 | Vulnerability · Source |
| CVE-2024-53187 | suse_vex | SUSE CVE CVE-2024-53187 | known affected: 533 known not affected: 388 recommended: 358 | 2026-10-04T16:55:14+00:00 | Vulnerability · Source |
| CVE-2024-53190 | suse_vex | SUSE CVE CVE-2024-53190 | known affected: 394 known not affected: 16 recommended: 415 | 2026-10-04T16:55:12+00:00 | Vulnerability · Source |
| CVE-2024-53207 | suse_vex | SUSE CVE CVE-2024-53207 | known affected: 394 known not affected: 481 recommended: 358 | 2026-10-04T16:55:10+00:00 | Vulnerability · Source |
| CVE-2024-53231 | suse_vex | SUSE CVE CVE-2024-53231 | known affected: 394 known not affected: 515 recommended: 358 | 2026-10-04T16:55:08+00:00 | Vulnerability · Source |
| CVE-2024-53233 | suse_vex | SUSE CVE CVE-2024-53233 | known affected: 394 known not affected: 494 recommended: 358 | 2026-10-04T16:55:07+00:00 | Vulnerability · Source |
| CVE-2024-53236 | suse_vex | SUSE CVE CVE-2024-53236 | known affected: 410 known not affected: 511 recommended: 358 | 2026-10-04T16:55:04+00:00 | Vulnerability · Source |
| CVE-2024-53920 | suse_vex | SUSE CVE CVE-2024-53920 | known not affected: 191 recommended: 199 | 2026-10-04T16:55:02+00:00 | Vulnerability · Source |
| CVE-2024-56533 | suse_vex | SUSE CVE CVE-2024-56533 | known affected: 658 known not affected: 85 recommended: 499 | 2026-10-04T16:54:59+00:00 | Vulnerability · Source |
| CVE-2024-56549 | suse_vex | SUSE CVE CVE-2024-56549 | known affected: 418 known not affected: 389 recommended: 468 | 2026-10-04T16:54:57+00:00 | Vulnerability · Source |
| CVE-2024-56568 | suse_vex | SUSE CVE CVE-2024-56568 | known affected: 777 known not affected: 134 recommended: 360 | 2026-10-04T16:54: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-04T16:54:52+00:00 | Vulnerability · Source |
| CVE-2024-56582 | suse_vex | SUSE CVE CVE-2024-56582 | known affected: 398 known not affected: 512 recommended: 382 | 2026-10-04T16:54:49+00:00 | Vulnerability · Source |
| CVE-2024-56584 | suse_vex | SUSE CVE CVE-2024-56584 | known affected: 582 known not affected: 299 recommended: 358 | 2026-10-04T16:54:47+00:00 | Vulnerability · Source |
| CVE-2024-56588 | suse_vex | SUSE CVE CVE-2024-56588 | known affected: 504 known not affected: 321 recommended: 459 | 2026-10-04T16:54:45+00:00 | Vulnerability · Source |
| CVE-2024-56595 | suse_vex | SUSE CVE CVE-2024-56595 | known affected: 651 known not affected: 230 recommended: 381 | 2026-10-04T16:54:43+00:00 | Vulnerability · Source |
| CVE-2024-56596 | suse_vex | SUSE CVE CVE-2024-56596 | known affected: 587 known not affected: 284 recommended: 381 | 2026-10-04T16:54:41+00:00 | Vulnerability · Source |
| CVE-2024-56597 | suse_vex | SUSE CVE CVE-2024-56597 | known affected: 671 known not affected: 238 recommended: 381 | 2026-10-04T16:54:38+00:00 | Vulnerability · Source |
| CVE-2024-56607 | suse_vex | SUSE CVE CVE-2024-56607 | known affected: 410 known not affected: 512 recommended: 358 | 2026-10-04T16:54:34+00:00 | Vulnerability · Source |
| CVE-2024-56609 | suse_vex | SUSE CVE CVE-2024-56609 | known affected: 410 known not affected: 512 recommended: 358 | 2026-10-04T16:54:32+00:00 | Vulnerability · Source |
| CVE-2024-56619 | suse_vex | SUSE CVE CVE-2024-56619 | known affected: 421 known not affected: 358 recommended: 527 | 2026-10-04T16:54:29+00:00 | Vulnerability · Source |
| CVE-2024-56622 | suse_vex | SUSE CVE CVE-2024-56622 | known affected: 600 known not affected: 321 recommended: 358 | 2026-10-04T16:54:27+00:00 | Vulnerability · Source |
| CVE-2024-56644 | suse_vex | SUSE CVE CVE-2024-56644 | known affected: 733 known not affected: 139 recommended: 522 | 2026-10-04T16:54:23+00:00 | Vulnerability · Source |