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-39793 | suse_vex | SUSE CVE CVE-2025-39793 | known not affected: 416 | 2026-07-25T00:40:13+00:00 | Vulnerability · Source |
| CVE-2025-39798 | suse_vex | SUSE CVE CVE-2025-39798 | first fixed: 2 known affected: 654 known not affected: 3 recommended: 500 | 2026-07-25T00:40:07+00:00 | Vulnerability · Source |
| CVE-2025-39801 | suse_vex | SUSE CVE CVE-2025-39801 | first fixed: 2 known affected: 620 known not affected: 39 recommended: 500 | 2026-07-25T00:40:04+00:00 | Vulnerability · Source |
| CVE-2025-39810 | suse_vex | SUSE CVE CVE-2025-39810 | first fixed: 2 known affected: 568 known not affected: 99 recommended: 500 | 2026-07-25T00:40:00+00:00 | Vulnerability · Source |
| CVE-2025-39821 | suse_vex | SUSE CVE CVE-2025-39821 | known not affected: 416 recommended: 27 | 2026-07-25T00:39:56+00:00 | Vulnerability · Source |
| CVE-2025-39831 | suse_vex | SUSE CVE CVE-2025-39831 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:39:51+00:00 | Vulnerability · Source |
| CVE-2025-39832 | suse_vex | SUSE CVE CVE-2025-39832 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:39:49+00:00 | Vulnerability · Source |
| CVE-2025-39838 | suse_vex | SUSE CVE CVE-2025-39838 | first fixed: 2 known affected: 509 known not affected: 124 recommended: 537 | 2026-07-25T00:39:46+00:00 | Vulnerability · Source |
| CVE-2025-39839 | suse_vex | SUSE CVE CVE-2025-39839 | first fixed: 2 known affected: 568 known not affected: 97 recommended: 500 | 2026-07-25T00:39:45+00:00 | Vulnerability · Source |
| CVE-2025-39841 | suse_vex | SUSE CVE CVE-2025-39841 | first fixed: 2 known affected: 583 known not affected: 52 recommended: 586 | 2026-07-25T00:39:40+00:00 | Vulnerability · Source |
| CVE-2025-39846 | suse_vex | SUSE CVE CVE-2025-39846 | known affected: 394 known not affected: 271 recommended: 346 | 2026-07-25T00:39:37+00:00 | Vulnerability · Source |
| CVE-2025-39847 | suse_vex | SUSE CVE CVE-2025-39847 | first fixed: 2 known affected: 633 recommended: 537 | 2026-07-25T00:39:34+00:00 | Vulnerability · Source |
| CVE-2025-39850 | suse_vex | SUSE CVE CVE-2025-39850 | first fixed: 2 known affected: 552 known not affected: 113 recommended: 500 | 2026-07-25T00:39:29+00:00 | Vulnerability · Source |
| CVE-2025-39852 | suse_vex | SUSE CVE CVE-2025-39852 | first fixed: 2 known affected: 62 known not affected: 376 recommended: 154 | 2026-07-25T00:39:27+00:00 | Vulnerability · Source |
| CVE-2025-39854 | suse_vex | SUSE CVE CVE-2025-39854 | first fixed: 2 known affected: 394 known not affected: 271 recommended: 500 | 2026-07-25T00:39:24+00:00 | Vulnerability · Source |
| CVE-2025-39857 | suse_vex | SUSE CVE CVE-2025-39857 | first fixed: 2 known affected: 456 known not affected: 213 recommended: 500 | 2026-07-25T00:39:21+00:00 | Vulnerability · Source |
| CVE-2025-39861 | suse_vex | SUSE CVE CVE-2025-39861 | first fixed: 2 known affected: 394 known not affected: 265 recommended: 500 | 2026-07-25T00:39:17+00:00 | Vulnerability · Source |
| CVE-2025-39864 | suse_vex | SUSE CVE CVE-2025-39864 | first fixed: 2 known affected: 552 known not affected: 113 recommended: 561 | 2026-07-25T00:39:14+00:00 | Vulnerability · Source |
| CVE-2025-39865 | suse_vex | SUSE CVE CVE-2025-39865 | first fixed: 2 known affected: 613 known not affected: 22 recommended: 523 | 2026-07-25T00:39:11+00:00 | Vulnerability · Source |
| CVE-2025-39870 | suse_vex | SUSE CVE CVE-2025-39870 | first fixed: 2 known affected: 397 known not affected: 262 recommended: 500 | 2026-07-25T00:39:07+00:00 | Vulnerability · Source |
| CVE-2025-39874 | suse_vex | SUSE CVE CVE-2025-39874 | known not affected: 416 | 2026-07-25T00:39:04+00:00 | Vulnerability · Source |
| CVE-2025-39875 | suse_vex | SUSE CVE CVE-2025-39875 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 154 | 2026-07-25T00:39:01+00:00 | Vulnerability · Source |
| CVE-2025-39878 | suse_vex | SUSE CVE CVE-2025-39878 | known not affected: 416 | 2026-07-25T00:38:58+00:00 | Vulnerability · Source |
| CVE-2025-39879 | suse_vex | SUSE CVE CVE-2025-39879 | known not affected: 416 | 2026-07-25T00:38:55+00:00 | Vulnerability · Source |
| CVE-2025-39880 | suse_vex | SUSE CVE CVE-2025-39880 | first fixed: 2 known affected: 607 known not affected: 156 recommended: 307 | 2026-07-25T00:38:53+00:00 | Vulnerability · Source |
| CVE-2025-39885 | suse_vex | SUSE CVE CVE-2025-39885 | first fixed: 2 known affected: 635 recommended: 537 | 2026-07-25T00:38:49+00:00 | Vulnerability · Source |
| CVE-2025-39890 | suse_vex | SUSE CVE CVE-2025-39890 | first fixed: 2 known affected: 449 known not affected: 288 recommended: 384 | 2026-07-25T00:38:46+00:00 | Vulnerability · Source |
| 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 |