VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
289306 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49565 | suse_vex | SUSE CVE CVE-2022-49565 | known affected: 364 known not affected: 302 recommended: 127 | 2026-08-01T17:10:38+00:00 | Vulnerability · Source |
| CVE-2022-49582 | suse_vex | SUSE CVE CVE-2022-49582 | known not affected: 352 | 2026-08-01T17:10:37+00:00 | Vulnerability · Source |
| CVE-2022-49605 | suse_vex | SUSE CVE CVE-2022-49605 | known affected: 414 known not affected: 194 recommended: 291 | 2026-08-01T17:10:35+00:00 | Vulnerability · Source |
| CVE-2022-49808 | suse_vex | SUSE CVE CVE-2022-49808 | known affected: 163 known not affected: 239 | 2026-08-01T17:10:29+00:00 | Vulnerability · Source |
| CVE-2022-49996 | suse_vex | SUSE CVE CVE-2022-49996 | known not affected: 401 | 2026-08-01T17:10:26+00:00 | Vulnerability · Source |
| CVE-2022-50077 | suse_vex | SUSE CVE CVE-2022-50077 | known affected: 395 known not affected: 247 recommended: 206 | 2026-08-01T17:10:23+00:00 | Vulnerability · Source |
| CVE-2022-50239 | suse_vex | SUSE CVE CVE-2022-50239 | known affected: 344 known not affected: 304 recommended: 235 | 2026-08-01T17:10:19+00:00 | Vulnerability · Source |
| CVE-2022-50401 | suse_vex | SUSE CVE CVE-2022-50401 | known affected: 344 known not affected: 237 recommended: 296 | 2026-08-01T17:10:17+00:00 | Vulnerability · Source |
| CVE-2022-50461 | suse_vex | SUSE CVE CVE-2022-50461 | known affected: 55 known not affected: 361 | 2026-08-01T17:10:15+00:00 | Vulnerability · Source |
| CVE-2023-5557 | suse_vex | SUSE CVE CVE-2023-5557 | recommended: 67 | 2026-08-01T17:09:59+00:00 | Vulnerability · Source |
| CVE-2023-20584 | suse_vex | SUSE CVE CVE-2023-20584 | known not affected: 325 recommended: 38 | 2026-08-01T17:09:55+00:00 | Vulnerability · Source |
| CVE-2023-26604 | suse_vex | SUSE CVE CVE-2023-26604 | known affected: 395 known not affected: 521 recommended: 245 | 2026-08-01T17:09:52+00:00 | Vulnerability · Source |
| CVE-2023-39176 | suse_vex | SUSE CVE CVE-2023-39176 | known not affected: 518 | 2026-08-01T17:09:44+00:00 | Vulnerability · Source |
| CVE-2023-39179 | suse_vex | SUSE CVE CVE-2023-39179 | known not affected: 518 | 2026-08-01T17:09:43+00:00 | Vulnerability · Source |
| CVE-2023-39180 | suse_vex | SUSE CVE CVE-2023-39180 | known not affected: 518 | 2026-08-01T17:09:41+00:00 | Vulnerability · Source |
| CVE-2023-52829 | suse_vex | SUSE CVE CVE-2023-52829 | known affected: 394 known not affected: 297 recommended: 358 | 2026-08-01T17:09:28+00:00 | Vulnerability · Source |
| CVE-2023-52847 | suse_vex | SUSE CVE CVE-2023-52847 | known affected: 302 known not affected: 138 recommended: 830 | 2026-08-01T17:09:26+00:00 | Vulnerability · Source |
| CVE-2023-52978 | suse_vex | SUSE CVE CVE-2023-52978 | known affected: 55 known not affected: 289 | 2026-08-01T17:09:24+00:00 | Vulnerability · Source |
| CVE-2023-53483 | suse_vex | SUSE CVE CVE-2023-53483 | known affected: 57 known not affected: 359 recommended: 20 | 2026-08-01T17:09:18+00:00 | Vulnerability · Source |
| CVE-2023-54086 | suse_vex | SUSE CVE CVE-2023-54086 | known affected: 112 known not affected: 341 | 2026-08-01T17:09:14+00:00 | Vulnerability · Source |
| CVE-2024-0646 | suse_vex | SUSE CVE CVE-2024-0646 | known not affected: 362 recommended: 255 | 2026-08-01T17:09:09+00:00 | Vulnerability · Source |
| CVE-2024-1975 | suse_vex | SUSE CVE CVE-2024-1975 | known affected: 408 recommended: 497 | 2026-08-01T17:09:07+00:00 | Vulnerability · Source |
| CVE-2024-2199 | suse_vex | SUSE CVE CVE-2024-2199 | known affected: 32 recommended: 138 | 2026-08-01T17:09:05+00:00 | Vulnerability · Source |
| CVE-2024-9391 | suse_vex | SUSE CVE CVE-2024-9391 | known affected: 29 recommended: 9 | 2026-08-01T17:09:00+00:00 | Vulnerability · Source |
| CVE-2024-11697 | suse_vex | SUSE CVE CVE-2024-11697 | known affected: 29 recommended: 235 | 2026-08-01T17:08:58+00:00 | Vulnerability · Source |
| CVE-2024-23672 | suse_vex | SUSE CVE CVE-2024-23672 | known affected: 523 known not affected: 3 recommended: 756 | 2026-08-01T17:08:52+00:00 | Vulnerability · Source |
| CVE-2024-26929 | suse_vex | SUSE CVE CVE-2024-26929 | known affected: 269 known not affected: 256 recommended: 972 | 2026-08-01T17:08:44+00:00 | Vulnerability · Source |
| CVE-2024-36912 | suse_vex | SUSE CVE CVE-2024-36912 | known affected: 391 known not affected: 181 recommended: 656 | 2026-08-01T17:08:35+00:00 | Vulnerability · Source |
| CVE-2024-38583 | suse_vex | SUSE CVE CVE-2024-38583 | known affected: 330 known not affected: 114 recommended: 656 | 2026-08-01T17:08:32+00:00 | Vulnerability · Source |
| CVE-2026-43195 | redhat_vex | kernel: drm/amdgpu: validate user queue size constraints | known affected: 274 | 2026-08-01T17:08:30+00:00 | Vulnerability · Source |
| CVE-2024-43910 | suse_vex | SUSE CVE CVE-2024-43910 | known not affected: 325 recommended: 43 | 2026-08-01T17:08:23+00:00 | Vulnerability · Source |
| CVE-2024-49569 | suse_vex | SUSE CVE CVE-2024-49569 | known affected: 512 known not affected: 172 recommended: 406 | 2026-08-01T17:08:17+00:00 | Vulnerability · Source |
| CVE-2024-49994 | suse_vex | SUSE CVE CVE-2024-49994 | known affected: 682 known not affected: 2 recommended: 417 | 2026-08-01T17:08:12+00:00 | Vulnerability · Source |
| CVE-2024-50067 | suse_vex | SUSE CVE CVE-2024-50067 | known affected: 602 known not affected: 42 recommended: 668 | 2026-08-01T17:08:09+00:00 | Vulnerability · Source |
| CVE-2024-50217 | suse_vex | SUSE CVE CVE-2024-50217 | known not affected: 511 recommended: 6 | 2026-08-01T17:08:06+00:00 | Vulnerability · Source |
| CVE-2024-52006 | suse_vex | SUSE CVE CVE-2024-52006 | known affected: 104 known not affected: 105 recommended: 421 | 2026-08-01T17:08:03+00:00 | Vulnerability · Source |
| CVE-2024-53180 | suse_vex | SUSE CVE CVE-2024-53180 | known affected: 590 known not affected: 181 recommended: 363 | 2026-08-01T17:07:59+00:00 | Vulnerability · Source |
| CVE-2025-5372 | suse_vex | SUSE CVE CVE-2025-5372 | known affected: 380 known not affected: 6 recommended: 202 | 2026-08-01T17:07:39+00:00 | Vulnerability · Source |
| CVE-2025-8277 | suse_vex | SUSE CVE CVE-2025-8277 | known affected: 482 recommended: 128 | 2026-08-01T17:07:36+00:00 | Vulnerability · Source |
| CVE-2025-13324 | suse_vex | SUSE CVE CVE-2025-13324 | No product status | 2026-08-01T17:07:22+00:00 | Vulnerability · Source |
| CVE-2025-14986 | suse_vex | SUSE CVE CVE-2025-14986 | No product status | 2026-08-01T17:07:18+00:00 | Vulnerability · Source |
| CVE-2025-14987 | suse_vex | SUSE CVE CVE-2025-14987 | No product status | 2026-08-01T17:07:17+00:00 | Vulnerability · Source |
| CVE-2025-21840 | suse_vex | SUSE CVE CVE-2025-21840 | known affected: 57 known not affected: 295 | 2026-08-01T17:07:11+00:00 | Vulnerability · Source |
| CVE-2025-22037 | suse_vex | SUSE CVE CVE-2025-22037 | known not affected: 453 | 2026-08-01T17:07:07+00:00 | Vulnerability · Source |
| CVE-2025-37924 | suse_vex | SUSE CVE CVE-2025-37924 | known not affected: 451 | 2026-08-01T17:07:00+00:00 | Vulnerability · Source |
| CVE-2025-37976 | suse_vex | SUSE CVE CVE-2025-37976 | known affected: 47 known not affected: 328 | 2026-08-01T17:06:58+00:00 | Vulnerability · Source |
| CVE-2025-38562 | suse_vex | SUSE CVE CVE-2025-38562 | known not affected: 472 | 2026-08-01T17:06:48+00:00 | Vulnerability · Source |
| CVE-2025-40154 | suse_vex | SUSE CVE CVE-2025-40154 | first fixed: 2 known affected: 366 known not affected: 99 recommended: 874 | 2026-08-01T17:06:35+00:00 | Vulnerability · Source |
| CVE-2025-47183 | suse_vex | SUSE CVE CVE-2025-47183 | known affected: 54 recommended: 53 | 2026-08-01T17:06:29+00:00 | Vulnerability · Source |
| CVE-2025-59342 | suse_vex | SUSE CVE CVE-2025-59342 | recommended: 1 | 2026-08-01T17:06:17+00:00 | Vulnerability · Source |