VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292142 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-0805 | suse_vex | SUSE CVE CVE-2015-0805 | known affected: 1 known not affected: 25 recommended: 246 | 2026-07-21T13:52:21+00:00 | Vulnerability · Source |
| CVE-2015-0828 | suse_vex | SUSE CVE CVE-2015-0828 | known not affected: 31 recommended: 251 | 2026-07-21T13:52:18+00:00 | Vulnerability · Source |
| CVE-2015-0848 | suse_vex | SUSE CVE CVE-2015-0848 | known not affected: 60 recommended: 221 | 2026-07-21T13:52:17+00:00 | Vulnerability · Source |
| CVE-2015-2170 | suse_vex | SUSE CVE CVE-2015-2170 | known not affected: 2241 recommended: 264 | 2026-07-21T13:52:13+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-3223 | suse_vex | SUSE CVE CVE-2015-3223 | known affected: 310 known not affected: 186 recommended: 4364 | 2026-07-21T13:51:52+00:00 | Vulnerability · Source |
| CVE-2015-4483 | suse_vex | SUSE CVE CVE-2015-4483 | known affected: 1 recommended: 246 | 2026-07-21T13:51:45+00:00 | Vulnerability · Source |
| CVE-2015-7219 | suse_vex | SUSE CVE CVE-2015-7219 | known affected: 2 recommended: 247 | 2026-07-21T13:51:26+00:00 | Vulnerability · Source |
| CVE-2015-7220 | suse_vex | SUSE CVE CVE-2015-7220 | known affected: 2 recommended: 247 | 2026-07-21T13:51:25+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-8737 | suse_vex | SUSE CVE CVE-2015-8737 | recommended: 436 | 2026-07-21T13:51:18+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-1933 | suse_vex | SUSE CVE CVE-2016-1933 | known affected: 21 recommended: 246 | 2026-07-21T13:50:52+00:00 | Vulnerability · Source |
| CVE-2016-1938 | suse_vex | SUSE CVE CVE-2016-1938 | known affected: 164 recommended: 626 | 2026-07-21T13:50:49+00:00 | Vulnerability · Source |
| CVE-2016-2105 | suse_vex | SUSE CVE CVE-2016-2105 | known affected: 324 known not affected: 331 recommended: 1049 | 2026-07-21T13:50:42+00:00 | Vulnerability · Source |
| CVE-2016-2529 | suse_vex | SUSE CVE CVE-2016-2529 | known affected: 3 recommended: 436 | 2026-07-21T13:50:31+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-2016-8574 | suse_vex | SUSE CVE CVE-2016-8574 | known affected: 300 recommended: 179 | 2026-07-21T13:49:34+00:00 | Vulnerability · Source |
| CVE-2016-8867 | suse_vex | SUSE CVE CVE-2016-8867 | known affected: 320 known not affected: 147 recommended: 321 | 2026-07-21T13:49:26+00:00 | Vulnerability · Source |
| CVE-2016-9627 | suse_vex | SUSE CVE CVE-2016-9627 | known affected: 1 recommended: 81 | 2026-07-21T13:49:14+00:00 | Vulnerability · Source |
| CVE-2016-9903 | suse_vex | SUSE CVE CVE-2016-9903 | known affected: 1 recommended: 246 | 2026-07-21T13:49:12+00:00 | Vulnerability · Source |
| CVE-2016-10745 | suse_vex | SUSE CVE CVE-2016-10745 | known affected: 337 recommended: 465 | 2026-07-21T13:49:04+00:00 | Vulnerability · Source |
| CVE-2017-2630 | suse_vex | SUSE CVE CVE-2017-2630 | known affected: 382 known not affected: 152 recommended: 1613 | 2026-07-21T13:48:59+00:00 | Vulnerability · Source |
| CVE-2017-5395 | suse_vex | SUSE CVE CVE-2017-5395 | known affected: 1 known not affected: 32 recommended: 245 | 2026-07-21T13:48:46+00:00 | Vulnerability · Source |
| CVE-2017-5410 | suse_vex | SUSE CVE CVE-2017-5410 | known affected: 1 recommended: 404 | 2026-07-21T13:48:43+00:00 | Vulnerability · Source |
| CVE-2017-5414 | suse_vex | SUSE CVE CVE-2017-5414 | known affected: 1 recommended: 329 | 2026-07-21T13:48:42+00:00 | Vulnerability · Source |
| CVE-2017-7757 | suse_vex | SUSE CVE CVE-2017-7757 | known affected: 2 known not affected: 42 recommended: 451 | 2026-07-21T13:47:49+00:00 | Vulnerability · Source |
| CVE-2017-9023 | suse_vex | SUSE CVE CVE-2017-9023 | known affected: 53 known not affected: 41 recommended: 362 | 2026-07-21T13:47:39+00:00 | Vulnerability · Source |
| CVE-2017-10683 | suse_vex | SUSE CVE CVE-2017-10683 | recommended: 347 | 2026-07-21T13:47:26+00:00 | Vulnerability · Source |
| CVE-2017-11126 | suse_vex | SUSE CVE CVE-2017-11126 | recommended: 347 | 2026-07-21T13:47:24+00:00 | Vulnerability · Source |
| CVE-2017-13047 | suse_vex | SUSE CVE CVE-2017-13047 | known affected: 313 known not affected: 22 recommended: 147 | 2026-07-21T13:46:58+00:00 | Vulnerability · Source |
| CVE-2017-13725 | suse_vex | SUSE CVE CVE-2017-13725 | known affected: 321 known not affected: 22 recommended: 147 | 2026-07-21T13:46:54+00:00 | Vulnerability · Source |
| CVE-2017-1000256 | suse_vex | SUSE CVE CVE-2017-1000256 | known affected: 382 known not affected: 94 recommended: 1803 | 2026-07-21T13:46:33+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-4437 | suse_vex | SUSE CVE CVE-2018-4437 | known affected: 76 recommended: 959 | 2026-07-21T13:46:07+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-5729 | suse_vex | SUSE CVE CVE-2018-5729 | known affected: 392 known not affected: 108 recommended: 673 | 2026-07-21T13:45:55+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-2018-8784 | suse_vex | SUSE CVE CVE-2018-8784 | recommended: 204 | 2026-07-21T13:45:33+00:00 | Vulnerability · Source |
| CVE-2018-10105 | suse_vex | SUSE CVE CVE-2018-10105 | known affected: 292 recommended: 142 | 2026-07-21T13:45:28+00:00 | Vulnerability · Source |
| CVE-2018-10856 | suse_vex | SUSE CVE CVE-2018-10856 | known not affected: 29 recommended: 152 | 2026-07-21T13:45:25+00:00 | Vulnerability · Source |
| CVE-2018-12023 | suse_vex | SUSE CVE CVE-2018-12023 | recommended: 45 | 2026-07-21T13:45:19+00:00 | Vulnerability · Source |
| CVE-2018-12366 | suse_vex | SUSE CVE CVE-2018-12366 | known affected: 21 recommended: 441 | 2026-07-21T13:45:15+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-14718 | suse_vex | SUSE CVE CVE-2018-14718 | recommended: 45 | 2026-07-21T13:34:07+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-2018-20364 | suse_vex | SUSE CVE CVE-2018-20364 | recommended: 127 | 2026-07-21T13:33:30+00:00 | Vulnerability · Source |
| CVE-2019-3836 | suse_vex | SUSE CVE CVE-2019-3836 | known affected: 333 known not affected: 97 recommended: 529 | 2026-07-21T13:33:03+00:00 | Vulnerability · Source |