VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2005-3391 | suse_vex | SUSE CVE CVE-2005-3391 | known affected: 2110 recommended: 201 | 2026-07-21T13:57:25+00:00 | Vulnerability · Source |
| CVE-2005-3392 | suse_vex | SUSE CVE CVE-2005-3392 | known affected: 2110 recommended: 201 | 2026-07-21T13:57:24+00:00 | Vulnerability · Source |
| CVE-2006-5456 | suse_vex | SUSE CVE CVE-2006-5456 | recommended: 96 | 2026-07-21T13:57:19+00:00 | Vulnerability · Source |
| CVE-2006-6143 | suse_vex | SUSE CVE CVE-2006-6143 | recommended: 67 | 2026-07-21T13:57:15+00:00 | Vulnerability · Source |
| CVE-2006-7243 | suse_vex | SUSE CVE CVE-2006-7243 | known affected: 2110 recommended: 527 | 2026-07-21T13:57:12+00:00 | Vulnerability · Source |
| CVE-2007-4351 | suse_vex | SUSE CVE CVE-2007-4351 | known not affected: 40 recommended: 52 | 2026-07-21T13:57:04+00:00 | Vulnerability · Source |
| CVE-2008-1950 | suse_vex | SUSE CVE CVE-2008-1950 | recommended: 55 | 2026-07-21T13:56:56+00:00 | Vulnerability · Source |
| CVE-2009-1890 | suse_vex | SUSE CVE CVE-2009-1890 | recommended: 227 | 2026-07-21T13:56:36+00:00 | Vulnerability · Source |
| CVE-2010-4150 | suse_vex | SUSE CVE CVE-2010-4150 | known not affected: 329 recommended: 520 | 2026-07-21T13:56:00+00:00 | Vulnerability · Source |
| CVE-2012-2688 | suse_vex | SUSE CVE CVE-2012-2688 | known affected: 2110 known not affected: 3 recommended: 548 | 2026-07-21T13:55:02+00:00 | Vulnerability · Source |
| CVE-2013-2127 | suse_vex | SUSE CVE CVE-2013-2127 | recommended: 112 | 2026-07-21T13:54:04+00:00 | Vulnerability · Source |
| CVE-2013-4536 | suse_vex | SUSE CVE CVE-2013-4536 | known affected: 3 known not affected: 1227 recommended: 377 | 2026-07-21T13:53:55+00:00 | Vulnerability · Source |
| CVE-2014-0467 | suse_vex | SUSE CVE CVE-2014-0467 | known not affected: 17 recommended: 195 | 2026-07-21T13:53:24+00:00 | Vulnerability · Source |
| CVE-2014-1494 | suse_vex | SUSE CVE CVE-2014-1494 | known affected: 1 recommended: 115 | 2026-07-21T13:53:22+00:00 | Vulnerability · Source |
| CVE-2014-8713 | suse_vex | SUSE CVE CVE-2014-8713 | known not affected: 1 recommended: 457 | 2026-07-21T13:52:37+00:00 | Vulnerability · Source |
| CVE-2015-2731 | suse_vex | SUSE CVE CVE-2015-2731 | known affected: 23 known not affected: 144 recommended: 329 | 2026-07-21T13:52:05+00:00 | Vulnerability · Source |
| CVE-2015-8735 | suse_vex | SUSE CVE CVE-2015-8735 | recommended: 436 | 2026-07-21T13:51:19+00:00 | Vulnerability · Source |
| CVE-2015-8740 | suse_vex | SUSE CVE CVE-2015-8740 | recommended: 436 | 2026-07-21T13:51:16+00:00 | Vulnerability · Source |
| CVE-2016-0775 | suse_vex | SUSE CVE CVE-2016-0775 | recommended: 147 | 2026-07-21T13:51:03+00:00 | Vulnerability · Source |
| CVE-2016-7401 | suse_vex | SUSE CVE CVE-2016-7401 | known not affected: 2 recommended: 24 | 2026-07-21T13:49:47+00:00 | Vulnerability · Source |
| CVE-2018-4299 | suse_vex | SUSE CVE CVE-2018-4299 | known affected: 76 known not affected: 82 recommended: 926 | 2026-07-21T13:46:09+00:00 | Vulnerability · Source |
| CVE-2018-5152 | suse_vex | SUSE CVE CVE-2018-5152 | known affected: 20 recommended: 74 | 2026-07-21T13:45:57+00:00 | Vulnerability · Source |
| CVE-2018-5801 | suse_vex | SUSE CVE CVE-2018-5801 | recommended: 62 | 2026-07-21T13:45:49+00:00 | Vulnerability · Source |
| CVE-2026-63929 | redhat_vex | kernel: iio: buffer: Fix DMA fence leak in iio_buffer_enqueue_dmabuf() | known affected: 76 known not affected: 198 | 2026-07-21T13:41:28+00:00 | Vulnerability · Source |
| CVE-2026-64019 | redhat_vex | kernel: nvme-pci: fix dma mapping leak on data setup error | known affected: 76 known not affected: 198 | 2026-07-21T13:36:47+00:00 | Vulnerability · Source |
| CVE-2018-16468 | suse_vex | SUSE CVE CVE-2018-16468 | known affected: 388 known not affected: 24 recommended: 145 | 2026-07-21T13:33:53+00:00 | Vulnerability · Source |
| CVE-2019-8844 | suse_vex | SUSE CVE CVE-2019-8844 | known affected: 37 known not affected: 82 recommended: 1045 | 2026-07-21T13:32:43+00:00 | Vulnerability · Source |
| CVE-2019-13456 | suse_vex | SUSE CVE CVE-2019-13456 | known affected: 77 known not affected: 93 recommended: 724 | 2026-07-21T13:31:57+00:00 | Vulnerability · Source |
| CVE-2020-25074 | suse_vex | SUSE CVE CVE-2020-25074 | recommended: 2 | 2026-07-21T13:29:48+00:00 | Vulnerability · Source |
| CVE-2021-21272 | suse_vex | SUSE CVE CVE-2021-21272 | known affected: 394 recommended: 92 | 2026-07-21T13:28:42+00:00 | Vulnerability · Source |
| CVE-2021-22960 | suse_vex | SUSE CVE CVE-2021-22960 | known not affected: 72 recommended: 378 | 2026-07-21T13:28:36+00:00 | Vulnerability · Source |
| CVE-2021-30459 | suse_vex | SUSE CVE CVE-2021-30459 | recommended: 6 | 2026-07-21T13:28:18+00:00 | Vulnerability · Source |
| CVE-2021-35266 | suse_vex | SUSE CVE CVE-2021-35266 | recommended: 139 | 2026-07-21T13:28:04+00:00 | Vulnerability · Source |
| CVE-2022-0545 | suse_vex | SUSE CVE CVE-2022-0545 | recommended: 13 | 2026-07-21T13:27:32+00:00 | Vulnerability · Source |
| CVE-2022-31626 | suse_vex | SUSE CVE CVE-2022-31626 | known not affected: 1 recommended: 4373 | 2026-07-21T13:26:33+00:00 | Vulnerability · Source |
| CVE-2023-28120 | suse_vex | SUSE CVE CVE-2023-28120 | known affected: 382 known not affected: 14 recommended: 127 | 2026-07-21T13:25:10+00:00 | Vulnerability · Source |
| CVE-2026-2291 | suse_vex | SUSE CVE CVE-2026-2291 | known affected: 10 recommended: 45 | 2026-07-21T13:18:23+00:00 | Vulnerability · Source |
| CVE-2026-4430 | suse_vex | SUSE CVE CVE-2026-4430 | known affected: 509 | 2026-07-21T13:18:11+00:00 | Vulnerability · Source |
| CVE-2026-6039 | suse_vex | SUSE CVE CVE-2026-6039 | known affected: 509 | 2026-07-21T13:18:02+00:00 | Vulnerability · Source |
| CVE-2026-6040 | suse_vex | SUSE CVE CVE-2026-6040 | known affected: 509 | 2026-07-21T13:18:00+00:00 | Vulnerability · Source |
| CVE-2026-6045 | suse_vex | SUSE CVE CVE-2026-6045 | known affected: 509 | 2026-07-21T13:17:59+00:00 | Vulnerability · Source |
| CVE-2026-6047 | suse_vex | SUSE CVE CVE-2026-6047 | known affected: 509 | 2026-07-21T13:17:58+00:00 | Vulnerability · Source |
| CVE-2026-8149 | suse_vex | SUSE CVE CVE-2026-8149 | known not affected: 78 | 2026-07-21T13:17:52+00:00 | Vulnerability · Source |
| CVE-2026-8356 | suse_vex | SUSE CVE CVE-2026-8356 | known affected: 509 | 2026-07-21T13:17:50+00:00 | Vulnerability · Source |
| CVE-2026-8357 | suse_vex | SUSE CVE CVE-2026-8357 | known affected: 509 | 2026-07-21T13:17:49+00:00 | Vulnerability · Source |
| CVE-2026-8358 | suse_vex | SUSE CVE CVE-2026-8358 | known affected: 509 | 2026-07-21T13:17:48+00:00 | Vulnerability · Source |
| CVE-2026-15809 | suse_vex | SUSE CVE CVE-2026-15809 | No product status | 2026-07-21T13:17:18+00:00 | Vulnerability · Source |
| CVE-2026-16207 | suse_vex | SUSE CVE CVE-2026-16207 | No product status | 2026-07-21T13:17:02+00:00 | Vulnerability · Source |
| CVE-2026-16208 | suse_vex | SUSE CVE CVE-2026-16208 | No product status | 2026-07-21T13:17:00+00:00 | Vulnerability · Source |
| CVE-2026-21729 | suse_vex | SUSE CVE CVE-2026-21729 | No product status | 2026-07-21T13:16:53+00:00 | Vulnerability · Source |