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-38573 | suse_vex | SUSE CVE CVE-2025-38573 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T00:44:15+00:00 | Vulnerability · Source |
| CVE-2025-38576 | suse_vex | SUSE CVE CVE-2025-38576 | first fixed: 2 known affected: 633 known not affected: 79 recommended: 508 | 2026-07-25T00:44:13+00:00 | Vulnerability · Source |
| CVE-2025-38581 | suse_vex | SUSE CVE CVE-2025-38581 | first fixed: 2 known affected: 572 known not affected: 171 recommended: 508 | 2026-07-25T00:44:12+00:00 | Vulnerability · Source |
| CVE-2025-38583 | suse_vex | SUSE CVE CVE-2025-38583 | first fixed: 2 known affected: 521 known not affected: 222 recommended: 508 | 2026-07-25T00:44:10+00:00 | Vulnerability · Source |
| CVE-2025-38585 | suse_vex | SUSE CVE CVE-2025-38585 | first fixed: 2 known affected: 462 known not affected: 288 recommended: 508 | 2026-07-25T00:44:08+00:00 | Vulnerability · Source |
| CVE-2025-38587 | suse_vex | SUSE CVE CVE-2025-38587 | first fixed: 2 known affected: 394 known not affected: 349 recommended: 508 | 2026-07-25T00:44:06+00:00 | Vulnerability · Source |
| CVE-2025-38588 | suse_vex | SUSE CVE CVE-2025-38588 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 552 | 2026-07-25T00:44:04+00:00 | Vulnerability · Source |
| CVE-2025-38590 | suse_vex | SUSE CVE CVE-2025-38590 | first fixed: 2 known affected: 569 known not affected: 113 recommended: 526 | 2026-07-25T00:44:02+00:00 | Vulnerability · Source |
| CVE-2025-38591 | suse_vex | SUSE CVE CVE-2025-38591 | first fixed: 2 known affected: 693 known not affected: 27 recommended: 531 | 2026-07-25T00:44:00+00:00 | Vulnerability · Source |
| CVE-2025-38595 | suse_vex | SUSE CVE CVE-2025-38595 | first fixed: 2 known affected: 572 known not affected: 102 recommended: 508 | 2026-07-25T00:43:57+00:00 | Vulnerability · Source |
| CVE-2025-38601 | suse_vex | SUSE CVE CVE-2025-38601 | first fixed: 2 known affected: 521 known not affected: 222 recommended: 508 | 2026-07-25T00:43:55+00:00 | Vulnerability · Source |
| CVE-2025-38602 | suse_vex | SUSE CVE CVE-2025-38602 | first fixed: 2 known affected: 645 known not affected: 73 recommended: 545 | 2026-07-25T00:43:52+00:00 | Vulnerability · Source |
| CVE-2025-38604 | suse_vex | SUSE CVE CVE-2025-38604 | first fixed: 2 known affected: 639 known not affected: 73 recommended: 531 | 2026-07-25T00:43:50+00:00 | Vulnerability · Source |
| CVE-2025-38606 | suse_vex | SUSE CVE CVE-2025-38606 | known not affected: 416 | 2026-07-25T00:43:48+00:00 | Vulnerability · Source |
| CVE-2025-38609 | suse_vex | SUSE CVE CVE-2025-38609 | first fixed: 2 known affected: 521 known not affected: 222 recommended: 508 | 2026-07-25T00:43:44+00:00 | Vulnerability · Source |
| CVE-2025-38612 | suse_vex | SUSE CVE CVE-2025-38612 | first fixed: 2 known affected: 558 known not affected: 185 recommended: 508 | 2026-07-25T00:43:41+00:00 | Vulnerability · Source |
| CVE-2025-38613 | suse_vex | SUSE CVE CVE-2025-38613 | known not affected: 416 | 2026-07-25T00:43:39+00:00 | Vulnerability · Source |
| CVE-2025-38621 | suse_vex | SUSE CVE CVE-2025-38621 | first fixed: 2 known affected: 394 known not affected: 349 recommended: 508 | 2026-07-25T00:43:35+00:00 | Vulnerability · Source |
| CVE-2025-38622 | suse_vex | SUSE CVE CVE-2025-38622 | first fixed: 2 known affected: 583 known not affected: 99 recommended: 508 | 2026-07-25T00:43:33+00:00 | Vulnerability · Source |
| CVE-2025-38623 | suse_vex | SUSE CVE CVE-2025-38623 | first fixed: 2 known affected: 630 known not affected: 22 recommended: 531 | 2026-07-25T00:43:31+00:00 | Vulnerability · Source |
| CVE-2025-38624 | suse_vex | SUSE CVE CVE-2025-38624 | first fixed: 2 known affected: 619 known not affected: 93 recommended: 531 | 2026-07-25T00:43:29+00:00 | Vulnerability · Source |
| CVE-2025-38630 | suse_vex | SUSE CVE CVE-2025-38630 | first fixed: 2 known affected: 455 known not affected: 276 recommended: 508 | 2026-07-25T00:43:27+00:00 | Vulnerability · Source |
| CVE-2025-38632 | suse_vex | SUSE CVE CVE-2025-38632 | first fixed: 2 known affected: 394 known not affected: 305 recommended: 545 | 2026-07-25T00:43:25+00:00 | Vulnerability · Source |
| CVE-2025-38634 | suse_vex | SUSE CVE CVE-2025-38634 | first fixed: 2 known affected: 521 known not affected: 210 recommended: 508 | 2026-07-25T00:43:23+00:00 | Vulnerability · Source |
| CVE-2025-38635 | suse_vex | SUSE CVE CVE-2025-38635 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 508 | 2026-07-25T00:43:21+00:00 | Vulnerability · Source |
| CVE-2025-38638 | suse_vex | SUSE CVE CVE-2025-38638 | known not affected: 416 | 2026-07-25T00:43:19+00:00 | Vulnerability · Source |
| CVE-2025-38639 | suse_vex | SUSE CVE CVE-2025-38639 | first fixed: 2 known affected: 639 known not affected: 11 recommended: 545 | 2026-07-25T00:43:17+00:00 | Vulnerability · Source |
| 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 |