VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38640 | suse_vex | SUSE CVE CVE-2025-38640 | first fixed: 2 known affected: 399 known not affected: 283 recommended: 508 | 2026-07-25T00:43:15+00:00 | Vulnerability · Source |
| CVE-2025-38643 | suse_vex | SUSE CVE CVE-2025-38643 | first fixed: 2 known affected: 583 known not affected: 99 recommended: 508 | 2026-07-25T00:43:13+00:00 | Vulnerability · Source |
| CVE-2025-38644 | suse_vex | SUSE CVE CVE-2025-38644 | first fixed: 2 known affected: 405 known not affected: 324 recommended: 936 | 2026-07-25T00:43:10+00:00 | Vulnerability · Source |
| CVE-2025-38645 | suse_vex | SUSE CVE CVE-2025-38645 | first fixed: 2 known affected: 583 known not affected: 99 recommended: 526 | 2026-07-25T00:43:08+00:00 | Vulnerability · Source |
| CVE-2025-38650 | suse_vex | SUSE CVE CVE-2025-38650 | known affected: 598 known not affected: 179 recommended: 354 | 2026-07-25T00:43:06+00:00 | Vulnerability · Source |
| CVE-2025-38654 | suse_vex | SUSE CVE CVE-2025-38654 | known not affected: 416 | 2026-07-25T00:43:05+00:00 | Vulnerability · Source |
| CVE-2025-38659 | suse_vex | SUSE CVE CVE-2025-38659 | first fixed: 2 known affected: 364 known not affected: 156 recommended: 714 | 2026-07-25T00:43:03+00:00 | Vulnerability · Source |
| CVE-2025-38664 | suse_vex | SUSE CVE CVE-2025-38664 | first fixed: 2 known affected: 376 known not affected: 99 recommended: 906 | 2026-07-25T00:43:00+00:00 | Vulnerability · Source |
| CVE-2025-38667 | suse_vex | SUSE CVE CVE-2025-38667 | known not affected: 416 | 2026-07-25T00:42:56+00:00 | Vulnerability · Source |
| CVE-2025-38668 | suse_vex | SUSE CVE CVE-2025-38668 | first fixed: 2 known affected: 572 known not affected: 102 recommended: 508 | 2026-07-25T00:42:54+00:00 | Vulnerability · Source |
| CVE-2025-38671 | suse_vex | SUSE CVE CVE-2025-38671 | first fixed: 2 known affected: 572 known not affected: 159 recommended: 508 | 2026-07-25T00:42:52+00:00 | Vulnerability · Source |
| CVE-2025-38674 | suse_vex | SUSE CVE CVE-2025-38674 | known not affected: 416 | 2026-07-25T00:42:50+00:00 | Vulnerability · Source |
| CVE-2025-38675 | suse_vex | SUSE CVE CVE-2025-38675 | known affected: 276 known not affected: 196 | 2026-07-25T00:42:49+00:00 | Vulnerability · Source |
| CVE-2025-38676 | suse_vex | SUSE CVE CVE-2025-38676 | first fixed: 2 known affected: 451 known not affected: 226 recommended: 508 | 2026-07-25T00:42:47+00:00 | Vulnerability · Source |
| CVE-2025-38678 | suse_vex | SUSE CVE CVE-2025-38678 | first fixed: 2 known affected: 349 known not affected: 156 recommended: 811 | 2026-07-25T00:42:44+00:00 | Vulnerability · Source |
| CVE-2025-38679 | suse_vex | SUSE CVE CVE-2025-38679 | first fixed: 2 known affected: 408 known not affected: 104 recommended: 508 | 2026-07-25T00:42:42+00:00 | Vulnerability · Source |
| CVE-2025-38680 | suse_vex | SUSE CVE CVE-2025-38680 | first fixed: 2 known affected: 630 known not affected: 32 recommended: 537 | 2026-07-25T00:42:41+00:00 | Vulnerability · Source |
| CVE-2025-38684 | suse_vex | SUSE CVE CVE-2025-38684 | first fixed: 2 known affected: 391 known not affected: 113 recommended: 759 | 2026-07-25T00:42:38+00:00 | Vulnerability · Source |
| CVE-2025-38685 | suse_vex | SUSE CVE CVE-2025-38685 | first fixed: 2 known affected: 356 known not affected: 66 recommended: 837 | 2026-07-25T00:42:36+00:00 | Vulnerability · Source |
| CVE-2025-38690 | suse_vex | SUSE CVE CVE-2025-38690 | known not affected: 401 | 2026-07-25T00:42:34+00:00 | Vulnerability · Source |
| CVE-2025-38691 | suse_vex | SUSE CVE CVE-2025-38691 | first fixed: 2 known affected: 630 known not affected: 32 recommended: 537 | 2026-07-25T00:42:32+00:00 | Vulnerability · Source |
| CVE-2025-38694 | suse_vex | SUSE CVE CVE-2025-38694 | first fixed: 2 known affected: 394 recommended: 500 | 2026-07-25T00:42:29+00:00 | Vulnerability · Source |
| CVE-2025-38695 | suse_vex | SUSE CVE CVE-2025-38695 | first fixed: 2 known affected: 624 known not affected: 21 recommended: 523 | 2026-07-25T00:42:27+00:00 | Vulnerability · Source |
| 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 |