VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
282291 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38444 | suse_vex | SUSE CVE CVE-2025-38444 | first fixed: 2 known affected: 594 known not affected: 154 recommended: 508 | 2026-07-19T17:49:28+00:00 | Vulnerability · Source |
| CVE-2025-38445 | suse_vex | SUSE CVE CVE-2025-38445 | first fixed: 2 known affected: 651 known not affected: 97 recommended: 508 | 2026-07-19T17:49:27+00:00 | Vulnerability · Source |
| CVE-2025-38446 | suse_vex | SUSE CVE CVE-2025-38446 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-19T17:49:25+00:00 | Vulnerability · Source |
| CVE-2025-38456 | suse_vex | SUSE CVE CVE-2025-38456 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 508 | 2026-07-19T17:49:24+00:00 | Vulnerability · Source |
| CVE-2025-38457 | suse_vex | SUSE CVE CVE-2025-38457 | first fixed: 2 known affected: 700 recommended: 538 | 2026-07-19T17:49:23+00:00 | Vulnerability · Source |
| CVE-2025-38458 | suse_vex | SUSE CVE CVE-2025-38458 | first fixed: 2 known affected: 748 recommended: 508 | 2026-07-19T17:49:21+00:00 | Vulnerability · Source |
| CVE-2025-38459 | suse_vex | SUSE CVE CVE-2025-38459 | first fixed: 2 known affected: 467 known not affected: 281 recommended: 582 | 2026-07-19T17:49:20+00:00 | Vulnerability · Source |
| CVE-2025-38460 | suse_vex | SUSE CVE CVE-2025-38460 | first fixed: 2 known affected: 515 recommended: 823 | 2026-07-19T17:49:18+00:00 | Vulnerability · Source |
| CVE-2025-38461 | suse_vex | SUSE CVE CVE-2025-38461 | first fixed: 2 known affected: 572 known not affected: 154 recommended: 571 | 2026-07-19T17:49:17+00:00 | Vulnerability · Source |
| CVE-2025-38463 | suse_vex | SUSE CVE CVE-2025-38463 | first fixed: 2 known affected: 445 known not affected: 281 recommended: 508 | 2026-07-19T17:49:16+00:00 | Vulnerability · Source |
| CVE-2025-38464 | suse_vex | SUSE CVE CVE-2025-38464 | first fixed: 2 known affected: 716 known not affected: 6 recommended: 601 | 2026-07-19T17:49:14+00:00 | Vulnerability · Source |
| CVE-2025-38467 | suse_vex | SUSE CVE CVE-2025-38467 | first fixed: 2 known affected: 605 known not affected: 110 recommended: 508 | 2026-07-19T17:49:13+00:00 | Vulnerability · Source |
| CVE-2025-38485 | suse_vex | SUSE CVE CVE-2025-38485 | first fixed: 2 known affected: 394 known not affected: 321 recommended: 508 | 2026-07-19T17:49:11+00:00 | Vulnerability · Source |
| CVE-2025-38488 | suse_vex | SUSE CVE CVE-2025-38488 | first fixed: 2 known affected: 376 known not affected: 69 recommended: 892 | 2026-07-19T17:49:10+00:00 | Vulnerability · Source |
| CVE-2025-38491 | suse_vex | SUSE CVE CVE-2025-38491 | first fixed: 2 known affected: 467 known not affected: 281 recommended: 508 | 2026-07-19T17:49:08+00:00 | Vulnerability · Source |
| CVE-2025-38500 | suse_vex | SUSE CVE CVE-2025-38500 | first fixed: 2 known affected: 467 known not affected: 281 recommended: 613 | 2026-07-19T17:49:07+00:00 | Vulnerability · Source |
| CVE-2025-38510 | suse_vex | SUSE CVE CVE-2025-38510 | first fixed: 2 known affected: 394 known not affected: 347 recommended: 526 | 2026-07-19T17:49:05+00:00 | Vulnerability · Source |
| CVE-2025-38514 | suse_vex | SUSE CVE CVE-2025-38514 | first fixed: 2 known affected: 455 known not affected: 55 recommended: 508 | 2026-07-19T17:49:04+00:00 | Vulnerability · Source |
| CVE-2025-38524 | suse_vex | SUSE CVE CVE-2025-38524 | first fixed: 2 known affected: 694 known not affected: 54 recommended: 508 | 2026-07-19T17:49:03+00:00 | Vulnerability · Source |
| CVE-2025-38544 | suse_vex | SUSE CVE CVE-2025-38544 | first fixed: 2 known affected: 630 known not affected: 50 recommended: 508 | 2026-07-19T17:49:01+00:00 | Vulnerability · Source |
| CVE-2025-38546 | suse_vex | SUSE CVE CVE-2025-38546 | first fixed: 2 known affected: 533 known not affected: 6 recommended: 816 | 2026-07-19T17:49:00+00:00 | Vulnerability · Source |
| CVE-2025-38552 | suse_vex | SUSE CVE CVE-2025-38552 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 500 | 2026-07-19T17:48:58+00:00 | Vulnerability · Source |
| CVE-2025-38554 | suse_vex | SUSE CVE CVE-2025-38554 | first fixed: 2 known not affected: 446 recommended: 158 | 2026-07-19T17:48:57+00:00 | Vulnerability · Source |
| CVE-2025-38574 | suse_vex | SUSE CVE CVE-2025-38574 | first fixed: 2 known affected: 650 recommended: 538 | 2026-07-19T17:48:56+00:00 | Vulnerability · Source |
| CVE-2025-38584 | suse_vex | SUSE CVE CVE-2025-38584 | first fixed: 2 known affected: 680 recommended: 500 | 2026-07-19T17:48:54+00:00 | Vulnerability · Source |
| CVE-2025-38585 | suse_vex | SUSE CVE CVE-2025-38585 | first fixed: 2 known affected: 462 known not affected: 286 recommended: 508 | 2026-07-19T17:48:53+00:00 | Vulnerability · Source |
| CVE-2025-38593 | suse_vex | SUSE CVE CVE-2025-38593 | first fixed: 2 known affected: 456 known not affected: 224 recommended: 508 | 2026-07-19T17:48:52+00:00 | Vulnerability · Source |
| CVE-2025-38597 | suse_vex | SUSE CVE CVE-2025-38597 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 508 | 2026-07-19T17:48:50+00:00 | Vulnerability · Source |
| CVE-2025-38618 | suse_vex | SUSE CVE CVE-2025-38618 | first fixed: 2 known affected: 531 known not affected: 6 recommended: 935 | 2026-07-19T17:48:49+00:00 | Vulnerability · Source |
| CVE-2025-38621 | suse_vex | SUSE CVE CVE-2025-38621 | first fixed: 2 known affected: 394 known not affected: 347 recommended: 508 | 2026-07-19T17:48:47+00:00 | Vulnerability · Source |
| CVE-2025-38640 | suse_vex | SUSE CVE CVE-2025-38640 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 508 | 2026-07-19T17:48:46+00:00 | Vulnerability · Source |
| CVE-2025-38653 | suse_vex | SUSE CVE CVE-2025-38653 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 583 | 2026-07-19T17:48:45+00:00 | Vulnerability · Source |
| CVE-2025-38658 | suse_vex | SUSE CVE CVE-2025-38658 | first fixed: 2 known not affected: 414 recommended: 154 | 2026-07-19T17:48:43+00:00 | Vulnerability · Source |
| CVE-2025-38660 | suse_vex | SUSE CVE CVE-2025-38660 | first fixed: 2 known affected: 456 known not affected: 224 recommended: 508 | 2026-07-19T17:48:42+00:00 | Vulnerability · Source |
| CVE-2025-38678 | suse_vex | SUSE CVE CVE-2025-38678 | first fixed: 2 known affected: 349 known not affected: 154 recommended: 811 | 2026-07-19T17:48:40+00:00 | Vulnerability · Source |
| CVE-2025-38679 | suse_vex | SUSE CVE CVE-2025-38679 | first fixed: 2 known affected: 408 known not affected: 102 recommended: 508 | 2026-07-19T17:48:39+00:00 | Vulnerability · Source |
| CVE-2025-38701 | suse_vex | SUSE CVE CVE-2025-38701 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 538 | 2026-07-19T17:48:38+00:00 | Vulnerability · Source |
| CVE-2025-38709 | suse_vex | SUSE CVE CVE-2025-38709 | first fixed: 2 known affected: 612 known not affected: 53 recommended: 508 | 2026-07-19T17:48:36+00:00 | Vulnerability · Source |
| CVE-2025-38721 | suse_vex | SUSE CVE CVE-2025-38721 | first fixed: 2 known affected: 660 recommended: 508 | 2026-07-19T17:48:34+00:00 | Vulnerability · Source |
| CVE-2025-39676 | suse_vex | SUSE CVE CVE-2025-39676 | first fixed: 2 known affected: 624 known not affected: 6 recommended: 530 | 2026-07-19T17:48:33+00:00 | Vulnerability · Source |
| CVE-2025-39678 | suse_vex | SUSE CVE CVE-2025-39678 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 508 | 2026-07-19T17:48:31+00:00 | Vulnerability · Source |
| CVE-2025-39681 | suse_vex | SUSE CVE CVE-2025-39681 | first fixed: 2 known affected: 549 known not affected: 111 recommended: 500 | 2026-07-19T17:48:30+00:00 | Vulnerability · Source |
| CVE-2025-39683 | suse_vex | SUSE CVE CVE-2025-39683 | first fixed: 2 known affected: 596 known not affected: 69 recommended: 500 | 2026-07-19T17:48:29+00:00 | Vulnerability · Source |
| CVE-2025-39684 | suse_vex | SUSE CVE CVE-2025-39684 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-19T17:48:27+00:00 | Vulnerability · Source |
| CVE-2025-39686 | suse_vex | SUSE CVE CVE-2025-39686 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-19T17:48:26+00:00 | Vulnerability · Source |
| CVE-2025-39689 | suse_vex | SUSE CVE CVE-2025-39689 | first fixed: 2 known affected: 276 known not affected: 22 recommended: 425 | 2026-07-19T17:48:25+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: 744 | 2026-07-19T17:48:24+00:00 | Vulnerability · Source |
| CVE-2025-39694 | suse_vex | SUSE CVE CVE-2025-39694 | first fixed: 2 known affected: 456 known not affected: 209 recommended: 543 | 2026-07-19T17:48:23+00:00 | Vulnerability · Source |
| CVE-2025-39706 | suse_vex | SUSE CVE CVE-2025-39706 | first fixed: 2 known affected: 580 known not affected: 80 recommended: 523 | 2026-07-19T17:48:21+00:00 | Vulnerability · Source |
| CVE-2025-39738 | suse_vex | SUSE CVE CVE-2025-39738 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-19T17:48:20+00:00 | Vulnerability · Source |