VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-46941 | suse_vex | SUSE CVE CVE-2021-46941 | known affected: 516 known not affected: 210 recommended: 70 | 2026-08-01T17:12:57+00:00 | Vulnerability · Source |
| CVE-2021-47064 | suse_vex | SUSE CVE CVE-2021-47064 | known not affected: 292 | 2026-08-01T17:12:55+00:00 | Vulnerability · Source |
| CVE-2021-47538 | suse_vex | SUSE CVE CVE-2021-47538 | known affected: 324 known not affected: 181 recommended: 433 | 2026-08-01T17:12:42+00:00 | Vulnerability · Source |
| CVE-2022-0204 | suse_vex | SUSE CVE CVE-2022-0204 | known not affected: 51 recommended: 257 | 2026-08-01T17:12:30+00:00 | Vulnerability · Source |
| CVE-2022-0400 | suse_vex | SUSE CVE CVE-2022-0400 | known not affected: 643 | 2026-08-01T17:12:28+00:00 | Vulnerability · Source |
| CVE-2022-1183 | suse_vex | SUSE CVE CVE-2022-1183 | known not affected: 579 recommended: 25 | 2026-08-01T17:12:22+00:00 | Vulnerability · Source |
| CVE-2022-3515 | suse_vex | SUSE CVE CVE-2022-3515 | known affected: 253 known not affected: 1 recommended: 290 | 2026-08-01T17:12:11+00:00 | Vulnerability · Source |
| CVE-2022-3522 | suse_vex | SUSE CVE CVE-2022-3522 | recommended: 47 | 2026-08-01T17:12:10+00:00 | Vulnerability · Source |
| CVE-2022-22815 | suse_vex | SUSE CVE CVE-2022-22815 | known not affected: 48 recommended: 111 | 2026-08-01T17:11:52+00:00 | Vulnerability · Source |
| CVE-2022-28735 | suse_vex | SUSE CVE CVE-2022-28735 | known affected: 356 known not affected: 228 recommended: 499 | 2026-08-01T17:11:40+00:00 | Vulnerability · Source |
| CVE-2022-29885 | suse_vex | SUSE CVE CVE-2022-29885 | known not affected: 101 | 2026-08-01T17:11:36+00:00 | Vulnerability · Source |
| CVE-2022-34475 | suse_vex | SUSE CVE CVE-2022-34475 | known affected: 1 recommended: 365 | 2026-08-01T17:11:33+00:00 | Vulnerability · Source |
| CVE-2022-37434 | suse_vex | SUSE CVE CVE-2022-37434 | known affected: 237 known not affected: 4168 recommended: 1508 | 2026-08-01T17:11:29+00:00 | Vulnerability · Source |
| CVE-2022-39028 | suse_vex | SUSE CVE CVE-2022-39028 | known affected: 394 known not affected: 384 recommended: 166 | 2026-08-01T17:11:27+00:00 | Vulnerability · Source |
| CVE-2022-42312 | suse_vex | SUSE CVE CVE-2022-42312 | recommended: 377 | 2026-08-01T17:11:21+00:00 | Vulnerability · Source |
| CVE-2022-47024 | suse_vex | SUSE CVE CVE-2022-47024 | known not affected: 200 recommended: 5 | 2026-08-01T17:11:16+00:00 | Vulnerability · Source |
| CVE-2022-48468 | suse_vex | SUSE CVE CVE-2022-48468 | known affected: 15 recommended: 102 | 2026-08-01T17:11:14+00:00 | Vulnerability · Source |
| CVE-2022-48986 | suse_vex | SUSE CVE CVE-2022-48986 | known not affected: 462 | 2026-08-01T17:11:03+00:00 | Vulnerability · Source |
| CVE-2022-49008 | suse_vex | SUSE CVE CVE-2022-49008 | known not affected: 379 | 2026-08-01T17:11:01+00:00 | Vulnerability · Source |
| CVE-2022-49419 | suse_vex | SUSE CVE CVE-2022-49419 | known affected: 364 known not affected: 302 recommended: 100 | 2026-08-01T17:10:43+00:00 | Vulnerability · Source |
| CVE-2022-49516 | suse_vex | SUSE CVE CVE-2022-49516 | known affected: 456 known not affected: 180 recommended: 126 | 2026-08-01T17:10:40+00:00 | Vulnerability · Source |
| 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-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-1975 | suse_vex | SUSE CVE CVE-2024-1975 | known affected: 408 recommended: 497 | 2026-08-01T17:09:07+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-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-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-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 |