VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-23604 | suse_vex | SUSE CVE CVE-2023-23604 | known affected: 36 recommended: 9 | 2026-07-03T04:41:58+00:00 | Vulnerability · Source |
| CVE-2023-25736 | suse_vex | SUSE CVE CVE-2023-25736 | known affected: 1 recommended: 9 | 2026-07-03T04:41:46+00:00 | Vulnerability · Source |
| CVE-2023-27539 | suse_vex | SUSE CVE CVE-2023-27539 | known affected: 396 recommended: 32 | 2026-07-03T04:41:32+00:00 | Vulnerability · Source |
| CVE-2023-28486 | suse_vex | SUSE CVE CVE-2023-28486 | known affected: 286 known not affected: 15 recommended: 280 | 2026-07-03T04:41:25+00:00 | Vulnerability · Source |
| CVE-2023-29543 | suse_vex | SUSE CVE CVE-2023-29543 | known affected: 15 recommended: 9 | 2026-07-03T04:41:08+00:00 | Vulnerability · Source |
| CVE-2023-32004 | suse_vex | SUSE CVE CVE-2023-32004 | known not affected: 558 recommended: 5 | 2026-07-03T04:40:55+00:00 | Vulnerability · Source |
| CVE-2023-53063 | suse_vex | SUSE CVE CVE-2023-53063 | known affected: 394 recommended: 23 | 2026-07-03T04:37:30+00:00 | Vulnerability · Source |
| CVE-2023-53683 | suse_vex | SUSE CVE CVE-2023-53683 | known affected: 354 known not affected: 274 recommended: 219 | 2026-07-03T04:34: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-4766 | suse_vex | SUSE CVE CVE-2024-4766 | known affected: 33 recommended: 9 | 2026-07-03T04:31:26+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-5694 | suse_vex | SUSE CVE CVE-2024-5694 | known affected: 33 recommended: 9 | 2026-07-03T04:31:15+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-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-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-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-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-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-13006 | suse_vex | SUSE CVE CVE-2026-13006 | recommended: 4 | 2026-07-03T03:26:26+00:00 | Vulnerability · Source |
| CVE-2026-13769 | suse_vex | SUSE CVE CVE-2026-13769 | known affected: 31 | 2026-07-03T03:26:16+00:00 | Vulnerability · Source |
| CVE-2026-31451 | suse_vex | SUSE CVE CVE-2026-31451 | known affected: 47 known not affected: 184 | 2026-07-03T03:20:39+00:00 | Vulnerability · Source |
| CVE-2026-31622 | suse_vex | SUSE CVE CVE-2026-31622 | known affected: 458 known not affected: 19 recommended: 158 | 2026-07-03T03:19:22+00:00 | Vulnerability · Source |
| CVE-2026-32762 | suse_vex | SUSE CVE CVE-2026-32762 | known not affected: 89 | 2026-07-03T03:18:19+00:00 | Vulnerability · Source |
| CVE-2026-35505 | suse_vex | SUSE CVE CVE-2026-35505 | No product status | 2026-07-03T03:17:25+00:00 | Vulnerability · Source |
| CVE-2026-40917 | suse_vex | SUSE CVE CVE-2026-40917 | recommended: 9 | 2026-07-03T03:16:44+00:00 | Vulnerability · Source |
| CVE-2026-44628 | suse_vex | SUSE CVE CVE-2026-44628 | No product status | 2026-07-03T03:11:14+00:00 | Vulnerability · Source |
| CVE-2026-44946 | suse_vex | SUSE CVE CVE-2026-44946 | No product status | 2026-07-03T03:10:49+00:00 | Vulnerability · Source |
| CVE-2026-45372 | suse_vex | SUSE CVE CVE-2026-45372 | known affected: 5 recommended: 2 | 2026-07-03T03:10:40+00:00 | Vulnerability · Source |
| CVE-2026-46527 | suse_vex | SUSE CVE CVE-2026-46527 | known affected: 5 recommended: 2 | 2026-07-03T03:07:43+00:00 | Vulnerability · Source |
| CVE-2026-50003 | suse_vex | SUSE CVE CVE-2026-50003 | No product status | 2026-07-03T03:05:51+00:00 | Vulnerability · Source |
| CVE-2026-50052 | suse_vex | SUSE CVE CVE-2026-50052 | recommended: 3 | 2026-07-03T03:05:48+00:00 | Vulnerability · Source |
| CVE-2026-50254 | suse_vex | SUSE CVE CVE-2026-50254 | No product status | 2026-07-03T03:05:44+00:00 | Vulnerability · Source |
| CVE-2026-52868 | suse_vex | SUSE CVE CVE-2026-52868 | No product status | 2026-07-03T03:05:40+00:00 | Vulnerability · Source |
| CVE-2026-53114 | suse_vex | SUSE CVE CVE-2026-53114 | known affected: 15 known not affected: 276 | 2026-07-03T03:05:04+00:00 | Vulnerability · Source |
| CVE-2026-53118 | suse_vex | SUSE CVE CVE-2026-53118 | known affected: 160 known not affected: 131 | 2026-07-03T03:05:02+00:00 | Vulnerability · Source |
| CVE-2026-53326 | suse_vex | SUSE CVE CVE-2026-53326 | known not affected: 277 | 2026-07-03T03:04:36+00:00 | Vulnerability · Source |
| CVE-2026-53327 | suse_vex | SUSE CVE CVE-2026-53327 | known affected: 200 known not affected: 77 | 2026-07-03T03:04:34+00:00 | Vulnerability · Source |
| CVE-2026-53328 | suse_vex | SUSE CVE CVE-2026-53328 | known not affected: 277 | 2026-07-03T03:04:32+00:00 | Vulnerability · Source |
| CVE-2026-53333 | suse_vex | SUSE CVE CVE-2026-53333 | known not affected: 277 | 2026-07-03T03:04:23+00:00 | Vulnerability · Source |
| CVE-2026-53334 | suse_vex | SUSE CVE CVE-2026-53334 | known not affected: 277 | 2026-07-03T03:04:20+00:00 | Vulnerability · Source |
| CVE-2026-53336 | suse_vex | SUSE CVE CVE-2026-53336 | known affected: 112 known not affected: 165 | 2026-07-03T03:04:17+00:00 | Vulnerability · Source |
| CVE-2026-53340 | suse_vex | SUSE CVE CVE-2026-53340 | known not affected: 277 | 2026-07-03T03:04:11+00:00 | Vulnerability · Source |