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-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-2019-14241 | suse_vex | SUSE CVE CVE-2019-14241 | known not affected: 14 recommended: 11 | 2026-07-21T13:31:55+00:00 | Vulnerability · Source |
| CVE-2019-15784 | suse_vex | SUSE CVE CVE-2019-15784 | known not affected: 18 recommended: 57 | 2026-07-21T13:31:42+00:00 | Vulnerability · Source |
| CVE-2020-2875 | suse_vex | SUSE CVE CVE-2020-2875 | recommended: 17 | 2026-07-21T13:31:13+00:00 | Vulnerability · Source |
| CVE-2020-4033 | suse_vex | SUSE CVE CVE-2020-4033 | recommended: 165 | 2026-07-21T13:31:07+00:00 | Vulnerability · Source |
| CVE-2020-11076 | suse_vex | SUSE CVE CVE-2020-11076 | known affected: 374 recommended: 423 | 2026-07-21T13:30:41+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-2020-25649 | suse_vex | SUSE CVE CVE-2020-25649 | known affected: 389 recommended: 270 | 2026-07-21T13:29:47+00:00 | Vulnerability · Source |
| CVE-2020-28473 | suse_vex | SUSE CVE CVE-2020-28473 | recommended: 77 | 2026-07-21T13:29:20+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-27906 | suse_vex | SUSE CVE CVE-2021-27906 | known not affected: 25 recommended: 42 | 2026-07-21T13:28:26+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-30744 | suse_vex | SUSE CVE CVE-2021-30744 | known affected: 1 known not affected: 94 recommended: 1043 | 2026-07-21T13:28:15+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-2021-39240 | suse_vex | SUSE CVE CVE-2021-39240 | known not affected: 15 recommended: 6 | 2026-07-21T13:27:55+00:00 | Vulnerability · Source |
| CVE-2021-43565 | suse_vex | SUSE CVE CVE-2021-43565 | known affected: 350 known not affected: 44 recommended: 531 | 2026-07-21T13:27:47+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-1949 | suse_vex | SUSE CVE CVE-2022-1949 | recommended: 183 | 2026-07-21T13:27:20+00:00 | Vulnerability · Source |
| CVE-2022-3964 | suse_vex | SUSE CVE CVE-2022-3964 | known not affected: 533 recommended: 210 | 2026-07-21T13:27:03+00:00 | Vulnerability · Source |
| CVE-2022-30784 | suse_vex | SUSE CVE CVE-2022-30784 | recommended: 242 | 2026-07-21T13:26:34+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-2022-36055 | suse_vex | SUSE CVE CVE-2022-36055 | known affected: 382 known not affected: 1 recommended: 118 | 2026-07-21T13:26:17+00:00 | Vulnerability · Source |
| CVE-2023-6601 | suse_vex | SUSE CVE CVE-2023-6601 | known affected: 821 known not affected: 19 recommended: 200 | 2026-07-21T13:25:21+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-2023-38403 | suse_vex | SUSE CVE CVE-2023-38403 | recommended: 40 | 2026-07-21T13:24:55+00:00 | Vulnerability · Source |
| CVE-2024-25621 | suse_vex | SUSE CVE CVE-2024-25621 | known affected: 366 recommended: 130 | 2026-07-21T13:23:32+00:00 | Vulnerability · Source |
| CVE-2024-53150 | suse_vex | SUSE CVE CVE-2024-53150 | known affected: 576 known not affected: 70 recommended: 549 | 2026-07-21T13:21:51+00:00 | Vulnerability · Source |
| CVE-2025-38153 | suse_vex | SUSE CVE CVE-2025-38153 | first fixed: 2 known affected: 398 known not affected: 296 recommended: 531 | 2026-07-21T13:20:29+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-12080 | suse_vex | SUSE CVE CVE-2026-12080 | known affected: 867 known not affected: 212 | 2026-07-21T13:17:32+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-16221 | suse_vex | SUSE CVE CVE-2026-16221 | known affected: 75 known not affected: 41 | 2026-07-21T13:16:59+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 |
| CVE-2026-25990 | suse_vex | SUSE CVE CVE-2026-25990 | known not affected: 54 recommended: 12 | 2026-07-21T13:16:12+00:00 | Vulnerability · Source |
| CVE-2026-26080 | suse_vex | SUSE CVE CVE-2026-26080 | known not affected: 11 recommended: 4 | 2026-07-21T13:16:03+00:00 | Vulnerability · Source |
| CVE-2026-26081 | suse_vex | SUSE CVE CVE-2026-26081 | known not affected: 11 recommended: 5 | 2026-07-21T13:16:01+00:00 | Vulnerability · Source |
| CVE-2026-26197 | suse_vex | SUSE CVE CVE-2026-26197 | known not affected: 707 | 2026-07-21T13:15:59+00:00 | Vulnerability · Source |