VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-11508 | suse_vex | SUSE CVE CVE-2018-11508 | known not affected: 144 | 2026-08-01T00:19:42+00:00 | Vulnerability · Source |
| CVE-2018-13033 | suse_vex | SUSE CVE CVE-2018-13033 | recommended: 2 | 2026-08-01T00:19:39+00:00 | Vulnerability · Source |
| CVE-2018-18066 | suse_vex | SUSE CVE CVE-2018-18066 | known not affected: 297 recommended: 9 | 2026-08-01T00:19:27+00:00 | Vulnerability · Source |
| CVE-2018-18751 | suse_vex | SUSE CVE CVE-2018-18751 | known affected: 433 known not affected: 139 recommended: 98 | 2026-08-01T00:19:23+00:00 | Vulnerability · Source |
| CVE-2018-19591 | suse_vex | SUSE CVE CVE-2018-19591 | known not affected: 498 recommended: 216 | 2026-08-01T00:19:19+00:00 | Vulnerability · Source |
| CVE-2018-19636 | suse_vex | SUSE CVE CVE-2018-19636 | known not affected: 5 recommended: 43 | 2026-08-01T00:19:17+00:00 | Vulnerability · Source |
| CVE-2018-19870 | suse_vex | SUSE CVE CVE-2018-19870 | known affected: 36 known not affected: 1727 recommended: 1076 | 2026-08-01T00:19:15+00:00 | Vulnerability · Source |
| CVE-2018-19964 | suse_vex | SUSE CVE CVE-2018-19964 | known affected: 320 known not affected: 176 recommended: 369 | 2026-08-01T00:19:13+00:00 | Vulnerability · Source |
| CVE-2018-1000030 | suse_vex | SUSE CVE CVE-2018-1000030 | known affected: 465 known not affected: 123 recommended: 537 | 2026-08-01T00:19:04+00:00 | Vulnerability · Source |
| CVE-2019-1798 | suse_vex | SUSE CVE CVE-2019-1798 | known affected: 21 known not affected: 40 recommended: 242 | 2026-08-01T00:19:01+00:00 | Vulnerability · Source |
| CVE-2019-2213 | suse_vex | SUSE CVE CVE-2019-2213 | known not affected: 208 | 2026-08-01T00:18:59+00:00 | Vulnerability · Source |
| CVE-2019-2988 | suse_vex | SUSE CVE CVE-2019-2988 | known affected: 525 recommended: 1008 | 2026-08-01T00:18:54+00:00 | Vulnerability · Source |
| CVE-2019-2989 | suse_vex | SUSE CVE CVE-2019-2989 | known affected: 525 recommended: 1129 | 2026-08-01T00:18:53+00:00 | Vulnerability · Source |
| CVE-2019-3815 | suse_vex | SUSE CVE CVE-2019-3815 | known not affected: 242 recommended: 10 | 2026-08-01T00:18:51+00:00 | Vulnerability · Source |
| CVE-2019-3882 | suse_vex | SUSE CVE CVE-2019-3882 | known not affected: 102 recommended: 835 | 2026-08-01T00:18:47+00:00 | Vulnerability · Source |
| CVE-2019-12615 | suse_vex | SUSE CVE CVE-2019-12615 | known not affected: 206 | 2026-08-01T00:18:24+00:00 | Vulnerability · Source |
| CVE-2019-13012 | suse_vex | SUSE CVE CVE-2019-13012 | known affected: 66 known not affected: 5 recommended: 554 | 2026-08-01T00:18:20+00:00 | Vulnerability · Source |
| CVE-2019-1010189 | suse_vex | SUSE CVE CVE-2019-1010189 | known not affected: 64 | 2026-08-01T00:18:05+00:00 | Vulnerability · Source |
| CVE-2020-25678 | suse_vex | SUSE CVE CVE-2020-25678 | known affected: 64 known not affected: 1024 recommended: 1045 | 2026-08-01T00:17:51+00:00 | Vulnerability · Source |
| CVE-2020-25969 | suse_vex | SUSE CVE CVE-2020-25969 | known affected: 15 known not affected: 54 recommended: 5 | 2026-08-01T00:17:49+00:00 | Vulnerability · Source |
| CVE-2021-22897 | suse_vex | SUSE CVE CVE-2021-22897 | known not affected: 144 | 2026-08-01T00:17:31+00:00 | Vulnerability · Source |
| CVE-2022-49862 | suse_vex | SUSE CVE CVE-2022-49862 | known affected: 551 known not affected: 214 recommended: 70 | 2026-08-01T00:16:26+00:00 | Vulnerability · Source |
| CVE-2023-50229 | suse_vex | SUSE CVE CVE-2023-50229 | known affected: 65 known not affected: 32 recommended: 112 | 2026-08-01T00:15:51+00:00 | Vulnerability · Source |
| CVE-2026-0861 | suse_vex | SUSE CVE CVE-2026-0861 | first fixed: 1 known affected: 380 known not affected: 198 recommended: 892 | 2026-08-01T00:12:24+00:00 | Vulnerability · Source |
| CVE-2026-0915 | suse_vex | SUSE CVE CVE-2026-0915 | first fixed: 1 known affected: 492 recommended: 999 | 2026-08-01T00:12:22+00:00 | Vulnerability · Source |
| CVE-2026-5958 | suse_vex | SUSE CVE CVE-2026-5958 | known affected: 396 recommended: 75 | 2026-08-01T00:12:03+00:00 | Vulnerability · Source |
| CVE-2026-22795 | suse_vex | SUSE CVE CVE-2026-22795 | known affected: 406 known not affected: 251 recommended: 329 | 2026-08-01T00:10:27+00:00 | Vulnerability · Source |
| CVE-2026-22796 | suse_vex | SUSE CVE CVE-2026-22796 | known affected: 494 known not affected: 96 recommended: 391 | 2026-08-01T00:10:26+00:00 | Vulnerability · Source |
| CVE-2026-31790 | suse_vex | SUSE CVE CVE-2026-31790 | known affected: 394 known not affected: 373 recommended: 314 | 2026-08-01T00:08:57+00:00 | Vulnerability · Source |
| CVE-2026-34183 | suse_vex | SUSE CVE CVE-2026-34183 | known affected: 413 known not affected: 443 recommended: 80 | 2026-08-01T00:08:46+00:00 | Vulnerability · Source |
| CVE-2026-51296 | suse_vex | SUSE CVE CVE-2026-51296 | No product status | 2026-08-01T00:06:41+00:00 | Vulnerability · Source |
| CVE-2026-51297 | suse_vex | SUSE CVE CVE-2026-51297 | No product status | 2026-08-01T00:06:40+00:00 | Vulnerability · Source |
| CVE-2026-51298 | suse_vex | SUSE CVE CVE-2026-51298 | No product status | 2026-08-01T00:06:38+00:00 | Vulnerability · Source |
| CVE-2026-51300 | suse_vex | SUSE CVE CVE-2026-51300 | No product status | 2026-08-01T00:06:36+00:00 | Vulnerability · Source |
| CVE-2026-51302 | suse_vex | SUSE CVE CVE-2026-51302 | No product status | 2026-08-01T00:06:34+00:00 | Vulnerability · Source |
| CVE-2026-51303 | suse_vex | SUSE CVE CVE-2026-51303 | No product status | 2026-08-01T00:06:32+00:00 | Vulnerability · Source |
| CVE-2026-51304 | suse_vex | SUSE CVE CVE-2026-51304 | No product status | 2026-08-01T00:06:31+00:00 | Vulnerability · Source |
| CVE-2026-54706 | suse_vex | SUSE CVE CVE-2026-54706 | recommended: 1 | 2026-08-01T00:06:08+00:00 | Vulnerability · Source |
| CVE-2026-54707 | suse_vex | SUSE CVE CVE-2026-54707 | recommended: 1 | 2026-08-01T00:06:07+00:00 | Vulnerability · Source |
| CVE-2026-54715 | suse_vex | SUSE CVE CVE-2026-54715 | No product status | 2026-08-01T00:06:06+00:00 | Vulnerability · Source |
| CVE-2026-55768 | suse_vex | SUSE CVE CVE-2026-55768 | No product status | 2026-08-01T00:05:59+00:00 | Vulnerability · Source |
| CVE-2026-55777 | suse_vex | SUSE CVE CVE-2026-55777 | No product status | 2026-08-01T00:05:57+00:00 | Vulnerability · Source |
| CVE-2026-58402 | suse_vex | SUSE CVE CVE-2026-58402 | No product status | 2026-08-01T00:05:47+00:00 | Vulnerability · Source |
| CVE-2026-58403 | suse_vex | SUSE CVE CVE-2026-58403 | No product status | 2026-08-01T00:05:46+00:00 | Vulnerability · Source |
| CVE-2026-58404 | suse_vex | SUSE CVE CVE-2026-58404 | No product status | 2026-08-01T00:05:44+00:00 | Vulnerability · Source |
| CVE-2026-64620 | suse_vex | SUSE CVE CVE-2026-64620 | known affected: 140 | 2026-08-01T00:05:23+00:00 | Vulnerability · Source |
| CVE-2026-64621 | suse_vex | SUSE CVE CVE-2026-64621 | known affected: 93 known not affected: 47 | 2026-08-01T00:05:22+00:00 | Vulnerability · Source |
| CVE-2026-66337 | suse_vex | SUSE CVE CVE-2026-66337 | known affected: 238 | 2026-08-01T00:05:18+00:00 | Vulnerability · Source |
| CVE-2026-66338 | suse_vex | SUSE CVE CVE-2026-66338 | known affected: 238 | 2026-08-01T00:05:16+00:00 | Vulnerability · Source |
| CVE-2026-66339 | suse_vex | SUSE CVE CVE-2026-66339 | known affected: 238 | 2026-08-01T00:05:15+00:00 | Vulnerability · Source |