VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-39909 | suse_vex | SUSE CVE CVE-2025-39909 | first fixed: 2 known not affected: 410 recommended: 154 | 2026-07-26T00:02:53+00:00 | Vulnerability · Source |
| CVE-2025-40126 | suse_vex | SUSE CVE CVE-2025-40126 | known not affected: 437 | 2026-07-26T00:02:49+00:00 | Vulnerability · Source |
| CVE-2025-43529 | suse_vex | SUSE CVE CVE-2025-43529 | known affected: 133 recommended: 624 | 2026-07-26T00:02:46+00:00 | Vulnerability · Source |
| CVE-2025-68216 | suse_vex | SUSE CVE CVE-2025-68216 | known not affected: 418 | 2026-07-26T00:02:41+00:00 | Vulnerability · Source |
| CVE-2025-68338 | suse_vex | SUSE CVE CVE-2025-68338 | known not affected: 453 | 2026-07-26T00:02:39+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-2025-71303 | suse_vex | SUSE CVE CVE-2025-71303 | known not affected: 293 | 2026-07-25T18:29:45+00:00 | Vulnerability · Source |
| CVE-2018-14354 | suse_vex | SUSE CVE CVE-2018-14354 | known affected: 29 recommended: 201 | 2026-07-25T18:14:51+00:00 | Vulnerability · Source |
| CVE-2018-14359 | suse_vex | SUSE CVE CVE-2018-14359 | known affected: 29 recommended: 200 | 2026-07-25T18:14:49+00:00 | Vulnerability · Source |
| CVE-2018-14369 | suse_vex | SUSE CVE CVE-2018-14369 | known affected: 118 recommended: 1022 | 2026-07-25T18:14:44+00:00 | Vulnerability · Source |
| CVE-2018-14370 | suse_vex | SUSE CVE CVE-2018-14370 | known affected: 118 recommended: 1022 | 2026-07-25T18:14:43+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-14404 | suse_vex | SUSE CVE CVE-2018-14404 | known affected: 417 known not affected: 80 recommended: 709 | 2026-07-25T18:14:40+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-14617 | suse_vex | SUSE CVE CVE-2018-14617 | known not affected: 193 recommended: 738 | 2026-07-25T18:14:24+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-14634 | suse_vex | SUSE CVE CVE-2018-14634 | known affected: 6 known not affected: 256 recommended: 239 | 2026-07-25T18:14:18+00:00 | Vulnerability · Source |
| CVE-2018-14678 | suse_vex | SUSE CVE CVE-2018-14678 | known not affected: 259 recommended: 84 | 2026-07-25T18:14:17+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-14779 | suse_vex | SUSE CVE CVE-2018-14779 | known not affected: 103 recommended: 323 | 2026-07-25T18:14:12+00:00 | Vulnerability · Source |
| CVE-2018-14780 | suse_vex | SUSE CVE CVE-2018-14780 | known not affected: 103 recommended: 323 | 2026-07-25T18:14:10+00:00 | Vulnerability · Source |
| CVE-2018-15470 | suse_vex | SUSE CVE CVE-2018-15470 | known affected: 320 known not affected: 97 recommended: 425 | 2026-07-25T18:14:07+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-15664 | suse_vex | SUSE CVE CVE-2018-15664 | known affected: 320 recommended: 647 | 2026-07-25T18:14:03+00:00 | Vulnerability · Source |
| CVE-2018-15863 | suse_vex | SUSE CVE CVE-2018-15863 | known affected: 565 known not affected: 65 recommended: 429 | 2026-07-25T18:13:56+00:00 | Vulnerability · Source |
| CVE-2018-16058 | suse_vex | SUSE CVE CVE-2018-16058 | known affected: 118 recommended: 1022 | 2026-07-25T18:13:53+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-16335 | suse_vex | SUSE CVE CVE-2018-16335 | known affected: 459 recommended: 290 | 2026-07-25T18:13:44+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-16376 | suse_vex | SUSE CVE CVE-2018-16376 | recommended: 330 | 2026-07-25T18:13:42+00:00 | Vulnerability · Source |
| CVE-2018-16392 | suse_vex | SUSE CVE CVE-2018-16392 | known affected: 16 known not affected: 19 recommended: 106 | 2026-07-25T18:13:40+00:00 | Vulnerability · Source |
| CVE-2018-16402 | suse_vex | SUSE CVE CVE-2018-16402 | known affected: 386 known not affected: 144 recommended: 670 | 2026-07-25T18:13:37+00:00 | Vulnerability · Source |
| CVE-2018-16420 | suse_vex | SUSE CVE CVE-2018-16420 | known affected: 15 known not affected: 37 recommended: 82 | 2026-07-25T18:13:34+00:00 | Vulnerability · Source |
| CVE-2018-16422 | suse_vex | SUSE CVE CVE-2018-16422 | known affected: 16 known not affected: 19 recommended: 106 | 2026-07-25T18:13:33+00:00 | Vulnerability · Source |
| CVE-2018-16426 | suse_vex | SUSE CVE CVE-2018-16426 | known affected: 15 known not affected: 37 recommended: 82 | 2026-07-25T18:13:29+00:00 | Vulnerability · Source |
| CVE-2018-16428 | suse_vex | SUSE CVE CVE-2018-16428 | known affected: 321 known not affected: 428 recommended: 1197 | 2026-07-25T18:13:28+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-16539 | suse_vex | SUSE CVE CVE-2018-16539 | known affected: 1 known not affected: 8 recommended: 370 | 2026-07-25T18:13:21+00:00 | Vulnerability · Source |
| CVE-2018-16643 | suse_vex | SUSE CVE CVE-2018-16643 | known affected: 95 recommended: 736 | 2026-07-25T18:13:15+00:00 | Vulnerability · Source |
| CVE-2018-16644 | suse_vex | SUSE CVE CVE-2018-16644 | recommended: 824 | 2026-07-25T18:13:14+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-16646 | suse_vex | SUSE CVE CVE-2018-16646 | known affected: 8 known not affected: 386 recommended: 170 | 2026-07-25T18:13:11+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-16745 | suse_vex | SUSE CVE CVE-2018-16745 | known affected: 12 recommended: 150 | 2026-07-25T18:13:08+00:00 | Vulnerability · Source |
| CVE-2018-16844 | suse_vex | SUSE CVE CVE-2018-16844 | known affected: 11 known not affected: 2 recommended: 85 | 2026-07-25T18:13:05+00:00 | Vulnerability · Source |
| CVE-2018-16857 | suse_vex | SUSE CVE CVE-2018-16857 | known affected: 320 known not affected: 1544 recommended: 2761 | 2026-07-25T18:13:02+00:00 | Vulnerability · Source |