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-2025-39704 | suse_vex | SUSE CVE CVE-2025-39704 | known affected: 90 known not affected: 472 | 2026-10-15T16:34:33+00:00 | Vulnerability · Source |
| CVE-2025-39705 | suse_vex | SUSE CVE CVE-2025-39705 | known affected: 635 known not affected: 96 recommended: 526 | 2026-10-15T16:34:31+00:00 | Vulnerability · Source |
| CVE-2025-39707 | suse_vex | SUSE CVE CVE-2025-39707 | known affected: 396 known not affected: 326 recommended: 278 | 2026-10-15T16:34:30+00:00 | Vulnerability · Source |
| CVE-2025-39709 | suse_vex | SUSE CVE CVE-2025-39709 | known affected: 593 known not affected: 190 recommended: 495 | 2026-10-15T16:34:28+00:00 | Vulnerability · Source |
| CVE-2025-39710 | suse_vex | SUSE CVE CVE-2025-39710 | known affected: 593 known not affected: 187 recommended: 495 | 2026-10-15T16:34:26+00:00 | Vulnerability · Source |
| CVE-2025-39712 | suse_vex | SUSE CVE CVE-2025-39712 | known affected: 69 known not affected: 447 recommended: 185 | 2026-10-15T16:34:25+00:00 | Vulnerability · Source |
| CVE-2025-39720 | suse_vex | SUSE CVE CVE-2025-39720 | known affected: 0 known not affected: 520 | 2026-10-15T16:34:23+00:00 | Vulnerability · Source |
| CVE-2025-39721 | suse_vex | SUSE CVE CVE-2025-39721 | known affected: 524 known not affected: 259 recommended: 495 | 2026-10-15T16:34:21+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | known affected: 69 known not affected: 447 recommended: 185 | 2026-10-15T16:34:19+00:00 | Vulnerability · Source |
| CVE-2025-39723 | suse_vex | SUSE CVE CVE-2025-39723 | known affected: 74 known not affected: 472 recommended: 185 | 2026-10-15T16:34:17+00:00 | Vulnerability · Source |
| CVE-2025-39724 | suse_vex | SUSE CVE CVE-2025-39724 | known affected: 720 known not affected: 11 recommended: 532 | 2026-10-15T16:34:15+00:00 | Vulnerability · Source |
| CVE-2025-39727 | suse_vex | SUSE CVE CVE-2025-39727 | known affected: 2 known not affected: 514 recommended: 228 | 2026-10-15T16:34:13+00:00 | Vulnerability · Source |
| CVE-2025-39730 | suse_vex | SUSE CVE CVE-2025-39730 | known affected: 593 known not affected: 187 recommended: 644 | 2026-10-15T16:34:11+00:00 | Vulnerability · Source |
| CVE-2025-39738 | suse_vex | SUSE CVE CVE-2025-39738 | known affected: 791 recommended: 495 | 2026-10-15T16:34:06+00:00 | Vulnerability · Source |
| CVE-2025-39739 | suse_vex | SUSE CVE CVE-2025-39739 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:34:03+00:00 | Vulnerability · Source |
| CVE-2025-39742 | suse_vex | SUSE CVE CVE-2025-39742 | known affected: 396 known not affected: 187 recommended: 720 | 2026-10-15T16:34:01+00:00 | Vulnerability · Source |
| CVE-2025-39744 | suse_vex | SUSE CVE CVE-2025-39744 | known affected: 604 known not affected: 187 recommended: 495 | 2026-10-15T16:33:59+00:00 | Vulnerability · Source |
| CVE-2025-39746 | suse_vex | SUSE CVE CVE-2025-39746 | known affected: 346 known not affected: 278 recommended: 709 | 2026-10-15T16:33:57+00:00 | Vulnerability · Source |
| CVE-2025-39747 | suse_vex | SUSE CVE CVE-2025-39747 | known affected: 517 known not affected: 208 recommended: 278 | 2026-10-15T16:33:54+00:00 | Vulnerability · Source |
| CVE-2025-39748 | suse_vex | SUSE CVE CVE-2025-39748 | known affected: 464 known not affected: 329 recommended: 316 | 2026-10-15T16:33:52+00:00 | Vulnerability · Source |
| CVE-2025-39749 | suse_vex | SUSE CVE CVE-2025-39749 | known affected: 596 known not affected: 187 recommended: 495 | 2026-10-15T16:33:50+00:00 | Vulnerability · Source |
| CVE-2025-39750 | suse_vex | SUSE CVE CVE-2025-39750 | known affected: 396 known not affected: 391 recommended: 495 | 2026-10-15T16:33:47+00:00 | Vulnerability · Source |
| CVE-2025-39752 | suse_vex | SUSE CVE CVE-2025-39752 | known affected: 0 known not affected: 520 | 2026-10-15T16:33:45+00:00 | Vulnerability · Source |
| CVE-2025-39753 | suse_vex | SUSE CVE CVE-2025-39753 | known affected: 2 known not affected: 514 recommended: 203 | 2026-10-15T16:33:44+00:00 | Vulnerability · Source |
| CVE-2025-39755 | suse_vex | SUSE CVE CVE-2025-39755 | known affected: 0 known not affected: 460 | 2026-10-15T16:33:42+00:00 | Vulnerability · Source |
| CVE-2025-39756 | suse_vex | SUSE CVE CVE-2025-39756 | known affected: 731 recommended: 532 | 2026-10-15T16:33:40+00:00 | Vulnerability · Source |
| CVE-2025-39760 | suse_vex | SUSE CVE CVE-2025-39760 | known affected: 726 known not affected: 28 recommended: 677 | 2026-10-15T16:33:39+00:00 | Vulnerability · Source |
| CVE-2025-39761 | suse_vex | SUSE CVE CVE-2025-39761 | known affected: 396 known not affected: 387 recommended: 581 | 2026-10-15T16:33:37+00:00 | Vulnerability · Source |
| CVE-2025-39762 | suse_vex | SUSE CVE CVE-2025-39762 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:33:35+00:00 | Vulnerability · Source |
| CVE-2025-39763 | suse_vex | SUSE CVE CVE-2025-39763 | known affected: 720 known not affected: 21 recommended: 518 | 2026-10-15T16:33:33+00:00 | Vulnerability · Source |
| CVE-2025-39764 | suse_vex | SUSE CVE CVE-2025-39764 | known affected: 731 recommended: 532 | 2026-10-15T16:33:31+00:00 | Vulnerability · Source |
| CVE-2025-39766 | suse_vex | SUSE CVE CVE-2025-39766 | known affected: 599 known not affected: 187 recommended: 578 | 2026-10-15T16:33:29+00:00 | Vulnerability · Source |
| CVE-2025-39768 | suse_vex | SUSE CVE CVE-2025-39768 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:33:27+00:00 | Vulnerability · Source |
| CVE-2025-39770 | suse_vex | SUSE CVE CVE-2025-39770 | known affected: 401 known not affected: 390 recommended: 495 | 2026-10-15T16:33:25+00:00 | Vulnerability · Source |
| CVE-2025-39773 | suse_vex | SUSE CVE CVE-2025-39773 | known affected: 731 recommended: 540 | 2026-10-15T16:33:23+00:00 | Vulnerability · Source |
| CVE-2025-39775 | suse_vex | SUSE CVE CVE-2025-39775 | known affected: 223 known not affected: 323 recommended: 185 | 2026-10-15T16:33:21+00:00 | Vulnerability · Source |
| CVE-2025-39779 | suse_vex | SUSE CVE CVE-2025-39779 | known affected: 524 known not affected: 262 recommended: 185 | 2026-10-15T16:33:19+00:00 | Vulnerability · Source |
| CVE-2025-39780 | suse_vex | SUSE CVE CVE-2025-39780 | known affected: 0 known not affected: 557 | 2026-10-15T16:33:17+00:00 | Vulnerability · Source |
| CVE-2025-39782 | suse_vex | SUSE CVE CVE-2025-39782 | known affected: 725 known not affected: 6 recommended: 540 | 2026-10-15T16:33:15+00:00 | Vulnerability · Source |
| CVE-2025-39783 | suse_vex | SUSE CVE CVE-2025-39783 | known affected: 593 known not affected: 190 recommended: 495 | 2026-10-15T16:33:13+00:00 | Vulnerability · Source |
| CVE-2025-39785 | suse_vex | SUSE CVE CVE-2025-39785 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-15T16:33:11+00:00 | Vulnerability · Source |
| CVE-2025-39786 | suse_vex | SUSE CVE CVE-2025-39786 | known affected: 0 known not affected: 520 | 2026-10-15T16:33:09+00:00 | Vulnerability · Source |
| CVE-2025-39787 | suse_vex | SUSE CVE CVE-2025-39787 | known affected: 686 known not affected: 39 recommended: 518 | 2026-10-15T16:33:08+00:00 | Vulnerability · Source |
| CVE-2025-39788 | suse_vex | SUSE CVE CVE-2025-39788 | known affected: 524 known not affected: 267 recommended: 495 | 2026-10-15T16:33:06+00:00 | Vulnerability · Source |
| CVE-2025-39791 | suse_vex | SUSE CVE CVE-2025-39791 | known affected: 7 known not affected: 539 recommended: 185 | 2026-10-15T16:33:04+00:00 | Vulnerability · Source |
| CVE-2025-39795 | suse_vex | SUSE CVE CVE-2025-39795 | known affected: 130 known not affected: 256 recommended: 203 | 2026-10-15T16:33:03+00:00 | Vulnerability · Source |
| CVE-2025-39797 | suse_vex | SUSE CVE CVE-2025-39797 | known affected: 354 known not affected: 256 recommended: 739 | 2026-10-15T16:33:01+00:00 | Vulnerability · Source |
| CVE-2025-39798 | suse_vex | SUSE CVE CVE-2025-39798 | known affected: 778 known not affected: 3 recommended: 495 | 2026-10-15T16:32:59+00:00 | Vulnerability · Source |
| CVE-2025-39800 | suse_vex | SUSE CVE CVE-2025-39800 | known affected: 665 known not affected: 66 recommended: 532 | 2026-10-15T16:32:57+00:00 | Vulnerability · Source |
| CVE-2025-39810 | suse_vex | SUSE CVE CVE-2025-39810 | known affected: 604 known not affected: 187 recommended: 495 | 2026-10-15T16:32:55+00:00 | Vulnerability · Source |