VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-40976 | suse_vex | SUSE CVE CVE-2024-40976 | known affected: 362 known not affected: 109 recommended: 658 | 2026-08-13T16:44:54+00:00 | Vulnerability · Source |
| CVE-2026-64283 | redhat_vex | kernel: KVM: guest_memfd: Treat memslot binding offset+size as unsigned values | known not affected: 274 | 2026-08-13T16:44:52+00:00 | Vulnerability · Source |
| CVE-2026-64177 | redhat_vex | kernel: phonet/pep: disable BH around forwarded sk_receive_skb() | known affected: 14 known not affected: 260 | 2026-08-13T16:44:51+00:00 | Vulnerability · Source |
| CVE-2024-41033 | suse_vex | SUSE CVE CVE-2024-41033 | known not affected: 324 | 2026-08-13T16:44:46+00:00 | Vulnerability · Source |
| CVE-2024-42139 | suse_vex | SUSE CVE CVE-2024-42139 | known affected: 401 known not affected: 169 recommended: 648 | 2026-08-13T16:44:32+00:00 | Vulnerability · Source |
| CVE-2024-42148 | suse_vex | SUSE CVE CVE-2024-42148 | known affected: 530 recommended: 746 | 2026-08-13T16:44:29+00:00 | Vulnerability · Source |
| CVE-2024-43357 | suse_vex | SUSE CVE CVE-2024-43357 | known affected: 17 known not affected: 153 | 2026-08-13T16:44:15+00:00 | Vulnerability · Source |
| CVE-2024-43824 | suse_vex | SUSE CVE CVE-2024-43824 | known affected: 569 known not affected: 138 recommended: 360 | 2026-08-13T16:44:13+00:00 | Vulnerability · Source |
| CVE-2024-43844 | suse_vex | SUSE CVE CVE-2024-43844 | known not affected: 310 | 2026-08-13T16:44:11+00:00 | Vulnerability · Source |
| CVE-2024-43904 | suse_vex | SUSE CVE CVE-2024-43904 | known affected: 340 known not affected: 195 recommended: 657 | 2026-08-13T16:44:04+00:00 | Vulnerability · Source |
| CVE-2024-44937 | suse_vex | SUSE CVE CVE-2024-44937 | known not affected: 310 recommended: 59 | 2026-08-13T16:43:57+00:00 | Vulnerability · Source |
| CVE-2024-44980 | suse_vex | SUSE CVE CVE-2024-44980 | known not affected: 325 recommended: 59 | 2026-08-13T16:43:51+00:00 | Vulnerability · Source |
| CVE-2024-44981 | suse_vex | SUSE CVE CVE-2024-44981 | known not affected: 324 | 2026-08-13T16:43:49+00:00 | Vulnerability · Source |
| CVE-2026-53361 | redhat_vex | kernel: af_unix: Set gc_in_progress to true in unix_gc() | known affected: 76 known not affected: 198 | 2026-08-13T16:43:45+00:00 | Vulnerability · Source |
| CVE-2026-53175 | redhat_vex | kernel: Linux kernel: Memory corruption via use-after-free in internet fragmentation | known not affected: 260 under investigation: 14 | 2026-08-13T16:43:44+00:00 | Vulnerability · Source |
| CVE-2024-45720 | suse_vex | SUSE CVE CVE-2024-45720 | known not affected: 243 | 2026-08-13T16:43:42+00:00 | Vulnerability · Source |
| CVE-2024-45751 | suse_vex | SUSE CVE CVE-2024-45751 | known affected: 30 recommended: 12 | 2026-08-13T16:43:41+00:00 | Vulnerability · Source |
| CVE-2026-54297 | redhat_vex | faraday: Faraday: Denial of Service via crafted nested query strings | fixed: 20 known affected: 44 known not affected: 359 | 2026-08-13T16:43:37+00:00 | Vulnerability · Source |
| CVE-2024-46699 | suse_vex | SUSE CVE CVE-2024-46699 | known not affected: 325 recommended: 59 | 2026-08-13T16:43:36+00:00 | Vulnerability · Source |
| CVE-2024-46700 | suse_vex | SUSE CVE CVE-2024-46700 | known not affected: 325 recommended: 59 | 2026-08-13T16:43:34+00:00 | Vulnerability · Source |
| CVE-2024-46701 | suse_vex | SUSE CVE CVE-2024-46701 | known not affected: 324 | 2026-08-13T16:43:32+00:00 | Vulnerability · Source |
| CVE-2024-46707 | suse_vex | SUSE CVE CVE-2024-46707 | known affected: 566 known not affected: 46 recommended: 715 | 2026-08-13T16:43:30+00:00 | Vulnerability · Source |
| CVE-2024-46712 | suse_vex | SUSE CVE CVE-2024-46712 | known not affected: 325 recommended: 59 | 2026-08-13T16:43:28+00:00 | Vulnerability · Source |
| CVE-2024-46759 | suse_vex | SUSE CVE CVE-2024-46759 | known affected: 349 known not affected: 6 recommended: 772 | 2026-08-13T16:43:22+00:00 | Vulnerability · Source |
| CVE-2024-46824 | suse_vex | SUSE CVE CVE-2024-46824 | known not affected: 325 recommended: 89 | 2026-08-13T16:43:16+00:00 | Vulnerability · Source |
| CVE-2024-46837 | suse_vex | SUSE CVE CVE-2024-46837 | known not affected: 324 recommended: 59 | 2026-08-13T16:43:14+00:00 | Vulnerability · Source |
| CVE-2024-47674 | suse_vex | SUSE CVE CVE-2024-47674 | known affected: 343 known not affected: 163 recommended: 983 | 2026-08-13T16:43:05+00:00 | Vulnerability · Source |
| CVE-2024-47689 | suse_vex | SUSE CVE CVE-2024-47689 | known not affected: 379 recommended: 6 | 2026-08-13T16:43:03+00:00 | Vulnerability · Source |
| CVE-2024-47747 | suse_vex | SUSE CVE CVE-2024-47747 | known affected: 356 known not affected: 177 recommended: 895 | 2026-08-13T16:42:57+00:00 | Vulnerability · Source |
| CVE-2024-47777 | suse_vex | SUSE CVE CVE-2024-47777 | known affected: 35 recommended: 99 | 2026-08-13T16:42:55+00:00 | Vulnerability · Source |
| CVE-2024-49880 | suse_vex | SUSE CVE CVE-2024-49880 | known not affected: 402 recommended: 6 | 2026-08-13T16:42:50+00:00 | Vulnerability · Source |
| CVE-2024-49945 | suse_vex | SUSE CVE CVE-2024-49945 | known affected: 481 known not affected: 60 recommended: 787 | 2026-08-13T16:42:45+00:00 | Vulnerability · Source |
| CVE-2024-50005 | suse_vex | SUSE CVE CVE-2024-50005 | known not affected: 379 recommended: 6 | 2026-08-13T16:42:37+00:00 | Vulnerability · Source |
| CVE-2024-50109 | suse_vex | SUSE CVE CVE-2024-50109 | known not affected: 370 recommended: 49 | 2026-08-13T16:42:26+00:00 | Vulnerability · Source |
| CVE-2024-50112 | suse_vex | SUSE CVE CVE-2024-50112 | known not affected: 370 recommended: 6 | 2026-08-13T16:42:24+00:00 | Vulnerability · Source |
| CVE-2024-50128 | suse_vex | SUSE CVE CVE-2024-50128 | known affected: 352 known not affected: 224 recommended: 751 | 2026-08-13T16:42:20+00:00 | Vulnerability · Source |
| CVE-2024-50267 | suse_vex | SUSE CVE CVE-2024-50267 | known affected: 430 known not affected: 42 recommended: 870 | 2026-08-13T16:42:10+00:00 | Vulnerability · Source |
| CVE-2024-53049 | suse_vex | SUSE CVE CVE-2024-53049 | known not affected: 372 | 2026-08-13T16:42:04+00:00 | Vulnerability · Source |
| CVE-2024-53164 | suse_vex | SUSE CVE CVE-2024-53164 | first fixed: 2 known affected: 489 known not affected: 121 recommended: 858 | 2026-08-13T16:41:52+00:00 | Vulnerability · Source |
| CVE-2024-53183 | suse_vex | SUSE CVE CVE-2024-53183 | known affected: 200 known not affected: 237 | 2026-08-13T16:41:47+00:00 | Vulnerability · Source |
| CVE-2024-53219 | suse_vex | SUSE CVE CVE-2024-53219 | known affected: 378 known not affected: 163 recommended: 53 | 2026-08-13T16:41:40+00:00 | Vulnerability · Source |
| CVE-2024-53682 | suse_vex | SUSE CVE CVE-2024-53682 | known not affected: 346 recommended: 53 | 2026-08-13T16:41:35+00:00 | Vulnerability · Source |
| CVE-2024-56631 | suse_vex | SUSE CVE CVE-2024-56631 | known affected: 511 known not affected: 42 recommended: 766 | 2026-08-13T16:41:15+00:00 | Vulnerability · Source |
| CVE-2024-21489 | redhat_vex | uplot: Prototype Pollution in uplot | fixed: 11 known affected: 15 known not affected: 6 | 2026-08-13T16:41:14+00:00 | Vulnerability · Source |
| CVE-2024-56744 | suse_vex | SUSE CVE CVE-2024-56744 | known not affected: 438 | 2026-08-13T16:40:54+00:00 | Vulnerability · Source |
| CVE-2024-57792 | suse_vex | SUSE CVE CVE-2024-57792 | known affected: 346 known not affected: 186 recommended: 587 | 2026-08-13T16:40:48+00:00 | Vulnerability · Source |
| CVE-2024-57914 | suse_vex | SUSE CVE CVE-2024-57914 | known not affected: 346 recommended: 53 | 2026-08-13T16:40:41+00:00 | Vulnerability · Source |
| CVE-2024-57947 | suse_vex | SUSE CVE CVE-2024-57947 | known affected: 377 known not affected: 130 recommended: 685 | 2026-08-13T16:40:36+00:00 | Vulnerability · Source |
| CVE-2024-58066 | suse_vex | SUSE CVE CVE-2024-58066 | known not affected: 352 | 2026-08-13T16:40:28+00:00 | Vulnerability · Source |
| CVE-2026-65325 | redhat_vex | Apache Traffic Server: HTTP/2 multiplexed origin sessions are reused without certificate re-verification | known not affected: 1 | 2026-08-13T16:40:27+00:00 | Vulnerability · Source |