VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38547 | suse_vex | SUSE CVE CVE-2025-38547 | first fixed: 2 known not affected: 416 recommended: 172 | 2026-07-31T01:08:44+00:00 | Vulnerability · Source |
| CVE-2025-38554 | suse_vex | SUSE CVE CVE-2025-38554 | first fixed: 2 known not affected: 448 recommended: 158 | 2026-07-31T01:08:40+00:00 | Vulnerability · Source |
| CVE-2025-38561 | suse_vex | SUSE CVE CVE-2025-38561 | known not affected: 472 | 2026-07-31T01:08:37+00:00 | Vulnerability · Source |
| CVE-2025-38568 | suse_vex | SUSE CVE CVE-2025-38568 | first fixed: 2 known affected: 394 known not affected: 337 recommended: 591 | 2026-07-31T01:08:34+00:00 | Vulnerability · Source |
| CVE-2025-38570 | suse_vex | SUSE CVE CVE-2025-38570 | known not affected: 416 | 2026-07-31T01:08:31+00:00 | Vulnerability · Source |
| CVE-2025-38575 | suse_vex | SUSE CVE CVE-2025-38575 | known not affected: 455 | 2026-07-31T01:08:26+00:00 | Vulnerability · Source |
| CVE-2025-38577 | suse_vex | SUSE CVE CVE-2025-38577 | known not affected: 470 | 2026-07-31T01:08:24+00:00 | Vulnerability · Source |
| CVE-2025-38578 | suse_vex | SUSE CVE CVE-2025-38578 | known not affected: 470 | 2026-07-31T01:08:21+00:00 | Vulnerability · Source |
| CVE-2025-38579 | suse_vex | SUSE CVE CVE-2025-38579 | known not affected: 470 | 2026-07-31T01:08:19+00:00 | Vulnerability · Source |
| CVE-2025-38586 | suse_vex | SUSE CVE CVE-2025-38586 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:08:14+00:00 | Vulnerability · Source |
| CVE-2025-38592 | suse_vex | SUSE CVE CVE-2025-38592 | known not affected: 416 | 2026-07-31T01:08:11+00:00 | Vulnerability · Source |
| CVE-2025-38594 | suse_vex | SUSE CVE CVE-2025-38594 | known not affected: 416 | 2026-07-31T01:08:08+00:00 | Vulnerability · Source |
| CVE-2025-38596 | suse_vex | SUSE CVE CVE-2025-38596 | known not affected: 346 | 2026-07-31T01:08:07+00:00 | Vulnerability · Source |
| CVE-2025-38607 | suse_vex | SUSE CVE CVE-2025-38607 | known not affected: 416 | 2026-07-31T01:08:01+00:00 | Vulnerability · Source |
| CVE-2025-38619 | suse_vex | SUSE CVE CVE-2025-38619 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-31T01:07:55+00:00 | Vulnerability · Source |
| CVE-2025-38626 | suse_vex | SUSE CVE CVE-2025-38626 | known not affected: 470 | 2026-07-31T01:07:52+00:00 | Vulnerability · Source |
| CVE-2025-38627 | suse_vex | SUSE CVE CVE-2025-38627 | known not affected: 425 | 2026-07-31T01:07:49+00:00 | Vulnerability · Source |
| CVE-2025-38652 | suse_vex | SUSE CVE CVE-2025-38652 | known affected: 394 known not affected: 425 recommended: 4 | 2026-07-31T01:07:44+00:00 | Vulnerability · Source |
| CVE-2025-38657 | suse_vex | SUSE CVE CVE-2025-38657 | known not affected: 416 | 2026-07-31T01:07:41+00:00 | Vulnerability · Source |
| CVE-2025-38661 | suse_vex | SUSE CVE CVE-2025-38661 | known not affected: 417 | 2026-07-31T01:07:37+00:00 | Vulnerability · Source |
| CVE-2025-38666 | suse_vex | SUSE CVE CVE-2025-38666 | known not affected: 470 | 2026-07-31T01:07:34+00:00 | Vulnerability · Source |
| CVE-2025-38703 | suse_vex | SUSE CVE CVE-2025-38703 | first fixed: 2 known affected: 399 known not affected: 376 recommended: 350 | 2026-07-31T01:07:25+00:00 | Vulnerability · Source |
| CVE-2025-38707 | suse_vex | SUSE CVE CVE-2025-38707 | known not affected: 416 | 2026-07-31T01:07:22+00:00 | Vulnerability · Source |
| CVE-2025-38717 | suse_vex | SUSE CVE CVE-2025-38717 | first fixed: 2 known affected: 379 known not affected: 22 recommended: 154 | 2026-07-31T01:07:17+00:00 | Vulnerability · Source |
| CVE-2025-38724 | suse_vex | SUSE CVE CVE-2025-38724 | first fixed: 2 known affected: 624 known not affected: 11 recommended: 640 | 2026-07-31T01:07:13+00:00 | Vulnerability · Source |
| CVE-2025-38730 | suse_vex | SUSE CVE CVE-2025-38730 | first fixed: 2 known affected: 451 known not affected: 205 recommended: 591 | 2026-07-31T01:07:10+00:00 | Vulnerability · Source |
| CVE-2025-38731 | suse_vex | SUSE CVE CVE-2025-38731 | known not affected: 416 recommended: 83 | 2026-07-31T01:07:07+00:00 | Vulnerability · Source |
| CVE-2025-38737 | suse_vex | SUSE CVE CVE-2025-38737 | known affected: 20 known not affected: 433 recommended: 42 | 2026-07-31T01:07:03+00:00 | Vulnerability · Source |
| CVE-2025-39680 | suse_vex | SUSE CVE CVE-2025-39680 | known affected: 57 known not affected: 359 | 2026-07-31T01:06:58+00:00 | Vulnerability · Source |
| CVE-2025-39688 | suse_vex | SUSE CVE CVE-2025-39688 | known not affected: 348 recommended: 53 | 2026-07-31T01:06:52+00:00 | Vulnerability · Source |
| CVE-2025-39697 | suse_vex | SUSE CVE CVE-2025-39697 | first fixed: 2 known affected: 557 known not affected: 102 recommended: 604 | 2026-07-31T01:06:47+00:00 | Vulnerability · Source |
| CVE-2025-39698 | suse_vex | SUSE CVE CVE-2025-39698 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 201 | 2026-07-31T01:06:45+00:00 | Vulnerability · Source |
| CVE-2025-39718 | suse_vex | SUSE CVE CVE-2025-39718 | first fixed: 2 known affected: 451 known not affected: 205 recommended: 614 | 2026-07-31T01:06:38+00:00 | Vulnerability · Source |
| CVE-2025-39735 | suse_vex | SUSE CVE CVE-2025-39735 | known affected: 376 known not affected: 320 recommended: 29 | 2026-07-31T01:06:33+00:00 | Vulnerability · Source |
| CVE-2025-39779 | suse_vex | SUSE CVE CVE-2025-39779 | first fixed: 2 known affected: 506 known not affected: 156 recommended: 154 | 2026-07-31T01:06:23+00:00 | Vulnerability · Source |
| CVE-2025-39791 | suse_vex | SUSE CVE CVE-2025-39791 | first fixed: 2 known affected: 5 known not affected: 435 recommended: 154 | 2026-07-31T01:06:17+00:00 | Vulnerability · Source |
| CVE-2025-39802 | suse_vex | SUSE CVE CVE-2025-39802 | known not affected: 416 | 2026-07-31T01:06:12+00:00 | Vulnerability · Source |
| CVE-2025-39804 | suse_vex | SUSE CVE CVE-2025-39804 | known not affected: 416 | 2026-07-31T01:06:10+00:00 | Vulnerability · Source |
| CVE-2025-39806 | suse_vex | SUSE CVE CVE-2025-39806 | first fixed: 2 known affected: 456 known not affected: 211 recommended: 583 | 2026-07-31T01:06:07+00:00 | Vulnerability · Source |
| CVE-2025-39815 | suse_vex | SUSE CVE CVE-2025-39815 | known affected: 2 known not affected: 414 | 2026-07-31T01:06:02+00:00 | Vulnerability · Source |
| CVE-2025-39818 | suse_vex | SUSE CVE CVE-2025-39818 | known not affected: 416 recommended: 110 | 2026-07-31T01:05:59+00:00 | Vulnerability · Source |
| CVE-2025-39837 | suse_vex | SUSE CVE CVE-2025-39837 | known not affected: 416 | 2026-07-31T01:05:51+00:00 | Vulnerability · Source |
| CVE-2025-39840 | suse_vex | SUSE CVE CVE-2025-39840 | known not affected: 416 recommended: 83 | 2026-07-31T01:05:48+00:00 | Vulnerability · Source |
| CVE-2025-39849 | suse_vex | SUSE CVE CVE-2025-39849 | first fixed: 2 known affected: 454 known not affected: 211 recommended: 606 | 2026-07-31T01:05:45+00:00 | Vulnerability · Source |
| CVE-2025-39862 | suse_vex | SUSE CVE CVE-2025-39862 | known not affected: 205 | 2026-07-31T01:05:41+00:00 | Vulnerability · Source |
| CVE-2025-39868 | suse_vex | SUSE CVE CVE-2025-39868 | known not affected: 416 | 2026-07-31T01:05:37+00:00 | Vulnerability · Source |
| CVE-2025-39872 | suse_vex | SUSE CVE CVE-2025-39872 | known not affected: 416 | 2026-07-31T01:05:34+00:00 | Vulnerability · Source |
| CVE-2025-39908 | suse_vex | SUSE CVE CVE-2025-39908 | known not affected: 416 | 2026-07-31T01:05:23+00:00 | Vulnerability · Source |
| CVE-2025-39918 | suse_vex | SUSE CVE CVE-2025-39918 | first fixed: 2 known not affected: 410 recommended: 237 | 2026-07-31T01:05:21+00:00 | Vulnerability · Source |
| CVE-2025-39928 | suse_vex | SUSE CVE CVE-2025-39928 | known not affected: 416 | 2026-07-31T01:05:17+00:00 | Vulnerability · Source |