VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306222 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-39681 | suse_vex | SUSE CVE CVE-2025-39681 | known affected: 573 known not affected: 213 recommended: 464 | 2026-10-10T02:00:19+00:00 | Vulnerability · Source |
| CVE-2025-39682 | suse_vex | SUSE CVE CVE-2025-39682 | known affected: 399 known not affected: 390 recommended: 616 | 2026-10-10T02:00:17+00:00 | Vulnerability · Source |
| CVE-2025-39683 | suse_vex | SUSE CVE CVE-2025-39683 | known affected: 662 known not affected: 129 recommended: 464 | 2026-10-10T02:00:15+00:00 | Vulnerability · Source |
| CVE-2025-39685 | suse_vex | SUSE CVE CVE-2025-39685 | known affected: 517 known not affected: 206 recommended: 464 | 2026-10-10T02:00:14+00:00 | Vulnerability · Source |
| CVE-2025-39686 | suse_vex | SUSE CVE CVE-2025-39686 | known affected: 791 recommended: 464 | 2026-10-10T02:00:12+00:00 | Vulnerability · Source |
| CVE-2025-39687 | suse_vex | SUSE CVE CVE-2025-39687 | known affected: 287 known not affected: 262 recommended: 154 | 2026-10-10T02:00:10+00:00 | Vulnerability · Source |
| CVE-2025-39695 | suse_vex | SUSE CVE CVE-2025-39695 | known affected: 396 known not affected: 467 recommended: 247 | 2026-10-10T02:00:08+00:00 | Vulnerability · Source |
| CVE-2025-39696 | suse_vex | SUSE CVE CVE-2025-39696 | known not affected: 523 recommended: 27 | 2026-10-10T02:00:06+00:00 | Vulnerability · Source |
| CVE-2025-39698 | suse_vex | SUSE CVE CVE-2025-39698 | known affected: 7 known not affected: 542 recommended: 244 | 2026-10-10T02:00:04+00:00 | Vulnerability · Source |
| CVE-2025-39700 | suse_vex | SUSE CVE CVE-2025-39700 | known affected: 2 known not affected: 517 recommended: 154 | 2026-10-10T02:00:02+00:00 | Vulnerability · Source |
| CVE-2025-39703 | suse_vex | SUSE CVE CVE-2025-39703 | known affected: 351 known not affected: 262 recommended: 678 | 2026-10-10T02:00:00+00:00 | Vulnerability · Source |
| CVE-2025-39706 | suse_vex | SUSE CVE CVE-2025-39706 | known affected: 632 known not affected: 124 recommended: 487 | 2026-10-10T01:59:58+00:00 | Vulnerability · Source |
| CVE-2025-39707 | suse_vex | SUSE CVE CVE-2025-39707 | known affected: 396 known not affected: 326 recommended: 247 | 2026-10-10T01:59:56+00:00 | Vulnerability · Source |
| CVE-2025-39709 | suse_vex | SUSE CVE CVE-2025-39709 | known affected: 593 known not affected: 190 recommended: 464 | 2026-10-10T01:59:54+00:00 | Vulnerability · Source |
| CVE-2025-39710 | suse_vex | SUSE CVE CVE-2025-39710 | known affected: 593 known not affected: 187 recommended: 464 | 2026-10-10T01:59:52+00:00 | Vulnerability · Source |
| CVE-2025-39712 | suse_vex | SUSE CVE CVE-2025-39712 | known affected: 69 known not affected: 450 recommended: 154 | 2026-10-10T01:59:50+00:00 | Vulnerability · Source |
| CVE-2025-39713 | suse_vex | SUSE CVE CVE-2025-39713 | known affected: 686 known not affected: 39 recommended: 464 | 2026-10-10T01:59:48+00:00 | Vulnerability · Source |
| CVE-2025-39714 | suse_vex | SUSE CVE CVE-2025-39714 | known affected: 714 known not affected: 9 recommended: 464 | 2026-10-10T01:59:46+00:00 | Vulnerability · Source |
| CVE-2025-39718 | suse_vex | SUSE CVE CVE-2025-39718 | known affected: 463 known not affected: 317 recommended: 621 | 2026-10-10T01:59:43+00:00 | Vulnerability · Source |
| CVE-2025-39719 | suse_vex | SUSE CVE CVE-2025-39719 | known affected: 463 known not affected: 320 recommended: 464 | 2026-10-10T01:59:41+00:00 | Vulnerability · Source |
| CVE-2025-39721 | suse_vex | SUSE CVE CVE-2025-39721 | known affected: 524 known not affected: 259 recommended: 464 | 2026-10-10T01:59:39+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | known affected: 69 known not affected: 450 recommended: 154 | 2026-10-10T01:59:37+00:00 | Vulnerability · Source |
| CVE-2025-39724 | suse_vex | SUSE CVE CVE-2025-39724 | known affected: 720 known not affected: 11 recommended: 501 | 2026-10-10T01:59:35+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | known affected: 479 known not affected: 68 recommended: 693 | 2026-10-10T01:59:33+00:00 | Vulnerability · Source |
| CVE-2025-39732 | suse_vex | SUSE CVE CVE-2025-39732 | known affected: 524 known not affected: 259 recommended: 464 | 2026-10-10T01:59:30+00:00 | Vulnerability · Source |
| CVE-2025-39735 | suse_vex | SUSE CVE CVE-2025-39735 | known affected: 376 known not affected: 423 recommended: 29 | 2026-10-10T01:59:27+00:00 | Vulnerability · Source |
| CVE-2025-39736 | suse_vex | SUSE CVE CVE-2025-39736 | known not affected: 560 | 2026-10-10T01:59:25+00:00 | Vulnerability · Source |
| CVE-2025-39738 | suse_vex | SUSE CVE CVE-2025-39738 | known affected: 791 recommended: 464 | 2026-10-10T01:59:23+00:00 | Vulnerability · Source |
| CVE-2025-39739 | suse_vex | SUSE CVE CVE-2025-39739 | known affected: 396 known not affected: 387 recommended: 464 | 2026-10-10T01:59:21+00:00 | Vulnerability · Source |
| CVE-2025-39743 | suse_vex | SUSE CVE CVE-2025-39743 | known affected: 394 known not affected: 441 recommended: 310 | 2026-10-10T01:59:19+00:00 | Vulnerability · Source |
| CVE-2025-39744 | suse_vex | SUSE CVE CVE-2025-39744 | known affected: 604 known not affected: 187 recommended: 464 | 2026-10-10T01:59:17+00:00 | Vulnerability · Source |
| CVE-2025-39747 | suse_vex | SUSE CVE CVE-2025-39747 | known affected: 517 known not affected: 208 recommended: 247 | 2026-10-10T01:59:15+00:00 | Vulnerability · Source |
| CVE-2025-39750 | suse_vex | SUSE CVE CVE-2025-39750 | known affected: 396 known not affected: 391 recommended: 464 | 2026-10-10T01:59:13+00:00 | Vulnerability · Source |
| CVE-2025-39754 | suse_vex | SUSE CVE CVE-2025-39754 | known affected: 725 known not affected: 6 recommended: 501 | 2026-10-10T01:59:10+00:00 | Vulnerability · Source |
| CVE-2025-39757 | suse_vex | SUSE CVE CVE-2025-39757 | known affected: 626 known not affected: 99 recommended: 606 | 2026-10-10T01:59:08+00:00 | Vulnerability · Source |
| CVE-2025-39758 | suse_vex | SUSE CVE CVE-2025-39758 | known affected: 463 known not affected: 320 recommended: 464 | 2026-10-10T01:59:06+00:00 | Vulnerability · Source |
| CVE-2025-39759 | suse_vex | SUSE CVE CVE-2025-39759 | known affected: 731 recommended: 501 | 2026-10-10T01:59:04+00:00 | Vulnerability · Source |
| CVE-2025-39760 | suse_vex | SUSE CVE CVE-2025-39760 | known affected: 726 known not affected: 28 recommended: 646 | 2026-10-10T01:59:02+00:00 | Vulnerability · Source |