VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292286 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-0744 | suse_vex | SUSE CVE CVE-2024-0744 | known affected: 93 recommended: 9 | 2026-07-03T04:32:07+00:00 | Vulnerability · Source |
| CVE-2024-0748 | suse_vex | SUSE CVE CVE-2024-0748 | known affected: 93 recommended: 9 | 2026-07-03T04:32:05+00:00 | Vulnerability · Source |
| CVE-2024-1554 | suse_vex | SUSE CVE CVE-2024-1554 | known affected: 42 recommended: 9 | 2026-07-03T04:32:02+00:00 | Vulnerability · Source |
| CVE-2024-1555 | suse_vex | SUSE CVE CVE-2024-1555 | known affected: 42 recommended: 9 | 2026-07-03T04:32:01+00:00 | Vulnerability · Source |
| CVE-2024-2606 | suse_vex | SUSE CVE CVE-2024-2606 | known affected: 41 recommended: 9 | 2026-07-03T04:31:57+00:00 | Vulnerability · Source |
| CVE-2024-3862 | suse_vex | SUSE CVE CVE-2024-3862 | known affected: 32 recommended: 9 | 2026-07-03T04:31:42+00:00 | Vulnerability · Source |
| CVE-2024-3865 | suse_vex | SUSE CVE CVE-2024-3865 | known affected: 32 recommended: 9 | 2026-07-03T04:31:39+00:00 | Vulnerability · Source |
| CVE-2024-3933 | suse_vex | SUSE CVE CVE-2024-3933 | known not affected: 538 recommended: 148 | 2026-07-03T04:31:37+00:00 | Vulnerability · Source |
| CVE-2024-4766 | suse_vex | SUSE CVE CVE-2024-4766 | known affected: 33 recommended: 9 | 2026-07-03T04:31:26+00:00 | Vulnerability · Source |
| CVE-2024-4774 | suse_vex | SUSE CVE CVE-2024-4774 | known affected: 33 recommended: 9 | 2026-07-03T04:31:24+00:00 | Vulnerability · Source |
| CVE-2024-4778 | suse_vex | SUSE CVE CVE-2024-4778 | known affected: 33 recommended: 9 | 2026-07-03T04:31:21+00:00 | Vulnerability · Source |
| CVE-2024-5689 | suse_vex | SUSE CVE CVE-2024-5689 | known affected: 33 recommended: 9 | 2026-07-03T04:31:18+00:00 | Vulnerability · Source |
| CVE-2024-5694 | suse_vex | SUSE CVE CVE-2024-5694 | known affected: 33 recommended: 9 | 2026-07-03T04:31:15+00:00 | Vulnerability · Source |
| CVE-2024-5701 | suse_vex | SUSE CVE CVE-2024-5701 | known affected: 33 recommended: 9 | 2026-07-03T04:31:11+00:00 | Vulnerability · Source |
| CVE-2024-7528 | suse_vex | SUSE CVE CVE-2024-7528 | known affected: 27 recommended: 231 | 2026-07-03T04:30:47+00:00 | Vulnerability · Source |
| CVE-2024-7546 | suse_vex | SUSE CVE CVE-2024-7546 | recommended: 9 | 2026-07-03T04:30:41+00:00 | Vulnerability · Source |
| CVE-2024-8394 | suse_vex | SUSE CVE CVE-2024-8394 | known affected: 30 recommended: 55 | 2026-07-03T04:30:27+00:00 | Vulnerability · Source |
| CVE-2024-21890 | suse_vex | SUSE CVE CVE-2024-21890 | known not affected: 526 recommended: 47 | 2026-07-03T04:28:56+00:00 | Vulnerability · Source |
| CVE-2024-21892 | suse_vex | SUSE CVE CVE-2024-21892 | known not affected: 446 recommended: 142 | 2026-07-03T04:28:54+00:00 | Vulnerability · Source |
| CVE-2024-22017 | suse_vex | SUSE CVE CVE-2024-22017 | known not affected: 526 recommended: 50 | 2026-07-03T04:28:52+00:00 | Vulnerability · Source |
| CVE-2024-24789 | suse_vex | SUSE CVE CVE-2024-24789 | known affected: 15 known not affected: 58 recommended: 279 | 2026-07-03T04:28:44+00:00 | Vulnerability · Source |
| CVE-2024-24795 | suse_vex | SUSE CVE CVE-2024-24795 | known affected: 450 recommended: 428 | 2026-07-03T04:28:42+00:00 | Vulnerability · Source |
| CVE-2024-26141 | suse_vex | SUSE CVE CVE-2024-26141 | known affected: 394 recommended: 35 | 2026-07-03T04:28:32+00:00 | Vulnerability · Source |
| CVE-2024-26991 | suse_vex | SUSE CVE CVE-2024-26991 | known affected: 394 known not affected: 306 recommended: 360 | 2026-07-03T04:26:05+00:00 | Vulnerability · Source |
| CVE-2024-27027 | suse_vex | SUSE CVE CVE-2024-27027 | known affected: 394 known not affected: 306 recommended: 335 | 2026-07-03T04:25:31+00:00 | Vulnerability · Source |
| CVE-2024-30260 | suse_vex | SUSE CVE CVE-2024-30260 | known affected: 44 known not affected: 21 recommended: 178 | 2026-07-03T04:24:21+00:00 | Vulnerability · Source |
| CVE-2024-30261 | suse_vex | SUSE CVE CVE-2024-30261 | known affected: 24 known not affected: 21 recommended: 168 | 2026-07-03T04:24:19+00:00 | Vulnerability · Source |
| CVE-2024-34161 | suse_vex | SUSE CVE CVE-2024-34161 | known not affected: 60 | 2026-07-03T04:24:05+00:00 | Vulnerability · Source |
| CVE-2026-46680 | redhat_vex | github.com/containerd/containerd: containerd: Privilege escalation via incorrect user ID handling | fixed: 3 known not affected: 192 | 2026-07-03T04:24:04+00:00 | Vulnerability · Source |
| CVE-2024-41946 | suse_vex | SUSE CVE CVE-2024-41946 | known affected: 394 known not affected: 141 recommended: 228 | 2026-07-03T04:14:51+00:00 | Vulnerability · Source |
| CVE-2024-42158 | suse_vex | SUSE CVE CVE-2024-42158 | known affected: 524 known not affected: 10 recommended: 677 | 2026-07-03T04:14:01+00:00 | Vulnerability · Source |
| CVE-2024-43591 | suse_vex | SUSE CVE CVE-2024-43591 | known affected: 394 known not affected: 10 recommended: 27 | 2026-07-03T04:13:08+00:00 | Vulnerability · Source |
| CVE-2024-46749 | suse_vex | SUSE CVE CVE-2024-46749 | known affected: 394 known not affected: 248 recommended: 330 | 2026-07-03T04:10:33+00:00 | Vulnerability · Source |
| CVE-2024-47533 | suse_vex | SUSE CVE CVE-2024-47533 | known affected: 394 recommended: 65 | 2026-07-03T04:09:59+00:00 | Vulnerability · Source |
| CVE-2024-50278 | suse_vex | SUSE CVE CVE-2024-50278 | known affected: 627 known not affected: 42 recommended: 490 | 2026-07-03T04:05:02+00:00 | Vulnerability · Source |
| CVE-2024-53975 | suse_vex | SUSE CVE CVE-2024-53975 | known affected: 158 | 2026-07-03T04:03:05+00:00 | Vulnerability · Source |
| CVE-2024-57988 | suse_vex | SUSE CVE CVE-2024-57988 | known affected: 394 known not affected: 350 recommended: 220 | 2026-07-03T03:59:47+00:00 | Vulnerability · Source |
| CVE-2024-58240 | suse_vex | SUSE CVE CVE-2024-58240 | known affected: 361 known not affected: 79 recommended: 654 | 2026-07-03T03:58:34+00:00 | Vulnerability · Source |
| CVE-2025-0838 | suse_vex | SUSE CVE CVE-2025-0838 | known affected: 433 known not affected: 12 recommended: 206 | 2026-07-03T03:58:21+00:00 | Vulnerability · Source |
| CVE-2025-9396 | suse_vex | SUSE CVE CVE-2025-9396 | recommended: 2 | 2026-07-03T03:56:00+00:00 | Vulnerability · Source |
| CVE-2025-10994 | suse_vex | SUSE CVE CVE-2025-10994 | recommended: 5 | 2026-07-03T03:55:45+00:00 | Vulnerability · Source |
| CVE-2025-10997 | suse_vex | SUSE CVE CVE-2025-10997 | recommended: 5 | 2026-07-03T03:55:43+00:00 | Vulnerability · Source |
| CVE-2025-24049 | suse_vex | SUSE CVE CVE-2025-24049 | known affected: 394 known not affected: 31 recommended: 5358 | 2026-07-03T03:51:18+00:00 | Vulnerability · Source |
| CVE-2025-30752 | suse_vex | SUSE CVE CVE-2025-30752 | known not affected: 653 | 2026-07-03T03:50:48+00:00 | Vulnerability · Source |
| CVE-2025-40776 | suse_vex | SUSE CVE CVE-2025-40776 | known not affected: 376 | 2026-07-03T03:34:27+00:00 | Vulnerability · Source |
| CVE-2025-40929 | suse_vex | SUSE CVE CVE-2025-40929 | recommended: 7 | 2026-07-03T03:34:22+00:00 | Vulnerability · Source |
| CVE-2025-54764 | suse_vex | SUSE CVE CVE-2025-54764 | recommended: 22 | 2026-07-03T03:33:38+00:00 | Vulnerability · Source |
| CVE-2026-6657 | suse_vex | SUSE CVE CVE-2026-6657 | No product status | 2026-07-03T03:27:38+00:00 | Vulnerability · Source |
| CVE-2026-9595 | suse_vex | SUSE CVE CVE-2026-9595 | known affected: 8 known not affected: 379 | 2026-07-03T03:26:58+00:00 | Vulnerability · Source |
| CVE-2026-10805 | suse_vex | SUSE CVE CVE-2026-10805 | known affected: 223 | 2026-07-03T03:26:46+00:00 | Vulnerability · Source |