VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-35939 | suse_vex | SUSE CVE CVE-2024-35939 | known affected: 315 known not affected: 244 recommended: 693 | 2026-07-26T00:05:05+00:00 | Vulnerability · Source |
| CVE-2024-36007 | suse_vex | SUSE CVE CVE-2024-36007 | known affected: 342 known not affected: 111 recommended: 691 | 2026-07-26T00:05:02+00:00 | Vulnerability · Source |
| CVE-2024-36462 | suse_vex | SUSE CVE CVE-2024-36462 | known not affected: 11 | 2026-07-26T00:05:00+00:00 | Vulnerability · Source |
| CVE-2024-37370 | suse_vex | SUSE CVE CVE-2024-37370 | known affected: 331 recommended: 489 | 2026-07-26T00:04:57+00:00 | Vulnerability · Source |
| CVE-2024-37371 | suse_vex | SUSE CVE CVE-2024-37371 | known affected: 331 recommended: 507 | 2026-07-26T00:04:55+00:00 | Vulnerability · Source |
| CVE-2024-38394 | suse_vex | SUSE CVE CVE-2024-38394 | known not affected: 57 recommended: 74 | 2026-07-26T00:04:52+00:00 | Vulnerability · Source |
| CVE-2024-38603 | suse_vex | SUSE CVE CVE-2024-38603 | known affected: 357 known not affected: 231 recommended: 656 | 2026-07-26T00:04:49+00:00 | Vulnerability · Source |
| CVE-2024-40898 | suse_vex | SUSE CVE CVE-2024-40898 | known not affected: 214 recommended: 37 | 2026-07-26T00:04:46+00:00 | Vulnerability · Source |
| CVE-2024-41000 | suse_vex | SUSE CVE CVE-2024-41000 | known affected: 340 known not affected: 231 recommended: 660 | 2026-07-26T00:04:42+00:00 | Vulnerability · Source |
| CVE-2024-42082 | suse_vex | SUSE CVE CVE-2024-42082 | known affected: 488 known not affected: 46 recommended: 747 | 2026-07-26T00:04:38+00:00 | Vulnerability · Source |
| CVE-2024-42255 | suse_vex | SUSE CVE CVE-2024-42255 | known not affected: 310 | 2026-07-26T00:04:35+00:00 | Vulnerability · Source |
| CVE-2024-43873 | suse_vex | SUSE CVE CVE-2024-43873 | known affected: 401 known not affected: 157 recommended: 691 | 2026-07-26T00:04:31+00:00 | Vulnerability · Source |
| CVE-2024-45491 | suse_vex | SUSE CVE CVE-2024-45491 | known affected: 489 known not affected: 7 recommended: 306 | 2026-07-26T00:04:28+00:00 | Vulnerability · Source |
| CVE-2024-46683 | suse_vex | SUSE CVE CVE-2024-46683 | known not affected: 324 recommended: 59 | 2026-07-26T00:04:25+00:00 | Vulnerability · Source |
| CVE-2024-46797 | suse_vex | SUSE CVE CVE-2024-46797 | known affected: 394 known not affected: 269 recommended: 377 | 2026-07-26T00:04:22+00:00 | Vulnerability · Source |
| CVE-2024-47539 | suse_vex | SUSE CVE CVE-2024-47539 | known affected: 27 known not affected: 16 recommended: 101 | 2026-07-26T00:04:17+00:00 | Vulnerability · Source |
| CVE-2024-47708 | suse_vex | SUSE CVE CVE-2024-47708 | known not affected: 402 recommended: 6 | 2026-07-26T00:04:14+00:00 | Vulnerability · Source |
| CVE-2024-47724 | suse_vex | SUSE CVE CVE-2024-47724 | known not affected: 402 recommended: 65 | 2026-07-26T00:04:12+00:00 | Vulnerability · Source |
| CVE-2024-47834 | suse_vex | SUSE CVE CVE-2024-47834 | known affected: 34 known not affected: 1 recommended: 99 | 2026-07-26T00:04:10+00:00 | Vulnerability · Source |
| CVE-2024-50303 | suse_vex | SUSE CVE CVE-2024-50303 | known not affected: 372 | 2026-07-26T00:04:04+00:00 | Vulnerability · Source |
| CVE-2024-52290 | suse_vex | SUSE CVE CVE-2024-52290 | recommended: 3 | 2026-07-26T00:04:02+00:00 | Vulnerability · Source |
| CVE-2024-52615 | suse_vex | SUSE CVE CVE-2024-52615 | known affected: 835 recommended: 502 | 2026-07-26T00:04:00+00:00 | Vulnerability · Source |
| CVE-2024-53065 | suse_vex | SUSE CVE CVE-2024-53065 | known not affected: 372 | 2026-07-26T00:03:57+00:00 | Vulnerability · Source |
| CVE-2024-57886 | suse_vex | SUSE CVE CVE-2024-57886 | known not affected: 346 | 2026-07-26T00:03:49+00:00 | Vulnerability · Source |
| CVE-2025-4330 | suse_vex | SUSE CVE CVE-2025-4330 | known affected: 394 known not affected: 145 recommended: 930 | 2026-07-26T00:03:43+00:00 | Vulnerability · Source |
| CVE-2025-6021 | suse_vex | SUSE CVE CVE-2025-6021 | known affected: 422 known not affected: 377 recommended: 285 | 2026-07-26T00:03:40+00:00 | Vulnerability · Source |
| CVE-2025-8058 | suse_vex | SUSE CVE CVE-2025-8058 | known affected: 578 recommended: 943 | 2026-07-26T00:03:36+00:00 | Vulnerability · Source |
| CVE-2025-8941 | suse_vex | SUSE CVE CVE-2025-8941 | known not affected: 285 recommended: 7 | 2026-07-26T00:03:34+00:00 | Vulnerability · Source |
| CVE-2025-13601 | suse_vex | SUSE CVE CVE-2025-13601 | known affected: 550 recommended: 567 | 2026-07-26T00:03:31+00:00 | Vulnerability · Source |
| CVE-2025-15282 | suse_vex | SUSE CVE CVE-2025-15282 | known affected: 382 known not affected: 75 recommended: 799 | 2026-07-26T00:03:28+00:00 | Vulnerability · Source |
| CVE-2025-20054 | suse_vex | SUSE CVE CVE-2025-20054 | known affected: 10 recommended: 43 | 2026-07-26T00:03:26+00:00 | Vulnerability · Source |
| CVE-2025-21800 | suse_vex | SUSE CVE CVE-2025-21800 | known not affected: 354 recommended: 145 | 2026-07-26T00:03:23+00:00 | Vulnerability · Source |
| CVE-2025-22078 | suse_vex | SUSE CVE CVE-2025-22078 | known not affected: 344 recommended: 53 | 2026-07-26T00:03:20+00:00 | Vulnerability · Source |
| CVE-2025-22839 | suse_vex | SUSE CVE CVE-2025-22839 | known affected: 14 recommended: 43 | 2026-07-26T00:03:18+00:00 | Vulnerability · Source |
| CVE-2025-23050 | suse_vex | SUSE CVE CVE-2025-23050 | known affected: 262 recommended: 49 | 2026-07-26T00:03:17+00:00 | Vulnerability · Source |
| CVE-2025-27831 | suse_vex | SUSE CVE CVE-2025-27831 | known not affected: 29 recommended: 104 | 2026-07-26T00:03:14+00:00 | Vulnerability · Source |
| CVE-2025-32049 | suse_vex | SUSE CVE CVE-2025-32049 | known affected: 126 recommended: 231 | 2026-07-26T00:03:12+00:00 | Vulnerability · Source |
| CVE-2025-32913 | suse_vex | SUSE CVE CVE-2025-32913 | known affected: 55 known not affected: 6 recommended: 246 | 2026-07-26T00:03:11+00:00 | Vulnerability · Source |
| CVE-2025-38233 | suse_vex | SUSE CVE CVE-2025-38233 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-26T00:03:05+00:00 | Vulnerability · Source |
| CVE-2025-38421 | suse_vex | SUSE CVE CVE-2025-38421 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-26T00:03:02+00:00 | Vulnerability · Source |
| CVE-2025-38558 | suse_vex | SUSE CVE CVE-2025-38558 | known not affected: 416 | 2026-07-26T00:02:59+00:00 | Vulnerability · Source |
| CVE-2025-38589 | suse_vex | SUSE CVE CVE-2025-38589 | first fixed: 2 known not affected: 431 recommended: 172 | 2026-07-26T00:02:58+00:00 | Vulnerability · Source |
| CVE-2025-39909 | suse_vex | SUSE CVE CVE-2025-39909 | first fixed: 2 known not affected: 410 recommended: 154 | 2026-07-26T00:02:53+00:00 | Vulnerability · Source |
| CVE-2025-40126 | suse_vex | SUSE CVE CVE-2025-40126 | known not affected: 437 | 2026-07-26T00:02:49+00:00 | Vulnerability · Source |
| CVE-2025-43529 | suse_vex | SUSE CVE CVE-2025-43529 | known affected: 133 recommended: 624 | 2026-07-26T00:02:46+00:00 | Vulnerability · Source |
| CVE-2025-68216 | suse_vex | SUSE CVE CVE-2025-68216 | known not affected: 418 | 2026-07-26T00:02:41+00:00 | Vulnerability · Source |
| CVE-2025-68338 | suse_vex | SUSE CVE CVE-2025-68338 | known not affected: 453 | 2026-07-26T00:02:39+00:00 | Vulnerability · Source |
| CVE-2026-15370 | suse_vex | SUSE CVE CVE-2026-15370 | first fixed: 8 known affected: 20 known not affected: 136 | 2026-07-26T00:02:30+00:00 | Vulnerability · Source |
| CVE-2026-59849 | suse_vex | SUSE CVE CVE-2026-59849 | first fixed: 8 known affected: 20 known not affected: 136 | 2026-07-26T00:02:00+00:00 | Vulnerability · Source |
| CVE-2026-63934 | suse_vex | SUSE CVE CVE-2026-63934 | No product status | 2026-07-26T00:01:57+00:00 | Vulnerability · Source |