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-2022-49020 | suse_vex | SUSE CVE CVE-2022-49020 | known affected: 579 known not affected: 55 recommended: 311 | 2026-08-02T16:50:00+00:00 | Vulnerability · Source |
| CVE-2022-49970 | suse_vex | SUSE CVE CVE-2022-49970 | known not affected: 401 recommended: 27 | 2026-08-02T16:49:47+00:00 | Vulnerability · Source |
| CVE-2022-50119 | suse_vex | SUSE CVE CVE-2022-50119 | known not affected: 401 | 2026-08-02T16:49:44+00:00 | Vulnerability · Source |
| CVE-2022-50723 | suse_vex | SUSE CVE CVE-2022-50723 | known affected: 374 known not affected: 396 recommended: 134 | 2026-08-02T16:49:38+00:00 | Vulnerability · Source |
| CVE-2023-28879 | suse_vex | SUSE CVE CVE-2023-28879 | known affected: 16 known not affected: 374 recommended: 206 | 2026-08-02T16:49:12+00:00 | Vulnerability · Source |
| CVE-2023-40267 | suse_vex | SUSE CVE CVE-2023-40267 | known not affected: 3 recommended: 12 | 2026-08-02T16:49:05+00:00 | Vulnerability · Source |
| CVE-2023-40476 | suse_vex | SUSE CVE CVE-2023-40476 | known affected: 312 recommended: 1483 | 2026-08-02T16:49:02+00:00 | Vulnerability · Source |
| CVE-2023-51780 | suse_vex | SUSE CVE CVE-2023-51780 | known affected: 333 recommended: 1380 | 2026-08-02T16:48:54+00:00 | Vulnerability · Source |
| CVE-2023-53022 | suse_vex | SUSE CVE CVE-2023-53022 | known affected: 55 known not affected: 289 | 2026-08-02T16:48:48+00:00 | Vulnerability · Source |
| CVE-2024-35946 | suse_vex | SUSE CVE CVE-2024-35946 | known affected: 394 known not affected: 270 recommended: 382 | 2026-08-02T16:48:16+00:00 | Vulnerability · Source |
| CVE-2024-40647 | suse_vex | SUSE CVE CVE-2024-40647 | recommended: 9 | 2026-08-02T16:48:11+00:00 | Vulnerability · Source |
| CVE-2024-49865 | suse_vex | SUSE CVE CVE-2024-49865 | known not affected: 379 recommended: 65 | 2026-08-02T16:47:58+00:00 | Vulnerability · Source |
| CVE-2024-56597 | suse_vex | SUSE CVE CVE-2024-56597 | known affected: 595 known not affected: 213 recommended: 411 | 2026-08-02T16:47:47+00:00 | Vulnerability · Source |
| CVE-2024-56627 | suse_vex | SUSE CVE CVE-2024-56627 | known not affected: 534 | 2026-08-02T16:47:45+00:00 | Vulnerability · Source |
| CVE-2025-11563 | suse_vex | SUSE CVE CVE-2025-11563 | known affected: 441 known not affected: 41 recommended: 137 | 2026-08-02T16:47:29+00:00 | Vulnerability · Source |
| CVE-2025-22039 | suse_vex | SUSE CVE CVE-2025-22039 | known not affected: 453 | 2026-08-02T16:47:22+00:00 | Vulnerability · Source |
| CVE-2025-22040 | suse_vex | SUSE CVE CVE-2025-22040 | known not affected: 453 | 2026-08-02T16:47:21+00:00 | Vulnerability · Source |
| CVE-2025-22041 | suse_vex | SUSE CVE CVE-2025-22041 | known not affected: 453 | 2026-08-02T16:47:19+00:00 | Vulnerability · Source |
| CVE-2025-49178 | suse_vex | SUSE CVE CVE-2025-49178 | known affected: 420 known not affected: 1 recommended: 184 | 2026-08-02T16:46:55+00:00 | Vulnerability · Source |
| CVE-2026-3184 | suse_vex | SUSE CVE CVE-2026-3184 | known affected: 715 recommended: 416 | 2026-08-02T16:46:43+00:00 | Vulnerability · Source |
| CVE-2026-5745 | suse_vex | SUSE CVE CVE-2026-5745 | known affected: 154 known not affected: 7 | 2026-08-02T16:46:39+00:00 | Vulnerability · Source |
| CVE-2026-23427 | suse_vex | SUSE CVE CVE-2026-23427 | known not affected: 338 | 2026-08-02T16:38:02+00:00 | Vulnerability · Source |
| CVE-2026-23428 | suse_vex | SUSE CVE CVE-2026-23428 | known not affected: 338 | 2026-08-02T16:38:00+00:00 | Vulnerability · Source |
| CVE-2026-31409 | suse_vex | SUSE CVE CVE-2026-31409 | known not affected: 338 | 2026-08-02T16:37:54+00:00 | Vulnerability · Source |
| CVE-2026-31410 | suse_vex | SUSE CVE CVE-2026-31410 | known not affected: 338 | 2026-08-02T16:37:52+00:00 | Vulnerability · Source |
| CVE-2026-31716 | suse_vex | SUSE CVE CVE-2026-31716 | known not affected: 293 recommended: 4 | 2026-08-02T16:37:49+00:00 | Vulnerability · Source |
| CVE-2026-40186 | suse_vex | SUSE CVE CVE-2026-40186 | known not affected: 313 | 2026-08-02T16:37:45+00:00 | Vulnerability · Source |
| CVE-2026-43185 | suse_vex | SUSE CVE CVE-2026-43185 | known not affected: 310 | 2026-08-02T16:37:41+00:00 | Vulnerability · Source |
| CVE-2026-43330 | suse_vex | SUSE CVE CVE-2026-43330 | known affected: 394 known not affected: 196 recommended: 196 | 2026-08-02T16:37:39+00:00 | Vulnerability · Source |
| CVE-2026-47035 | suse_vex | SUSE CVE CVE-2026-47035 | known not affected: 510 recommended: 2 | 2026-08-02T16:37:30+00:00 | Vulnerability · Source |
| CVE-2026-53383 | suse_vex | SUSE CVE CVE-2026-53383 | known not affected: 298 recommended: 4 | 2026-08-02T16:37:23+00:00 | Vulnerability · Source |
| CVE-2026-55971 | suse_vex | SUSE CVE CVE-2026-55971 | recommended: 9 | 2026-08-02T16:37:19+00:00 | Vulnerability · Source |
| CVE-2026-56741 | suse_vex | SUSE CVE CVE-2026-56741 | known not affected: 35 recommended: 65 | 2026-08-02T16:37:17+00:00 | Vulnerability · Source |
| CVE-2026-63796 | suse_vex | SUSE CVE CVE-2026-63796 | known affected: 298 recommended: 4 | 2026-08-02T16:37:15+00:00 | Vulnerability · Source |
| CVE-2026-63798 | suse_vex | SUSE CVE CVE-2026-63798 | known not affected: 298 recommended: 4 | 2026-08-02T16:37:13+00:00 | Vulnerability · Source |
| CVE-2026-63805 | suse_vex | SUSE CVE CVE-2026-63805 | known not affected: 298 recommended: 4 | 2026-08-02T16:37:12+00:00 | Vulnerability · Source |
| CVE-2026-64339 | redhat_vex | kernel: usb: misc: usbio: bound bulk IN response length to the received transfer | known affected: 76 known not affected: 198 | 2026-08-02T15:44:28+00:00 | Vulnerability · Source |
| CVE-2026-23467 | redhat_vex | kernel: drm/i915/dmc: Fix an unlikely NULL pointer deference at probe | known affected: 198 known not affected: 76 | 2026-08-02T12:10:50+00:00 | Vulnerability · Source |
| CVE-2026-31540 | redhat_vex | kernel: drm/i915/gt: Check set_default_submission() before deferencing | known affected: 246 known not affected: 28 | 2026-08-02T12:10:34+00:00 | Vulnerability · Source |
| CVE-2026-18572 | redhat_vex | keycloak-services: keycloak-services: UMA claim token can override authorization time-policy evaluation attributes | known affected: 3 known not affected: 3 | 2026-08-02T07:03:45+00:00 | Vulnerability · Source |
| CVE-2026-18573 | redhat_vex | keycloak-services: keycloak-services: Client access-type policy condition bypass during client update | known affected: 3 known not affected: 3 | 2026-08-02T07:03:42+00:00 | Vulnerability · Source |
| CVE-2026-18570 | redhat_vex | keycloak-services: keycloak-services: Full-scope-disabled client policy validation bypass via omitted fullScopeAllowed | known affected: 3 known not affected: 3 | 2026-08-02T07:03:34+00:00 | Vulnerability · Source |
| CVE-2025-66448 | redhat_vex | vllm: vLLM: Remote Code Execution via malicious model configuration | fixed: 37 known affected: 16 known not affected: 653 | 2026-08-02T00:00:57+00:00 | Vulnerability · Source |
| CVE-2001-1267 | suse_vex | SUSE CVE CVE-2001-1267 | known not affected: 107 recommended: 22 | 2026-08-01T23:43:56+00:00 | Vulnerability · Source |
| CVE-2002-0392 | suse_vex | SUSE CVE CVE-2002-0392 | known not affected: 126 | 2026-08-01T23:43:54+00:00 | Vulnerability · Source |
| CVE-2005-1080 | suse_vex | SUSE CVE CVE-2005-1080 | known affected: 40 known not affected: 141 recommended: 19 | 2026-08-01T23:43:52+00:00 | Vulnerability · Source |
| CVE-2005-2490 | suse_vex | SUSE CVE CVE-2005-2490 | known not affected: 111 | 2026-08-01T23:43:51+00:00 | Vulnerability · Source |
| CVE-2005-2492 | suse_vex | SUSE CVE CVE-2005-2492 | known not affected: 409 | 2026-08-01T23:43:50+00:00 | Vulnerability · Source |
| CVE-2006-1059 | suse_vex | SUSE CVE CVE-2006-1059 | recommended: 145 | 2026-08-01T23:43:48+00:00 | Vulnerability · Source |
| CVE-2006-1932 | suse_vex | SUSE CVE CVE-2006-1932 | recommended: 29 | 2026-08-01T23:43:47+00:00 | Vulnerability · Source |