VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-0089 | suse_vex | SUSE CVE CVE-2021-0089 | known affected: 312 known not affected: 46 recommended: 503 | 2026-07-26T00:13:07+00:00 | Vulnerability · Source |
| CVE-2021-3927 | suse_vex | SUSE CVE CVE-2021-3927 | known affected: 352 recommended: 384 | 2026-07-26T00:12:49+00:00 | Vulnerability · Source |
| CVE-2021-3947 | suse_vex | SUSE CVE CVE-2021-3947 | known not affected: 1077 | 2026-07-26T00:12:47+00:00 | Vulnerability · Source |
| CVE-2021-23983 | suse_vex | SUSE CVE CVE-2021-23983 | recommended: 9 | 2026-07-26T00:12:33+00:00 | Vulnerability · Source |
| CVE-2021-47010 | suse_vex | SUSE CVE CVE-2021-47010 | known not affected: 292 | 2026-07-26T00:12:05+00:00 | Vulnerability · Source |
| CVE-2021-47241 | suse_vex | SUSE CVE CVE-2021-47241 | known affected: 388 known not affected: 294 recommended: 91 | 2026-07-26T00:11:54+00:00 | Vulnerability · Source |
| CVE-2022-23131 | suse_vex | SUSE CVE CVE-2022-23131 | known not affected: 37 | 2026-07-26T00:10:58+00:00 | Vulnerability · Source |
| CVE-2022-28391 | suse_vex | SUSE CVE CVE-2022-28391 | known affected: 5 known not affected: 63 | 2026-07-26T00:10:47+00:00 | Vulnerability · Source |
| CVE-2022-38349 | suse_vex | SUSE CVE CVE-2022-38349 | known affected: 80 known not affected: 5 recommended: 273 | 2026-07-26T00:10:31+00:00 | Vulnerability · Source |
| CVE-2022-47521 | suse_vex | SUSE CVE CVE-2022-47521 | known not affected: 362 | 2026-07-26T00:10:17+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 310 | 2026-07-26T00:10:01+00:00 | Vulnerability · Source |
| CVE-2022-49536 | suse_vex | SUSE CVE CVE-2022-49536 | known affected: 385 known not affected: 193 recommended: 361 | 2026-07-26T00:09:12+00:00 | Vulnerability · Source |
| CVE-2022-50132 | suse_vex | SUSE CVE CVE-2022-50132 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-26T00:08:36+00:00 | Vulnerability · Source |
| CVE-2022-50278 | suse_vex | SUSE CVE CVE-2022-50278 | known affected: 468 known not affected: 181 recommended: 243 | 2026-07-26T00:08:23+00:00 | Vulnerability · Source |
| CVE-2023-6247 | suse_vex | SUSE CVE CVE-2023-6247 | known not affected: 102 | 2026-07-26T00:07:28+00:00 | Vulnerability · Source |
| CVE-2023-25750 | suse_vex | SUSE CVE CVE-2023-25750 | known affected: 1 recommended: 214 | 2026-07-26T00:07:18+00:00 | Vulnerability · Source |
| CVE-2023-26606 | suse_vex | SUSE CVE CVE-2023-26606 | known not affected: 284 | 2026-07-26T00:07:17+00:00 | Vulnerability · Source |
| CVE-2023-32636 | suse_vex | SUSE CVE CVE-2023-32636 | known not affected: 598 recommended: 64 | 2026-07-26T00:07:11+00:00 | Vulnerability · Source |
| CVE-2023-33850 | suse_vex | SUSE CVE CVE-2023-33850 | known affected: 394 recommended: 125 | 2026-07-26T00:07:08+00:00 | Vulnerability · Source |
| CVE-2023-34981 | suse_vex | SUSE CVE CVE-2023-34981 | known not affected: 333 | 2026-07-26T00:07:06+00:00 | Vulnerability · Source |
| CVE-2023-40481 | suse_vex | SUSE CVE CVE-2023-40481 | known not affected: 79 | 2026-07-26T00:07:02+00:00 | Vulnerability · Source |
| CVE-2023-52779 | suse_vex | SUSE CVE CVE-2023-52779 | known not affected: 330 | 2026-07-26T00:06:44+00:00 | Vulnerability · Source |
| CVE-2023-52907 | suse_vex | SUSE CVE CVE-2023-52907 | known affected: 425 known not affected: 76 recommended: 495 | 2026-07-26T00:06:34+00:00 | Vulnerability · Source |
| CVE-2023-53295 | suse_vex | SUSE CVE CVE-2023-53295 | known affected: 462 known not affected: 187 recommended: 243 | 2026-07-26T00:06:20+00:00 | Vulnerability · Source |
| CVE-2023-53796 | suse_vex | SUSE CVE CVE-2023-53796 | known not affected: 448 | 2026-07-26T00:06:07+00:00 | Vulnerability · Source |
| CVE-2023-53824 | suse_vex | SUSE CVE CVE-2023-53824 | known affected: 228 known not affected: 188 | 2026-07-26T00:06:05+00:00 | Vulnerability · Source |
| CVE-2024-0584 | suse_vex | SUSE CVE CVE-2024-0584 | known not affected: 362 | 2026-07-26T00:05:54+00:00 | Vulnerability · Source |
| CVE-2024-36462 | suse_vex | SUSE CVE CVE-2024-36462 | known not affected: 11 | 2026-07-26T00:05:00+00:00 | Vulnerability · Source |
| CVE-2026-27893 | redhat_vex | vllm: vLLM: Remote code execution due to hardcoded trust_remote_code setting | fixed: 25 known affected: 6 known not affected: 881 | 2026-07-25T21:49:35+00:00 | Vulnerability · Source |
| CVE-2018-14400 | suse_vex | SUSE CVE CVE-2018-14400 | known affected: 21 | 2026-07-25T18:14:41+00:00 | Vulnerability · Source |
| CVE-2018-14609 | suse_vex | SUSE CVE CVE-2018-14609 | known affected: 7 known not affected: 417 | 2026-07-25T18:14:30+00:00 | Vulnerability · Source |
| CVE-2018-14611 | suse_vex | SUSE CVE CVE-2018-14611 | known affected: 7 known not affected: 415 | 2026-07-25T18:14:28+00:00 | Vulnerability · Source |
| CVE-2018-14612 | suse_vex | SUSE CVE CVE-2018-14612 | known affected: 7 known not affected: 379 | 2026-07-25T18:14:27+00:00 | Vulnerability · Source |
| CVE-2018-14613 | suse_vex | SUSE CVE CVE-2018-14613 | known affected: 7 known not affected: 415 recommended: 472 | 2026-07-25T18:14:26+00:00 | Vulnerability · Source |
| CVE-2018-14619 | suse_vex | SUSE CVE CVE-2018-14619 | known not affected: 193 | 2026-07-25T18:14:23+00:00 | Vulnerability · Source |
| CVE-2018-14621 | suse_vex | SUSE CVE CVE-2018-14621 | known not affected: 52 recommended: 8 | 2026-07-25T18:14:21+00:00 | Vulnerability · Source |
| CVE-2018-14734 | suse_vex | SUSE CVE CVE-2018-14734 | known affected: 74 known not affected: 184 recommended: 445 | 2026-07-25T18:14:13+00:00 | Vulnerability · Source |
| CVE-2018-15471 | suse_vex | SUSE CVE CVE-2018-15471 | known affected: 4 known not affected: 43 recommended: 32 | 2026-07-25T18:14:06+00:00 | Vulnerability · Source |
| CVE-2018-16228 | suse_vex | SUSE CVE CVE-2018-16228 | known affected: 333 recommended: 141 | 2026-07-25T18:13:49+00:00 | Vulnerability · Source |
| CVE-2018-16369 | suse_vex | SUSE CVE CVE-2018-16369 | known not affected: 381 | 2026-07-25T18:13:43+00:00 | Vulnerability · Source |
| CVE-2018-16451 | suse_vex | SUSE CVE CVE-2018-16451 | known affected: 333 recommended: 145 | 2026-07-25T18:13:24+00:00 | Vulnerability · Source |
| CVE-2018-16645 | suse_vex | SUSE CVE CVE-2018-16645 | known affected: 95 recommended: 752 | 2026-07-25T18:13:12+00:00 | Vulnerability · Source |
| CVE-2018-16743 | suse_vex | SUSE CVE CVE-2018-16743 | known affected: 12 recommended: 153 | 2026-07-25T18:13:10+00:00 | Vulnerability · Source |
| CVE-2018-16866 | suse_vex | SUSE CVE CVE-2018-16866 | known not affected: 224 recommended: 575 | 2026-07-25T18:12:59+00:00 | Vulnerability · Source |
| CVE-2018-16868 | suse_vex | SUSE CVE CVE-2018-16868 | known affected: 320 recommended: 454 | 2026-07-25T18:12:57+00:00 | Vulnerability · Source |
| CVE-2018-16883 | suse_vex | SUSE CVE CVE-2018-16883 | known not affected: 167 | 2026-07-25T18:12:51+00:00 | Vulnerability · Source |
| CVE-2018-17199 | suse_vex | SUSE CVE CVE-2018-17199 | known affected: 111 known not affected: 40 recommended: 190 | 2026-07-25T18:12:45+00:00 | Vulnerability · Source |
| CVE-2018-17407 | suse_vex | SUSE CVE CVE-2018-17407 | known affected: 30 known not affected: 72 recommended: 13119 | 2026-07-25T18:12:33+00:00 | Vulnerability · Source |
| CVE-2018-17967 | suse_vex | SUSE CVE CVE-2018-17967 | known not affected: 176 recommended: 17 | 2026-07-25T18:12:31+00:00 | Vulnerability · Source |
| CVE-2018-18025 | suse_vex | SUSE CVE CVE-2018-18025 | known not affected: 176 | 2026-07-25T18:12:30+00:00 | Vulnerability · Source |