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-38525 | suse_vex | SUSE CVE CVE-2025-38525 | known not affected: 416 | 2026-07-25T00:45:08+00:00 | Vulnerability · Source |
| CVE-2025-38526 | suse_vex | SUSE CVE CVE-2025-38526 | first fixed: 2 known affected: 399 known not affected: 283 recommended: 508 | 2026-07-25T00:45:07+00:00 | Vulnerability · Source |
| CVE-2025-38527 | suse_vex | SUSE CVE CVE-2025-38527 | first fixed: 2 known affected: 639 known not affected: 6 recommended: 608 | 2026-07-25T00:45:05+00:00 | Vulnerability · Source |
| CVE-2025-38528 | suse_vex | SUSE CVE CVE-2025-38528 | first fixed: 2 known affected: 585 known not affected: 165 recommended: 508 | 2026-07-25T00:45:03+00:00 | Vulnerability · Source |
| CVE-2025-38529 | suse_vex | SUSE CVE CVE-2025-38529 | first fixed: 2 known affected: 633 known not affected: 98 recommended: 526 | 2026-07-25T00:45:01+00:00 | Vulnerability · Source |
| CVE-2025-38530 | suse_vex | SUSE CVE CVE-2025-38530 | first fixed: 2 known affected: 639 known not affected: 92 recommended: 526 | 2026-07-25T00:44:59+00:00 | Vulnerability · Source |
| CVE-2025-38533 | suse_vex | SUSE CVE CVE-2025-38533 | first fixed: 2 known affected: 394 known not affected: 280 recommended: 508 | 2026-07-25T00:44:56+00:00 | Vulnerability · Source |
| CVE-2025-38534 | suse_vex | SUSE CVE CVE-2025-38534 | known not affected: 416 | 2026-07-25T00:44:54+00:00 | Vulnerability · Source |
| CVE-2025-38535 | suse_vex | SUSE CVE CVE-2025-38535 | first fixed: 2 known affected: 558 known not affected: 173 recommended: 526 | 2026-07-25T00:44:52+00:00 | Vulnerability · Source |
| CVE-2025-38537 | suse_vex | SUSE CVE CVE-2025-38537 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 526 | 2026-07-25T00:44:50+00:00 | Vulnerability · Source |
| CVE-2025-38538 | suse_vex | SUSE CVE CVE-2025-38538 | first fixed: 2 known affected: 633 known not affected: 109 recommended: 526 | 2026-07-25T00:44:48+00:00 | Vulnerability · Source |
| CVE-2025-38539 | suse_vex | SUSE CVE CVE-2025-38539 | first fixed: 2 known affected: 650 recommended: 587 | 2026-07-25T00:44:47+00:00 | Vulnerability · Source |
| CVE-2025-38540 | suse_vex | SUSE CVE CVE-2025-38540 | first fixed: 2 known affected: 639 known not affected: 60 recommended: 526 | 2026-07-25T00:44:45+00:00 | Vulnerability · Source |
| CVE-2025-38541 | suse_vex | SUSE CVE CVE-2025-38541 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 526 | 2026-07-25T00:44:43+00:00 | Vulnerability · Source |
| CVE-2025-38543 | suse_vex | SUSE CVE CVE-2025-38543 | first fixed: 2 known affected: 451 known not affected: 280 recommended: 526 | 2026-07-25T00:44:40+00:00 | Vulnerability · Source |
| CVE-2025-38548 | suse_vex | SUSE CVE CVE-2025-38548 | first fixed: 2 known affected: 521 known not affected: 210 recommended: 526 | 2026-07-25T00:44:38+00:00 | Vulnerability · Source |
| CVE-2025-38549 | suse_vex | SUSE CVE CVE-2025-38549 | first fixed: 2 known affected: 494 known not affected: 283 recommended: 276 | 2026-07-25T00:44:36+00:00 | Vulnerability · Source |
| CVE-2025-38556 | suse_vex | SUSE CVE CVE-2025-38556 | first fixed: 2 known affected: 654 recommended: 621 | 2026-07-25T00:44:29+00:00 | Vulnerability · Source |
| CVE-2025-38560 | suse_vex | SUSE CVE CVE-2025-38560 | first fixed: 2 known affected: 426 known not affected: 156 recommended: 714 | 2026-07-25T00:44:27+00:00 | Vulnerability · Source |
| CVE-2025-38565 | suse_vex | SUSE CVE CVE-2025-38565 | first fixed: 2 known affected: 185 known not affected: 6 recommended: 705 | 2026-07-25T00:44:23+00:00 | Vulnerability · Source |
| CVE-2025-38566 | suse_vex | SUSE CVE CVE-2025-38566 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 617 | 2026-07-25T00:44:21+00:00 | Vulnerability · Source |
| CVE-2025-38571 | suse_vex | SUSE CVE CVE-2025-38571 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 551 | 2026-07-25T00:44:18+00:00 | Vulnerability · Source |
| CVE-2025-38572 | suse_vex | SUSE CVE CVE-2025-38572 | first fixed: 2 known affected: 344 known not affected: 154 recommended: 905 | 2026-07-25T00:44:17+00:00 | Vulnerability · Source |
| 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 |