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-39891 | suse_vex | SUSE CVE CVE-2025-39891 | first fixed: 2 known affected: 618 known not affected: 9 recommended: 500 | 2026-07-25T00:38:43+00:00 | Vulnerability · Source |
| CVE-2025-39892 | suse_vex | SUSE CVE CVE-2025-39892 | known not affected: 416 recommended: 27 | 2026-07-25T00:38:41+00:00 | Vulnerability · Source |
| CVE-2025-39893 | suse_vex | SUSE CVE CVE-2025-39893 | known not affected: 416 | 2026-07-25T00:38:39+00:00 | Vulnerability · Source |
| CVE-2025-39900 | suse_vex | SUSE CVE CVE-2025-39900 | first fixed: 2 known affected: 394 known not affected: 376 recommended: 265 | 2026-07-25T00:38:31+00:00 | Vulnerability · Source |
| CVE-2025-39901 | suse_vex | SUSE CVE CVE-2025-39901 | known affected: 230 | 2026-07-25T00:38:29+00:00 | Vulnerability · Source |
| CVE-2025-39903 | suse_vex | SUSE CVE CVE-2025-39903 | first fixed: 2 known affected: 394 known not affected: 435 recommended: 154 | 2026-07-25T00:38:27+00:00 | Vulnerability · Source |
| CVE-2025-39906 | suse_vex | SUSE CVE CVE-2025-39906 | known not affected: 416 | 2026-07-25T00:38:25+00:00 | Vulnerability · Source |
| CVE-2025-39907 | suse_vex | SUSE CVE CVE-2025-39907 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:38:23+00:00 | Vulnerability · Source |
| CVE-2025-39913 | suse_vex | SUSE CVE CVE-2025-39913 | first fixed: 2 known affected: 596 known not affected: 36 recommended: 425 | 2026-07-25T00:38:20+00:00 | Vulnerability · Source |
| CVE-2025-39920 | suse_vex | SUSE CVE CVE-2025-39920 | known affected: 400 known not affected: 265 recommended: 346 | 2026-07-25T00:38:16+00:00 | Vulnerability · Source |
| CVE-2025-39923 | suse_vex | SUSE CVE CVE-2025-39923 | first fixed: 2 known affected: 604 known not affected: 25 recommended: 523 | 2026-07-25T00:38:13+00:00 | Vulnerability · Source |
| CVE-2025-39925 | suse_vex | SUSE CVE CVE-2025-39925 | first fixed: 2 known affected: 506 known not affected: 153 recommended: 583 | 2026-07-25T00:38:11+00:00 | Vulnerability · Source |
| CVE-2025-39941 | suse_vex | SUSE CVE CVE-2025-39941 | known not affected: 416 | 2026-07-25T00:38:07+00:00 | Vulnerability · Source |
| CVE-2025-39947 | suse_vex | SUSE CVE CVE-2025-39947 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:38:01+00:00 | Vulnerability · Source |
| CVE-2025-39948 | suse_vex | SUSE CVE CVE-2025-39948 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:59+00:00 | Vulnerability · Source |
| CVE-2025-39951 | suse_vex | SUSE CVE CVE-2025-39951 | known not affected: 416 | 2026-07-25T00:37:56+00:00 | Vulnerability · Source |
| CVE-2025-39952 | suse_vex | SUSE CVE CVE-2025-39952 | first fixed: 2 known affected: 557 known not affected: 120 recommended: 500 | 2026-07-25T00:37:53+00:00 | Vulnerability · Source |
| CVE-2025-39955 | suse_vex | SUSE CVE CVE-2025-39955 | first fixed: 2 known affected: 629 known not affected: 6 recommended: 611 | 2026-07-25T00:37:51+00:00 | Vulnerability · Source |
| CVE-2025-39957 | suse_vex | SUSE CVE CVE-2025-39957 | first fixed: 2 known affected: 618 known not affected: 59 recommended: 500 | 2026-07-25T00:37:48+00:00 | Vulnerability · Source |
| CVE-2025-39960 | suse_vex | SUSE CVE CVE-2025-39960 | known not affected: 416 | 2026-07-25T00:37:46+00:00 | Vulnerability · Source |
| CVE-2025-39962 | suse_vex | SUSE CVE CVE-2025-39962 | known not affected: 416 | 2026-07-25T00:37:45+00:00 | Vulnerability · Source |
| CVE-2025-39965 | suse_vex | SUSE CVE CVE-2025-39965 | first fixed: 2 known not affected: 171 recommended: 656 | 2026-07-25T00:37:41+00:00 | Vulnerability · Source |
| CVE-2025-39968 | suse_vex | SUSE CVE CVE-2025-39968 | first fixed: 2 known affected: 354 known not affected: 87 recommended: 794 | 2026-07-25T00:37:39+00:00 | Vulnerability · Source |
| CVE-2025-39969 | suse_vex | SUSE CVE CVE-2025-39969 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:37+00:00 | Vulnerability · Source |
| CVE-2025-39972 | suse_vex | SUSE CVE CVE-2025-39972 | first fixed: 2 known affected: 394 known not affected: 235 recommended: 523 | 2026-07-25T00:37:33+00:00 | Vulnerability · Source |
| CVE-2025-39975 | suse_vex | SUSE CVE CVE-2025-39975 | known not affected: 416 | 2026-07-25T00:37:28+00:00 | Vulnerability · Source |
| CVE-2025-39977 | suse_vex | SUSE CVE CVE-2025-39977 | first fixed: 2 known affected: 407 known not affected: 156 recommended: 695 | 2026-07-25T00:37:25+00:00 | Vulnerability · Source |
| CVE-2025-39980 | suse_vex | SUSE CVE CVE-2025-39980 | first fixed: 2 known affected: 549 known not affected: 113 recommended: 500 | 2026-07-25T00:37:22+00:00 | Vulnerability · Source |
| CVE-2025-39985 | suse_vex | SUSE CVE CVE-2025-39985 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:12+00:00 | Vulnerability · Source |
| CVE-2025-39987 | suse_vex | SUSE CVE CVE-2025-39987 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:09+00:00 | Vulnerability · Source |
| CVE-2025-39988 | suse_vex | SUSE CVE CVE-2025-39988 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:37:06+00:00 | Vulnerability · Source |
| CVE-2025-39991 | suse_vex | SUSE CVE CVE-2025-39991 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 506 | 2026-07-25T00:37:03+00:00 | Vulnerability · Source |
| CVE-2025-39993 | suse_vex | SUSE CVE CVE-2025-39993 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 539 | 2026-07-25T00:37:00+00:00 | Vulnerability · Source |
| CVE-2025-39996 | suse_vex | SUSE CVE CVE-2025-39996 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 506 | 2026-07-25T00:36:56+00:00 | Vulnerability · Source |
| CVE-2025-40010 | suse_vex | SUSE CVE CVE-2025-40010 | known affected: 506 known not affected: 159 recommended: 346 | 2026-07-25T00:36:49+00:00 | Vulnerability · Source |
| CVE-2025-40013 | suse_vex | SUSE CVE CVE-2025-40013 | first fixed: 2 known affected: 399 known not affected: 268 recommended: 506 | 2026-07-25T00:36:46+00:00 | Vulnerability · Source |
| CVE-2025-40016 | suse_vex | SUSE CVE CVE-2025-40016 | first fixed: 2 known affected: 400 known not affected: 277 recommended: 506 | 2026-07-25T00:36:43+00:00 | Vulnerability · Source |
| CVE-2025-40018 | suse_vex | SUSE CVE CVE-2025-40018 | first fixed: 2 known affected: 410 known not affected: 19 recommended: 916 | 2026-07-25T00:36:40+00:00 | Vulnerability · Source |
| CVE-2025-40019 | suse_vex | SUSE CVE CVE-2025-40019 | first fixed: 2 known affected: 391 known not affected: 125 recommended: 706 | 2026-07-25T00:36:37+00:00 | Vulnerability · Source |
| CVE-2025-40020 | suse_vex | SUSE CVE CVE-2025-40020 | first fixed: 2 known affected: 394 known not affected: 274 recommended: 500 | 2026-07-25T00:36:34+00:00 | Vulnerability · Source |
| CVE-2025-40029 | suse_vex | SUSE CVE CVE-2025-40029 | first fixed: 2 known affected: 533 known not affected: 135 recommended: 506 | 2026-07-25T00:36:27+00:00 | Vulnerability · Source |
| CVE-2025-40032 | suse_vex | SUSE CVE CVE-2025-40032 | first fixed: 2 known affected: 506 known not affected: 150 recommended: 506 | 2026-07-25T00:36:24+00:00 | Vulnerability · Source |
| CVE-2025-40036 | suse_vex | SUSE CVE CVE-2025-40036 | first fixed: 2 known affected: 394 known not affected: 273 recommended: 506 | 2026-07-25T00:36:20+00:00 | Vulnerability · Source |
| CVE-2025-40043 | suse_vex | SUSE CVE CVE-2025-40043 | first fixed: 2 known affected: 618 known not affected: 38 recommended: 506 | 2026-07-25T00:36:16+00:00 | Vulnerability · Source |
| CVE-2025-40044 | suse_vex | SUSE CVE CVE-2025-40044 | first fixed: 2 known affected: 478 recommended: 739 | 2026-07-25T00:36:14+00:00 | Vulnerability · Source |
| CVE-2025-40045 | suse_vex | SUSE CVE CVE-2025-40045 | first fixed: 2 known not affected: 407 recommended: 178 | 2026-07-25T00:36:11+00:00 | Vulnerability · Source |
| CVE-2025-40051 | suse_vex | SUSE CVE CVE-2025-40051 | first fixed: 2 known affected: 451 known not affected: 211 recommended: 506 | 2026-07-25T00:36:08+00:00 | Vulnerability · Source |
| CVE-2025-40056 | suse_vex | SUSE CVE CVE-2025-40056 | first fixed: 2 known affected: 394 known not affected: 268 recommended: 506 | 2026-07-25T00:36:04+00:00 | Vulnerability · Source |
| CVE-2025-40062 | suse_vex | SUSE CVE CVE-2025-40062 | first fixed: 2 known affected: 451 known not affected: 211 recommended: 506 | 2026-07-25T00:36:00+00:00 | Vulnerability · Source |
| CVE-2025-40063 | suse_vex | SUSE CVE CVE-2025-40063 | known not affected: 407 recommended: 6 | 2026-07-25T00:35:58+00:00 | Vulnerability · Source |