VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292268 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38697 | suse_vex | SUSE CVE CVE-2025-38697 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T00:42:25+00:00 | Vulnerability · Source |
| CVE-2025-38699 | suse_vex | SUSE CVE CVE-2025-38699 | known affected: 630 known not affected: 20 recommended: 383 | 2026-07-25T00:42:23+00:00 | Vulnerability · Source |
| CVE-2025-38702 | suse_vex | SUSE CVE CVE-2025-38702 | first fixed: 2 known affected: 614 known not affected: 21 recommended: 537 | 2026-07-25T00:42:21+00:00 | Vulnerability · Source |
| CVE-2025-38705 | suse_vex | SUSE CVE CVE-2025-38705 | first fixed: 2 known affected: 506 known not affected: 123 recommended: 531 | 2026-07-25T00:42:18+00:00 | Vulnerability · Source |
| CVE-2025-38706 | suse_vex | SUSE CVE CVE-2025-38706 | first fixed: 2 known affected: 387 known not affected: 118 recommended: 706 | 2026-07-25T00:42:16+00:00 | Vulnerability · Source |
| CVE-2025-38712 | suse_vex | SUSE CVE CVE-2025-38712 | known affected: 624 known not affected: 26 recommended: 383 | 2026-07-25T00:42:14+00:00 | Vulnerability · Source |
| CVE-2025-38715 | suse_vex | SUSE CVE CVE-2025-38715 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T00:42:11+00:00 | Vulnerability · Source |
| CVE-2025-38718 | suse_vex | SUSE CVE CVE-2025-38718 | first fixed: 2 known affected: 604 known not affected: 22 recommended: 599 | 2026-07-25T00:42:09+00:00 | Vulnerability · Source |
| CVE-2025-38725 | suse_vex | SUSE CVE CVE-2025-38725 | first fixed: 2 known affected: 506 known not affected: 150 recommended: 500 | 2026-07-25T00:42:06+00:00 | Vulnerability · Source |
| CVE-2025-38727 | suse_vex | SUSE CVE CVE-2025-38727 | first fixed: 2 known not affected: 233 recommended: 537 | 2026-07-25T00:42:03+00:00 | Vulnerability · Source |
| CVE-2025-38728 | suse_vex | SUSE CVE CVE-2025-38728 | first fixed: 2 known affected: 649 known not affected: 27 recommended: 407 | 2026-07-25T00:42:01+00:00 | Vulnerability · Source |
| CVE-2025-38729 | suse_vex | SUSE CVE CVE-2025-38729 | first fixed: 2 known affected: 574 known not affected: 52 recommended: 536 | 2026-07-25T00:41:59+00:00 | Vulnerability · Source |
| CVE-2025-38734 | suse_vex | SUSE CVE CVE-2025-38734 | first fixed: 2 known affected: 347 known not affected: 156 recommended: 706 | 2026-07-25T00:41:55+00:00 | Vulnerability · Source |
| CVE-2025-38736 | suse_vex | SUSE CVE CVE-2025-38736 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:41:53+00:00 | Vulnerability · Source |
| CVE-2025-39677 | suse_vex | SUSE CVE CVE-2025-39677 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 537 | 2026-07-25T00:41:50+00:00 | Vulnerability · Source |
| CVE-2025-39679 | suse_vex | SUSE CVE CVE-2025-39679 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:41:48+00:00 | Vulnerability · Source |
| CVE-2025-39682 | suse_vex | SUSE CVE CVE-2025-39682 | first fixed: 2 known affected: 397 known not affected: 268 recommended: 609 | 2026-07-25T00:41:46+00:00 | Vulnerability · Source |
| CVE-2025-39685 | suse_vex | SUSE CVE CVE-2025-39685 | first fixed: 2 known affected: 455 known not affected: 172 recommended: 500 | 2026-07-25T00:41:44+00:00 | Vulnerability · Source |
| CVE-2025-39691 | suse_vex | SUSE CVE CVE-2025-39691 | first fixed: 2 known affected: 468 known not affected: 5 recommended: 751 | 2026-07-25T00:41:42+00:00 | Vulnerability · Source |
| CVE-2025-39693 | suse_vex | SUSE CVE CVE-2025-39693 | first fixed: 2 known affected: 506 known not affected: 153 recommended: 500 | 2026-07-25T00:41:40+00:00 | Vulnerability · Source |
| CVE-2025-39699 | suse_vex | SUSE CVE CVE-2025-39699 | known not affected: 416 | 2026-07-25T00:41:38+00:00 | Vulnerability · Source |
| CVE-2025-39701 | suse_vex | SUSE CVE CVE-2025-39701 | first fixed: 2 known affected: 451 known not affected: 205 recommended: 500 | 2026-07-25T00:41:37+00:00 | Vulnerability · Source |
| CVE-2025-39702 | suse_vex | SUSE CVE CVE-2025-39702 | first fixed: 2 known affected: 615 known not affected: 22 recommended: 566 | 2026-07-25T00:41:35+00:00 | Vulnerability · Source |
| CVE-2025-39705 | suse_vex | SUSE CVE CVE-2025-39705 | first fixed: 2 known affected: 583 known not affected: 52 recommended: 531 | 2026-07-25T00:41:33+00:00 | Vulnerability · Source |
| CVE-2025-39707 | suse_vex | SUSE CVE CVE-2025-39707 | first fixed: 2 known affected: 394 known not affected: 232 recommended: 265 | 2026-07-25T00:41:31+00:00 | Vulnerability · Source |
| CVE-2025-39709 | suse_vex | SUSE CVE CVE-2025-39709 | first fixed: 2 known affected: 557 known not affected: 102 recommended: 500 | 2026-07-25T00:41:29+00:00 | Vulnerability · Source |
| CVE-2025-39710 | suse_vex | SUSE CVE CVE-2025-39710 | first fixed: 2 known affected: 557 known not affected: 99 recommended: 500 | 2026-07-25T00:41:27+00:00 | Vulnerability · Source |
| CVE-2025-39713 | suse_vex | SUSE CVE CVE-2025-39713 | first fixed: 2 known affected: 604 known not affected: 25 recommended: 500 | 2026-07-25T00:41:25+00:00 | Vulnerability · Source |
| CVE-2025-39719 | suse_vex | SUSE CVE CVE-2025-39719 | first fixed: 2 known affected: 451 known not affected: 208 recommended: 500 | 2026-07-25T00:41:23+00:00 | Vulnerability · Source |
| CVE-2025-39722 | suse_vex | SUSE CVE CVE-2025-39722 | first fixed: 2 known affected: 57 known not affected: 353 recommended: 154 | 2026-07-25T00:41:21+00:00 | Vulnerability · Source |
| CVE-2025-39724 | suse_vex | SUSE CVE CVE-2025-39724 | first fixed: 2 known affected: 624 known not affected: 11 recommended: 537 | 2026-07-25T00:41:20+00:00 | Vulnerability · Source |
| CVE-2025-39726 | suse_vex | SUSE CVE CVE-2025-39726 | first fixed: 2 known affected: 429 known not affected: 38 recommended: 729 | 2026-07-25T00:41:18+00:00 | Vulnerability · Source |
| CVE-2025-39739 | suse_vex | SUSE CVE CVE-2025-39739 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:41:11+00:00 | Vulnerability · Source |
| CVE-2025-39742 | suse_vex | SUSE CVE CVE-2025-39742 | first fixed: 2 known affected: 394 known not affected: 99 recommended: 725 | 2026-07-25T00:41:09+00:00 | Vulnerability · Source |
| CVE-2025-39746 | suse_vex | SUSE CVE CVE-2025-39746 | first fixed: 2 known affected: 344 known not affected: 172 recommended: 714 | 2026-07-25T00:41:03+00:00 | Vulnerability · Source |
| CVE-2025-39748 | suse_vex | SUSE CVE CVE-2025-39748 | first fixed: 2 known affected: 474 known not affected: 235 recommended: 300 | 2026-07-25T00:41:01+00:00 | Vulnerability · Source |
| CVE-2025-39749 | suse_vex | SUSE CVE CVE-2025-39749 | first fixed: 2 known affected: 560 known not affected: 99 recommended: 500 | 2026-07-25T00:40:58+00:00 | Vulnerability · Source |
| CVE-2025-39750 | suse_vex | SUSE CVE CVE-2025-39750 | first fixed: 2 known affected: 394 known not affected: 269 recommended: 500 | 2026-07-25T00:40:55+00:00 | Vulnerability · Source |
| CVE-2025-39758 | suse_vex | SUSE CVE CVE-2025-39758 | first fixed: 2 known affected: 451 known not affected: 208 recommended: 500 | 2026-07-25T00:40:48+00:00 | Vulnerability · Source |
| CVE-2025-39761 | suse_vex | SUSE CVE CVE-2025-39761 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 543 | 2026-07-25T00:40:43+00:00 | Vulnerability · Source |
| CVE-2025-39763 | suse_vex | SUSE CVE CVE-2025-39763 | first fixed: 2 known affected: 624 known not affected: 21 recommended: 523 | 2026-07-25T00:40:40+00:00 | Vulnerability · Source |
| CVE-2025-39764 | suse_vex | SUSE CVE CVE-2025-39764 | first fixed: 2 known affected: 635 recommended: 537 | 2026-07-25T00:40:38+00:00 | Vulnerability · Source |
| CVE-2025-39765 | suse_vex | SUSE CVE CVE-2025-39765 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:40:35+00:00 | Vulnerability · Source |
| CVE-2025-39768 | suse_vex | SUSE CVE CVE-2025-39768 | known not affected: 416 | 2026-07-25T00:40:31+00:00 | Vulnerability · Source |
| CVE-2025-39770 | suse_vex | SUSE CVE CVE-2025-39770 | first fixed: 2 known affected: 399 known not affected: 268 recommended: 500 | 2026-07-25T00:40:28+00:00 | Vulnerability · Source |
| CVE-2025-39775 | suse_vex | SUSE CVE CVE-2025-39775 | first fixed: 2 known affected: 229 known not affected: 211 recommended: 154 | 2026-07-25T00:40:25+00:00 | Vulnerability · Source |
| CVE-2025-39776 | suse_vex | SUSE CVE CVE-2025-39776 | known affected: 246 known not affected: 211 | 2026-07-25T00:40:23+00:00 | Vulnerability · Source |
| CVE-2025-39783 | suse_vex | SUSE CVE CVE-2025-39783 | first fixed: 2 known affected: 557 known not affected: 102 recommended: 500 | 2026-07-25T00:40:20+00:00 | Vulnerability · Source |
| CVE-2025-39789 | suse_vex | SUSE CVE CVE-2025-39789 | known affected: 358 known not affected: 99 | 2026-07-25T00:40:17+00:00 | Vulnerability · Source |
| CVE-2025-39790 | suse_vex | SUSE CVE CVE-2025-39790 | first fixed: 2 known affected: 344 known not affected: 153 recommended: 706 | 2026-07-25T00:40:15+00:00 | Vulnerability · Source |