VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284624 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-40990 | suse_vex | SUSE CVE CVE-2024-40990 | known affected: 448 known not affected: 2 recommended: 742 | 2026-07-26T16:45:33+00:00 | Vulnerability · Source |
| CVE-2024-40997 | suse_vex | SUSE CVE CVE-2024-40997 | known affected: 354 known not affected: 238 recommended: 649 | 2026-07-26T16:45:31+00:00 | Vulnerability · Source |
| CVE-2024-41061 | suse_vex | SUSE CVE CVE-2024-41061 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-26T16:45:29+00:00 | Vulnerability · Source |
| CVE-2024-41097 | suse_vex | SUSE CVE CVE-2024-41097 | known affected: 534 known not affected: 12 recommended: 752 | 2026-07-26T16:45:27+00:00 | Vulnerability · Source |
| CVE-2024-41996 | suse_vex | SUSE CVE CVE-2024-41996 | known affected: 394 known not affected: 575 recommended: 147 | 2026-07-26T16:45:25+00:00 | Vulnerability · Source |
| CVE-2024-42117 | suse_vex | SUSE CVE CVE-2024-42117 | known affected: 394 known not affected: 264 recommended: 360 | 2026-07-26T16:45:23+00:00 | Vulnerability · Source |
| CVE-2024-43850 | suse_vex | SUSE CVE CVE-2024-43850 | known affected: 394 known not affected: 280 recommended: 360 | 2026-07-26T16:45:20+00:00 | Vulnerability · Source |
| CVE-2024-44935 | suse_vex | SUSE CVE CVE-2024-44935 | known affected: 474 known not affected: 125 recommended: 657 | 2026-07-26T16:45:16+00:00 | Vulnerability · Source |
| CVE-2024-44938 | suse_vex | SUSE CVE CVE-2024-44938 | known affected: 310 known not affected: 140 recommended: 771 | 2026-07-26T16:45:14+00:00 | Vulnerability · Source |
| CVE-2024-45620 | suse_vex | SUSE CVE CVE-2024-45620 | known affected: 422 recommended: 39 | 2026-07-26T16:45:11+00:00 | Vulnerability · Source |
| CVE-2024-45779 | suse_vex | SUSE CVE CVE-2024-45779 | known affected: 485 recommended: 408 | 2026-07-26T16:45:09+00:00 | Vulnerability · Source |
| CVE-2024-48869 | suse_vex | SUSE CVE CVE-2024-48869 | known affected: 55 | 2026-07-26T16:45:03+00:00 | Vulnerability · Source |
| CVE-2024-50071 | suse_vex | SUSE CVE CVE-2024-50071 | known not affected: 379 recommended: 6 | 2026-07-26T16:44:58+00:00 | Vulnerability · Source |
| CVE-2024-50193 | suse_vex | SUSE CVE CVE-2024-50193 | known not affected: 439 recommended: 6 | 2026-07-26T16:44:55+00:00 | Vulnerability · Source |
| CVE-2024-56706 | suse_vex | SUSE CVE CVE-2024-56706 | known not affected: 425 recommended: 53 | 2026-07-26T16:44:29+00:00 | Vulnerability · Source |
| CVE-2024-56772 | suse_vex | SUSE CVE CVE-2024-56772 | known not affected: 367 recommended: 53 | 2026-07-26T16:44:25+00:00 | Vulnerability · Source |
| CVE-2024-57898 | suse_vex | SUSE CVE CVE-2024-57898 | known not affected: 272 recommended: 155 | 2026-07-26T16:44:20+00:00 | Vulnerability · Source |
| CVE-2024-57985 | suse_vex | SUSE CVE CVE-2024-57985 | known not affected: 352 recommended: 53 | 2026-07-26T16:44:16+00:00 | Vulnerability · Source |
| CVE-2024-57992 | suse_vex | SUSE CVE CVE-2024-57992 | known not affected: 352 | 2026-07-26T16:44:15+00:00 | Vulnerability · Source |
| CVE-2024-58064 | suse_vex | SUSE CVE CVE-2024-58064 | known not affected: 352 recommended: 96 | 2026-07-26T16:44:13+00:00 | Vulnerability · Source |
| CVE-2025-0246 | suse_vex | SUSE CVE CVE-2025-0246 | known affected: 57 recommended: 9 | 2026-07-26T16:44:11+00:00 | Vulnerability · Source |
| CVE-2025-1352 | suse_vex | SUSE CVE CVE-2025-1352 | known affected: 61 known not affected: 259 recommended: 308 | 2026-07-26T16:44:09+00:00 | Vulnerability · Source |
| CVE-2025-1936 | suse_vex | SUSE CVE CVE-2025-1936 | known affected: 37 recommended: 173 | 2026-07-26T16:44:08+00:00 | Vulnerability · Source |
| CVE-2025-1941 | suse_vex | SUSE CVE CVE-2025-1941 | recommended: 9 | 2026-07-26T16:44:06+00:00 | Vulnerability · Source |
| CVE-2025-1943 | suse_vex | SUSE CVE CVE-2025-1943 | recommended: 9 | 2026-07-26T16:44:05+00:00 | Vulnerability · Source |
| CVE-2025-3032 | suse_vex | SUSE CVE CVE-2025-3032 | known affected: 37 recommended: 9 | 2026-07-26T16:44:03+00:00 | Vulnerability · Source |
| CVE-2025-3033 | suse_vex | SUSE CVE CVE-2025-3033 | recommended: 9 | 2026-07-26T16:44:02+00:00 | Vulnerability · Source |
| CVE-2025-3576 | suse_vex | SUSE CVE CVE-2025-3576 | known affected: 600 known not affected: 35 recommended: 198 | 2026-07-26T16:44:00+00:00 | Vulnerability · Source |
| CVE-2025-3608 | suse_vex | SUSE CVE CVE-2025-3608 | known affected: 16 known not affected: 134 recommended: 9 | 2026-07-26T16:43:59+00:00 | Vulnerability · Source |
| CVE-2025-3770 | suse_vex | SUSE CVE CVE-2025-3770 | known affected: 1708 known not affected: 193 | 2026-07-26T16:43:57+00:00 | Vulnerability · Source |
| CVE-2025-4082 | suse_vex | SUSE CVE CVE-2025-4082 | known affected: 69 recommended: 112 | 2026-07-26T16:43:56+00:00 | Vulnerability · Source |
| CVE-2025-4086 | suse_vex | SUSE CVE CVE-2025-4086 | known affected: 69 recommended: 9 | 2026-07-26T16:43:54+00:00 | Vulnerability · Source |
| CVE-2025-4087 | suse_vex | SUSE CVE CVE-2025-4087 | known affected: 69 recommended: 117 | 2026-07-26T16:43:53+00:00 | Vulnerability · Source |
| CVE-2025-4092 | suse_vex | SUSE CVE CVE-2025-4092 | known affected: 69 recommended: 9 | 2026-07-26T16:43:51+00:00 | Vulnerability · Source |
| CVE-2025-4802 | suse_vex | SUSE CVE CVE-2025-4802 | known affected: 339 known not affected: 169 recommended: 957 | 2026-07-26T16:43:50+00:00 | Vulnerability · Source |
| CVE-2025-5271 | suse_vex | SUSE CVE CVE-2025-5271 | known affected: 37 recommended: 9 | 2026-07-26T16:43:48+00:00 | Vulnerability · Source |
| CVE-2025-5278 | suse_vex | SUSE CVE CVE-2025-5278 | known affected: 370 recommended: 173 | 2026-07-26T16:43:47+00:00 | Vulnerability · Source |
| CVE-2025-5745 | suse_vex | SUSE CVE CVE-2025-5745 | known not affected: 516 recommended: 38 | 2026-07-26T16:43:45+00:00 | Vulnerability · Source |
| CVE-2025-5914 | suse_vex | SUSE CVE CVE-2025-5914 | known affected: 453 known not affected: 52 recommended: 97 | 2026-07-26T16:43:44+00:00 | Vulnerability · Source |
| CVE-2025-6020 | suse_vex | SUSE CVE CVE-2025-6020 | known affected: 449 recommended: 224 | 2026-07-26T16:43:42+00:00 | Vulnerability · Source |
| CVE-2025-6075 | suse_vex | SUSE CVE CVE-2025-6075 | known affected: 541 recommended: 947 | 2026-07-26T16:43:40+00:00 | Vulnerability · Source |
| CVE-2025-7345 | suse_vex | SUSE CVE CVE-2025-7345 | known affected: 509 known not affected: 1004 recommended: 349 | 2026-07-26T16:43:38+00:00 | Vulnerability · Source |
| CVE-2025-7425 | suse_vex | SUSE CVE CVE-2025-7425 | known affected: 344 known not affected: 198 recommended: 276 | 2026-07-26T16:43:36+00:00 | Vulnerability · Source |
| CVE-2025-8043 | suse_vex | SUSE CVE CVE-2025-8043 | known affected: 37 recommended: 9 | 2026-07-26T16:43:35+00:00 | Vulnerability · Source |
| CVE-2025-8044 | suse_vex | SUSE CVE CVE-2025-8044 | known affected: 37 recommended: 9 | 2026-07-26T16:43:33+00:00 | Vulnerability · Source |
| CVE-2025-9186 | suse_vex | SUSE CVE CVE-2025-9186 | known affected: 37 recommended: 9 | 2026-07-26T16:43:31+00:00 | Vulnerability · Source |
| CVE-2025-9187 | suse_vex | SUSE CVE CVE-2025-9187 | known affected: 37 recommended: 506 | 2026-07-26T16:43:30+00:00 | Vulnerability · Source |
| CVE-2025-10530 | suse_vex | SUSE CVE CVE-2025-10530 | known affected: 37 recommended: 9 | 2026-07-26T16:43:28+00:00 | Vulnerability · Source |
| CVE-2025-10534 | suse_vex | SUSE CVE CVE-2025-10534 | known affected: 37 recommended: 9 | 2026-07-26T16:43:26+00:00 | Vulnerability · Source |
| CVE-2025-11720 | suse_vex | SUSE CVE CVE-2025-11720 | known affected: 70 recommended: 9 | 2026-07-26T16:43:24+00:00 | Vulnerability · Source |