VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2024-57989 | redhat_vex | kernel: wifi: mt76: mt7925: fix NULL deref check in mt7925_change_vif_links | fixed: 612 known affected: 22 known not affected: 90 | 2026-07-24T03:35:25+00:00 | Vulnerability · Source |
| CVE-2026-43190 | redhat_vex | kernel: netfilter: xt_tcpmss: check remaining length before reading optlen | fixed: 2085 known affected: 36 | 2026-07-24T03:35:08+00:00 | Vulnerability · Source |
| CVE-2026-53123 | redhat_vex | kernel: md: wake raid456 reshape waiters before suspend | known affected: 184 known not affected: 90 | 2026-07-24T03:33:16+00:00 | Vulnerability · Source |
| CVE-2024-56675 | redhat_vex | kernel: bpf: Fix UAF via mismatching bpf_prog/attachment RCU flavors | fixed: 612 known affected: 50 known not affected: 62 | 2026-07-24T03:33:09+00:00 | Vulnerability · Source |
| CVE-2026-44209 | redhat_vex | banks: banks: Remote Code Execution via Server-Side Template Injection | known affected: 2 known not affected: 3 | 2026-07-24T03:33:08+00:00 | Vulnerability · Source |
| CVE-2025-71239 | suse_vex | SUSE CVE CVE-2025-71239 | first fixed: 2 known affected: 635 known not affected: 99 recommended: 172 | 2026-07-24T02:46:11+00:00 | Vulnerability · Source |
| CVE-2025-71268 | suse_vex | SUSE CVE CVE-2025-71268 | first fixed: 2 known affected: 591 known not affected: 24 recommended: 332 | 2026-07-24T02:46:09+00:00 | Vulnerability · Source |
| CVE-2025-71292 | suse_vex | SUSE CVE CVE-2025-71292 | known affected: 4 known not affected: 289 | 2026-07-24T02:46:06+00:00 | Vulnerability · Source |
| CVE-2025-71293 | suse_vex | SUSE CVE CVE-2025-71293 | known not affected: 293 | 2026-07-24T02:46:03+00:00 | Vulnerability · Source |
| CVE-2025-71299 | suse_vex | SUSE CVE CVE-2025-71299 | known not affected: 293 | 2026-07-24T02:45:58+00:00 | Vulnerability · Source |
| CVE-2025-71312 | suse_vex | SUSE CVE CVE-2025-71312 | known not affected: 293 | 2026-07-24T02:45:55+00:00 | Vulnerability · Source |
| CVE-2026-3842 | suse_vex | SUSE CVE CVE-2026-3842 | known affected: 576 known not affected: 449 recommended: 373 | 2026-07-24T02:45:32+00:00 | Vulnerability · Source |
| CVE-2026-4105 | suse_vex | SUSE CVE CVE-2026-4105 | first fixed: 1 known affected: 480 recommended: 476 | 2026-07-24T02:45:29+00:00 | Vulnerability · Source |
| CVE-2026-4890 | suse_vex | SUSE CVE CVE-2026-4890 | known affected: 8 recommended: 42 | 2026-07-24T02:45:23+00:00 | Vulnerability · Source |
| CVE-2026-4891 | suse_vex | SUSE CVE CVE-2026-4891 | known affected: 8 recommended: 42 | 2026-07-24T02:45:22+00:00 | Vulnerability · Source |
| CVE-2026-4892 | suse_vex | SUSE CVE CVE-2026-4892 | known affected: 8 recommended: 42 | 2026-07-24T02:45:20+00:00 | Vulnerability · Source |
| CVE-2026-8595 | suse_vex | SUSE CVE CVE-2026-8595 | known not affected: 3 | 2026-07-24T02:44:58+00:00 | Vulnerability · Source |
| CVE-2026-8925 | suse_vex | SUSE CVE CVE-2026-8925 | known not affected: 143 recommended: 9 | 2026-07-24T02:44:56+00:00 | Vulnerability · Source |
| CVE-2026-8932 | suse_vex | SUSE CVE CVE-2026-8932 | known affected: 143 recommended: 9 | 2026-07-24T02:44:53+00:00 | Vulnerability · Source |
| CVE-2026-8953 | suse_vex | SUSE CVE CVE-2026-8953 | known affected: 30 recommended: 125 | 2026-07-24T02:44:51+00:00 | Vulnerability · Source |
| CVE-2026-9546 | suse_vex | SUSE CVE CVE-2026-9546 | known not affected: 143 recommended: 9 | 2026-07-24T02:44:43+00:00 | Vulnerability · Source |
| CVE-2026-10051 | suse_vex | SUSE CVE CVE-2026-10051 | known not affected: 163 | 2026-07-24T02:44:39+00:00 | Vulnerability · Source |
| CVE-2026-11352 | suse_vex | SUSE CVE CVE-2026-11352 | known not affected: 144 recommended: 9 | 2026-07-24T02:44:32+00:00 | Vulnerability · Source |
| CVE-2026-11564 | suse_vex | SUSE CVE CVE-2026-11564 | known not affected: 144 recommended: 9 | 2026-07-24T02:44:31+00:00 | Vulnerability · Source |
| CVE-2026-11586 | suse_vex | SUSE CVE CVE-2026-11586 | known not affected: 144 recommended: 9 | 2026-07-24T02:44:29+00:00 | Vulnerability · Source |
| CVE-2026-11856 | suse_vex | SUSE CVE CVE-2026-11856 | known affected: 151 recommended: 9 | 2026-07-24T02:44:27+00:00 | Vulnerability · Source |
| CVE-2026-12548 | suse_vex | SUSE CVE CVE-2026-12548 | known affected: 238 | 2026-07-24T02:44:23+00:00 | Vulnerability · Source |
| CVE-2026-15788 | suse_vex | SUSE CVE CVE-2026-15788 | known not affected: 4 | 2026-07-24T02:43:56+00:00 | Vulnerability · Source |
| CVE-2026-15789 | suse_vex | SUSE CVE CVE-2026-15789 | known affected: 7 | 2026-07-24T02:43:54+00:00 | Vulnerability · Source |
| CVE-2026-15791 | suse_vex | SUSE CVE CVE-2026-15791 | known affected: 7 | 2026-07-24T02:43:52+00:00 | Vulnerability · Source |
| CVE-2026-15792 | suse_vex | SUSE CVE CVE-2026-15792 | known affected: 7 | 2026-07-24T02:43:51+00:00 | Vulnerability · Source |
| CVE-2026-15793 | suse_vex | SUSE CVE CVE-2026-15793 | known affected: 7 | 2026-07-24T02:43:49+00:00 | Vulnerability · Source |
| CVE-2026-16277 | suse_vex | SUSE CVE CVE-2026-16277 | known affected: 39 | 2026-07-24T02:43:46+00:00 | Vulnerability · Source |
| CVE-2026-16461 | suse_vex | SUSE CVE CVE-2026-16461 | known affected: 39 | 2026-07-24T02:42:01+00:00 | Vulnerability · Source |
| CVE-2026-16473 | suse_vex | SUSE CVE CVE-2026-16473 | known affected: 83 | 2026-07-24T02:42:00+00:00 | Vulnerability · Source |
| CVE-2026-16493 | suse_vex | SUSE CVE CVE-2026-16493 | known affected: 15 | 2026-07-24T02:41:58+00:00 | Vulnerability · Source |
| CVE-2026-16517 | suse_vex | SUSE CVE CVE-2026-16517 | known affected: 158 | 2026-07-24T02:41:56+00:00 | Vulnerability · Source |
| CVE-2026-16560 | suse_vex | SUSE CVE CVE-2026-16560 | known affected: 97 | 2026-07-24T02:41:55+00:00 | Vulnerability · Source |
| CVE-2026-21411 | suse_vex | SUSE CVE CVE-2026-21411 | No product status | 2026-07-24T02:41:51+00:00 | Vulnerability · Source |
| CVE-2026-21723 | suse_vex | SUSE CVE CVE-2026-21723 | known affected: 3 | 2026-07-24T02:41:49+00:00 | Vulnerability · Source |
| CVE-2026-22976 | suse_vex | SUSE CVE CVE-2026-22976 | first fixed: 2 known affected: 567 recommended: 344 | 2026-07-24T02:41:43+00:00 | Vulnerability · Source |
| CVE-2026-22977 | suse_vex | SUSE CVE CVE-2026-22977 | first fixed: 2 known affected: 518 known not affected: 81 recommended: 307 | 2026-07-24T02:41:42+00:00 | Vulnerability · Source |
| CVE-2026-22978 | suse_vex | SUSE CVE CVE-2026-22978 | first fixed: 2 known affected: 614 recommended: 344 | 2026-07-24T02:41:40+00:00 | Vulnerability · Source |
| CVE-2026-22979 | suse_vex | SUSE CVE CVE-2026-22979 | first fixed: 2 known affected: 498 known not affected: 156 recommended: 336 | 2026-07-24T02:41:38+00:00 | Vulnerability · Source |
| CVE-2026-22982 | suse_vex | SUSE CVE CVE-2026-22982 | first fixed: 2 known affected: 538 known not affected: 112 recommended: 295 | 2026-07-24T02:41:36+00:00 | Vulnerability · Source |
| CVE-2026-22984 | suse_vex | SUSE CVE CVE-2026-22984 | first fixed: 2 known affected: 394 known not affected: 256 recommended: 368 | 2026-07-24T02:41:35+00:00 | Vulnerability · Source |
| CVE-2026-22985 | suse_vex | SUSE CVE CVE-2026-22985 | first fixed: 2 known affected: 140 known not affected: 112 recommended: 307 | 2026-07-24T02:41:33+00:00 | Vulnerability · Source |
| CVE-2026-22988 | suse_vex | SUSE CVE CVE-2026-22988 | first fixed: 2 known not affected: 224 recommended: 344 | 2026-07-24T02:41:32+00:00 | Vulnerability · Source |
| CVE-2026-22990 | suse_vex | SUSE CVE CVE-2026-22990 | first fixed: 2 known affected: 614 recommended: 405 | 2026-07-24T02:41:30+00:00 | Vulnerability · Source |
| CVE-2026-22991 | suse_vex | SUSE CVE CVE-2026-22991 | first fixed: 2 known affected: 600 known not affected: 18 recommended: 344 | 2026-07-24T02:41:29+00:00 | Vulnerability · Source |