VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294144 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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-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 |
| CVE-2018-18492 | suse_vex | SUSE CVE CVE-2018-18492 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:12+00:00 | Vulnerability · Source |
| CVE-2018-18493 | suse_vex | SUSE CVE CVE-2018-18493 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:10+00:00 | Vulnerability · Source |
| CVE-2018-18505 | suse_vex | SUSE CVE CVE-2018-18505 | known not affected: 154 recommended: 1193 | 2026-07-25T18:12:03+00:00 | Vulnerability · Source |
| CVE-2018-19059 | suse_vex | SUSE CVE CVE-2018-19059 | known affected: 26 known not affected: 324 recommended: 170 | 2026-07-25T18:11:52+00:00 | Vulnerability · Source |
| CVE-2018-19416 | suse_vex | SUSE CVE CVE-2018-19416 | known affected: 405 known not affected: 8 recommended: 137 | 2026-07-25T18:11:41+00:00 | Vulnerability · Source |
| CVE-2018-19876 | suse_vex | SUSE CVE CVE-2018-19876 | known not affected: 149 | 2026-07-25T18:11:13+00:00 | Vulnerability · Source |
| CVE-2018-20185 | suse_vex | SUSE CVE CVE-2018-20185 | known affected: 3 known not affected: 205 recommended: 14 | 2026-07-25T18:10:51+00:00 | Vulnerability · Source |
| CVE-2018-20509 | suse_vex | SUSE CVE CVE-2018-20509 | known not affected: 127 | 2026-07-25T18:10:44+00:00 | Vulnerability · Source |
| CVE-2018-20510 | suse_vex | SUSE CVE CVE-2018-20510 | known not affected: 134 | 2026-07-25T18:10:43+00:00 | Vulnerability · Source |
| CVE-2018-20511 | suse_vex | SUSE CVE CVE-2018-20511 | known not affected: 563 | 2026-07-25T18:10:42+00:00 | Vulnerability · Source |
| CVE-2018-20584 | suse_vex | SUSE CVE CVE-2018-20584 | known not affected: 89 | 2026-07-25T18:10:37+00:00 | Vulnerability · Source |
| CVE-2018-20650 | suse_vex | SUSE CVE CVE-2018-20650 | known affected: 26 known not affected: 324 recommended: 179 | 2026-07-25T18:10:36+00:00 | Vulnerability · Source |
| CVE-2018-20712 | suse_vex | SUSE CVE CVE-2018-20712 | known not affected: 318 | 2026-07-25T18:10:29+00:00 | Vulnerability · Source |
| CVE-2018-20852 | suse_vex | SUSE CVE CVE-2018-20852 | known affected: 459 recommended: 1884 | 2026-07-25T18:10:17+00:00 | Vulnerability · Source |
| CVE-2018-21035 | suse_vex | SUSE CVE CVE-2018-21035 | recommended: 26 | 2026-07-25T18:10:12+00:00 | Vulnerability · Source |
| CVE-2018-25013 | suse_vex | SUSE CVE CVE-2018-25013 | known affected: 395 known not affected: 55 recommended: 227 | 2026-07-25T18:10:08+00:00 | Vulnerability · Source |
| CVE-2018-25015 | suse_vex | SUSE CVE CVE-2018-25015 | known not affected: 320 | 2026-07-25T18:10:07+00:00 | Vulnerability · Source |
| CVE-2018-25091 | suse_vex | SUSE CVE CVE-2018-25091 | known not affected: 147 recommended: 38 | 2026-07-25T18:10:06+00:00 | Vulnerability · Source |
| CVE-2018-1000028 | suse_vex | SUSE CVE CVE-2018-1000028 | known not affected: 142 recommended: 293 | 2026-07-25T18:10:01+00:00 | Vulnerability · Source |
| CVE-2018-1000032 | suse_vex | SUSE CVE CVE-2018-1000032 | known not affected: 14 | 2026-07-25T18:10:00+00:00 | Vulnerability · Source |
| CVE-2018-1000034 | suse_vex | SUSE CVE CVE-2018-1000034 | known not affected: 14 | 2026-07-25T18:09:58+00:00 | Vulnerability · Source |