VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292126 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38062 | suse_vex | SUSE CVE CVE-2025-38062 | first fixed: 2 known affected: 629 known not affected: 97 recommended: 508 | 2026-07-22T16:43:54+00:00 | Vulnerability · Source |
| CVE-2025-38085 | suse_vex | SUSE CVE CVE-2025-38085 | first fixed: 2 known affected: 559 recommended: 782 | 2026-07-22T16:43:52+00:00 | Vulnerability · Source |
| CVE-2025-38165 | suse_vex | SUSE CVE CVE-2025-38165 | first fixed: 2 known affected: 51 known not affected: 281 recommended: 508 | 2026-07-22T16:43:48+00:00 | Vulnerability · Source |
| CVE-2025-38182 | suse_vex | SUSE CVE CVE-2025-38182 | first fixed: 2 known affected: 445 known not affected: 281 recommended: 508 | 2026-07-22T16:43:46+00:00 | Vulnerability · Source |
| CVE-2025-38205 | suse_vex | SUSE CVE CVE-2025-38205 | first fixed: 2 known affected: 467 known not affected: 281 recommended: 508 | 2026-07-22T16:43:44+00:00 | Vulnerability · Source |
| CVE-2025-38222 | suse_vex | SUSE CVE CVE-2025-38222 | first fixed: 2 known affected: 694 known not affected: 6 recommended: 538 | 2026-07-22T16:43:43+00:00 | Vulnerability · Source |
| CVE-2025-38244 | suse_vex | SUSE CVE CVE-2025-38244 | first fixed: 2 known affected: 643 known not affected: 83 recommended: 508 | 2026-07-22T16:43:41+00:00 | Vulnerability · Source |
| CVE-2025-38255 | suse_vex | SUSE CVE CVE-2025-38255 | first fixed: 2 known affected: 456 known not affected: 224 recommended: 508 | 2026-07-22T16:43:40+00:00 | Vulnerability · Source |
| CVE-2025-38263 | suse_vex | SUSE CVE CVE-2025-38263 | first fixed: 2 known affected: 634 known not affected: 20 recommended: 538 | 2026-07-22T16:43:38+00:00 | Vulnerability · Source |
| CVE-2025-38312 | suse_vex | SUSE CVE CVE-2025-38312 | first fixed: 2 known affected: 639 known not affected: 62 recommended: 511 | 2026-07-22T16:43:36+00:00 | Vulnerability · Source |
| CVE-2025-38337 | suse_vex | SUSE CVE CVE-2025-38337 | first fixed: 2 known affected: 694 known not affected: 6 recommended: 538 | 2026-07-22T16:43:34+00:00 | Vulnerability · Source |
| CVE-2025-38351 | suse_vex | SUSE CVE CVE-2025-38351 | first fixed: 2 known affected: 399 known not affected: 281 recommended: 543 | 2026-07-22T16:43:31+00:00 | Vulnerability · Source |
| CVE-2025-38399 | suse_vex | SUSE CVE CVE-2025-38399 | first fixed: 2 known affected: 631 known not affected: 95 recommended: 508 | 2026-07-22T16:43:29+00:00 | Vulnerability · Source |
| CVE-2025-38402 | suse_vex | SUSE CVE CVE-2025-38402 | first fixed: 2 known affected: 526 known not affected: 154 recommended: 508 | 2026-07-22T16:43:28+00:00 | Vulnerability · Source |
| CVE-2025-38418 | suse_vex | SUSE CVE CVE-2025-38418 | first fixed: 2 known affected: 526 known not affected: 154 recommended: 508 | 2026-07-22T16:43:26+00:00 | Vulnerability · Source |
| CVE-2025-38419 | suse_vex | SUSE CVE CVE-2025-38419 | first fixed: 2 known affected: 526 known not affected: 154 recommended: 508 | 2026-07-22T16:43:25+00:00 | Vulnerability · Source |
| CVE-2025-38426 | suse_vex | SUSE CVE CVE-2025-38426 | first fixed: 2 known affected: 615 known not affected: 111 recommended: 508 | 2026-07-22T16:43:23+00:00 | Vulnerability · Source |
| CVE-2025-38439 | suse_vex | SUSE CVE CVE-2025-38439 | first fixed: 2 known affected: 651 known not affected: 97 recommended: 508 | 2026-07-22T16:43:22+00:00 | Vulnerability · Source |
| CVE-2025-38441 | suse_vex | SUSE CVE CVE-2025-38441 | first fixed: 2 known affected: 524 known not affected: 224 recommended: 508 | 2026-07-22T16:43:20+00:00 | Vulnerability · Source |
| CVE-2025-38444 | suse_vex | SUSE CVE CVE-2025-38444 | first fixed: 2 known affected: 594 known not affected: 154 recommended: 508 | 2026-07-22T16:43:19+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-22T16:43:17+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-22T16:43:16+00:00 | Vulnerability · Source |
| CVE-2025-38457 | suse_vex | SUSE CVE CVE-2025-38457 | first fixed: 2 known affected: 700 recommended: 538 | 2026-07-22T16:43:14+00:00 | Vulnerability · Source |
| CVE-2025-38458 | suse_vex | SUSE CVE CVE-2025-38458 | first fixed: 2 known affected: 748 recommended: 508 | 2026-07-22T16:43:13+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-22T16:43:12+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-22T16:43:09+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-22T16:43:07+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-22T16:43:06+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-22T16:43:03+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-22T16:43:01+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-22T16:42:59+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-22T16:42:58+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-22T16:42:56+00:00 | Vulnerability · Source |
| CVE-2025-38574 | suse_vex | SUSE CVE CVE-2025-38574 | first fixed: 2 known affected: 650 recommended: 538 | 2026-07-22T16:42:55+00:00 | Vulnerability · Source |
| CVE-2025-38584 | suse_vex | SUSE CVE CVE-2025-38584 | first fixed: 2 known affected: 680 recommended: 500 | 2026-07-22T16:42: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-22T16:42: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-22T16:42:50+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-22T16:42:45+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-22T16:42:44+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-22T16:42:41+00:00 | Vulnerability · Source |
| CVE-2025-38713 | suse_vex | SUSE CVE CVE-2025-38713 | known affected: 441 recommended: 676 | 2026-07-22T16:42:40+00:00 | Vulnerability · Source |
| CVE-2025-38714 | suse_vex | SUSE CVE CVE-2025-38714 | known affected: 652 recommended: 376 | 2026-07-22T16:42:38+00:00 | Vulnerability · Source |
| CVE-2025-38721 | suse_vex | SUSE CVE CVE-2025-38721 | first fixed: 2 known affected: 660 recommended: 508 | 2026-07-22T16:42:37+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-22T16:42:35+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-22T16:42:33+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-22T16:42:32+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-22T16:42:30+00:00 | Vulnerability · Source |
| CVE-2025-39684 | suse_vex | SUSE CVE CVE-2025-39684 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-22T16:42:28+00:00 | Vulnerability · Source |
| CVE-2025-39686 | suse_vex | SUSE CVE CVE-2025-39686 | first fixed: 2 known affected: 665 recommended: 500 | 2026-07-22T16:42:27+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-22T16:42:25+00:00 | Vulnerability · Source |