VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306216 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38584 | suse_vex | SUSE CVE CVE-2025-38584 | known affected: 806 recommended: 464 | 2026-10-10T02:02:14+00:00 | Vulnerability · Source |
| CVE-2025-38585 | suse_vex | SUSE CVE CVE-2025-38585 | known affected: 455 known not affected: 410 recommended: 472 | 2026-10-10T02:02:12+00:00 | Vulnerability · Source |
| CVE-2025-38586 | suse_vex | SUSE CVE CVE-2025-38586 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-10T02:02:10+00:00 | Vulnerability · Source |
| CVE-2025-38590 | suse_vex | SUSE CVE CVE-2025-38590 | known affected: 593 known not affected: 213 recommended: 490 | 2026-10-10T02:02:08+00:00 | Vulnerability · Source |
| CVE-2025-38591 | suse_vex | SUSE CVE CVE-2025-38591 | known affected: 766 known not affected: 41 recommended: 495 | 2026-10-10T02:02:06+00:00 | Vulnerability · Source |
| CVE-2025-38595 | suse_vex | SUSE CVE CVE-2025-38595 | known affected: 608 known not affected: 190 recommended: 472 | 2026-10-10T02:02:04+00:00 | Vulnerability · Source |
| CVE-2025-38601 | suse_vex | SUSE CVE CVE-2025-38601 | known affected: 539 known not affected: 322 recommended: 472 | 2026-10-10T02:02:01+00:00 | Vulnerability · Source |
| CVE-2025-38602 | suse_vex | SUSE CVE CVE-2025-38602 | known affected: 741 known not affected: 64 recommended: 509 | 2026-10-10T02:01:59+00:00 | Vulnerability · Source |
| CVE-2025-38608 | suse_vex | SUSE CVE CVE-2025-38608 | known affected: 500 known not affected: 154 recommended: 827 | 2026-10-10T02:01:56+00:00 | Vulnerability · Source |
| CVE-2025-38610 | suse_vex | SUSE CVE CVE-2025-38610 | known affected: 396 known not affected: 453 recommended: 472 | 2026-10-10T02:01:54+00:00 | Vulnerability · Source |
| CVE-2025-38612 | suse_vex | SUSE CVE CVE-2025-38612 | known affected: 582 known not affected: 279 recommended: 472 | 2026-10-10T02:01:52+00:00 | Vulnerability · Source |
| CVE-2025-38622 | suse_vex | SUSE CVE CVE-2025-38622 | known affected: 619 known not affected: 187 recommended: 472 | 2026-10-10T02:01:47+00:00 | Vulnerability · Source |
| CVE-2025-38625 | suse_vex | SUSE CVE CVE-2025-38625 | known affected: 2 known not affected: 538 recommended: 145 | 2026-10-10T02:01:45+00:00 | Vulnerability · Source |
| CVE-2025-38628 | suse_vex | SUSE CVE CVE-2025-38628 | known affected: 401 known not affected: 505 recommended: 247 | 2026-10-10T02:01:43+00:00 | Vulnerability · Source |
| CVE-2025-38629 | suse_vex | SUSE CVE CVE-2025-38629 | known not affected: 524 recommended: 27 | 2026-10-10T02:01:41+00:00 | Vulnerability · Source |
| CVE-2025-38630 | suse_vex | SUSE CVE CVE-2025-38630 | known affected: 517 known not affected: 332 recommended: 472 | 2026-10-10T02:01:38+00:00 | Vulnerability · Source |
| CVE-2025-38635 | suse_vex | SUSE CVE CVE-2025-38635 | known affected: 396 known not affected: 453 recommended: 472 | 2026-10-10T02:01:35+00:00 | Vulnerability · Source |
| CVE-2025-38637 | suse_vex | SUSE CVE CVE-2025-38637 | known affected: 671 known not affected: 96 recommended: 423 | 2026-10-10T02:01:33+00:00 | Vulnerability · Source |
| CVE-2025-38640 | suse_vex | SUSE CVE CVE-2025-38640 | known affected: 401 known not affected: 405 recommended: 472 | 2026-10-10T02:01:30+00:00 | Vulnerability · Source |
| CVE-2025-38643 | suse_vex | SUSE CVE CVE-2025-38643 | known affected: 619 known not affected: 187 recommended: 472 | 2026-10-10T02:01:27+00:00 | Vulnerability · Source |
| CVE-2025-38646 | suse_vex | SUSE CVE CVE-2025-38646 | known affected: 396 known not affected: 453 recommended: 472 | 2026-10-10T02:01:25+00:00 | Vulnerability · Source |
| CVE-2025-38652 | suse_vex | SUSE CVE CVE-2025-38652 | known affected: 394 known not affected: 533 recommended: 4 | 2026-10-10T02:01:23+00:00 | Vulnerability · Source |
| CVE-2025-38656 | suse_vex | SUSE CVE CVE-2025-38656 | known affected: 396 known not affected: 393 recommended: 509 | 2026-10-10T02:01:20+00:00 | Vulnerability · Source |
| CVE-2025-38658 | suse_vex | SUSE CVE CVE-2025-38658 | known affected: 2 known not affected: 524 recommended: 154 | 2026-10-10T02:01:19+00:00 | Vulnerability · Source |
| CVE-2025-38665 | suse_vex | SUSE CVE CVE-2025-38665 | known affected: 741 known not affected: 64 recommended: 495 | 2026-10-10T02:01:16+00:00 | Vulnerability · Source |
| CVE-2025-38668 | suse_vex | SUSE CVE CVE-2025-38668 | known affected: 608 known not affected: 190 recommended: 472 | 2026-10-10T02:01:14+00:00 | Vulnerability · Source |
| CVE-2025-38670 | suse_vex | SUSE CVE CVE-2025-38670 | known affected: 539 known not affected: 310 recommended: 472 | 2026-10-10T02:01:12+00:00 | Vulnerability · Source |
| CVE-2025-38676 | suse_vex | SUSE CVE CVE-2025-38676 | known affected: 463 known not affected: 338 recommended: 472 | 2026-10-10T02:01:09+00:00 | Vulnerability · Source |
| CVE-2025-38679 | suse_vex | SUSE CVE CVE-2025-38679 | known affected: 422 known not affected: 192 recommended: 472 | 2026-10-10T02:01:07+00:00 | Vulnerability · Source |
| CVE-2025-38680 | suse_vex | SUSE CVE CVE-2025-38680 | known affected: 726 known not affected: 32 recommended: 501 | 2026-10-10T02:01:05+00:00 | Vulnerability · Source |
| CVE-2025-38681 | suse_vex | SUSE CVE CVE-2025-38681 | known affected: 524 known not affected: 277 recommended: 464 | 2026-10-10T02:01:03+00:00 | Vulnerability · Source |
| CVE-2025-38687 | suse_vex | SUSE CVE CVE-2025-38687 | known affected: 774 known not affected: 6 recommended: 464 | 2026-10-10T02:01:01+00:00 | Vulnerability · Source |
| CVE-2025-38698 | suse_vex | SUSE CVE CVE-2025-38698 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-10T02:00:58+00:00 | Vulnerability · Source |
| CVE-2025-38701 | suse_vex | SUSE CVE CVE-2025-38701 | known affected: 725 known not affected: 6 recommended: 509 | 2026-10-10T02:00:56+00:00 | Vulnerability · Source |
| CVE-2025-38710 | suse_vex | SUSE CVE CVE-2025-38710 | known affected: 399 known not affected: 490 recommended: 247 | 2026-10-10T02:00:53+00:00 | Vulnerability · Source |
| CVE-2025-38712 | suse_vex | SUSE CVE CVE-2025-38712 | known affected: 718 known not affected: 26 recommended: 347 | 2026-10-10T02:00:50+00:00 | Vulnerability · Source |
| CVE-2025-38715 | suse_vex | SUSE CVE CVE-2025-38715 | known affected: 394 known not affected: 393 recommended: 310 | 2026-10-10T02:00:48+00:00 | Vulnerability · Source |
| CVE-2025-38718 | suse_vex | SUSE CVE CVE-2025-38718 | known affected: 686 known not affected: 36 recommended: 606 | 2026-10-10T02:00:46+00:00 | Vulnerability · Source |
| CVE-2025-38721 | suse_vex | SUSE CVE CVE-2025-38721 | known affected: 786 recommended: 472 | 2026-10-10T02:00:43+00:00 | Vulnerability · Source |
| CVE-2025-38724 | suse_vex | SUSE CVE CVE-2025-38724 | known affected: 720 known not affected: 11 recommended: 604 | 2026-10-10T02:00:41+00:00 | Vulnerability · Source |
| CVE-2025-38727 | suse_vex | SUSE CVE CVE-2025-38727 | known affected: 2 known not affected: 327 recommended: 501 | 2026-10-10T02:00:39+00:00 | Vulnerability · Source |
| CVE-2025-38728 | suse_vex | SUSE CVE CVE-2025-38728 | known affected: 725 known not affected: 41 recommended: 389 | 2026-10-10T02:00:37+00:00 | Vulnerability · Source |
| CVE-2025-38729 | suse_vex | SUSE CVE CVE-2025-38729 | known affected: 626 known not affected: 96 recommended: 500 | 2026-10-10T02:00:35+00:00 | Vulnerability · Source |
| CVE-2025-38730 | suse_vex | SUSE CVE CVE-2025-38730 | known affected: 463 known not affected: 317 recommended: 584 | 2026-10-10T02:00:33+00:00 | Vulnerability · Source |
| CVE-2025-38733 | suse_vex | SUSE CVE CVE-2025-38733 | known affected: 74 known not affected: 475 recommended: 154 | 2026-10-10T02:00:31+00:00 | Vulnerability · Source |
| CVE-2025-38734 | suse_vex | SUSE CVE CVE-2025-38734 | known affected: 349 known not affected: 262 recommended: 670 | 2026-10-10T02:00:29+00:00 | Vulnerability · Source |
| CVE-2025-39675 | suse_vex | SUSE CVE CVE-2025-39675 | known affected: 567 known not affected: 216 recommended: 464 | 2026-10-10T02:00:28+00:00 | Vulnerability · Source |
| CVE-2025-39677 | suse_vex | SUSE CVE CVE-2025-39677 | known affected: 725 known not affected: 6 recommended: 501 | 2026-10-10T02:00:26+00:00 | Vulnerability · Source |
| CVE-2025-39678 | suse_vex | SUSE CVE CVE-2025-39678 | known affected: 468 known not affected: 323 recommended: 472 | 2026-10-10T02:00:24+00:00 | Vulnerability · Source |
| CVE-2025-39679 | suse_vex | SUSE CVE CVE-2025-39679 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T02:00:22+00:00 | Vulnerability · Source |