VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292089 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2023-53191 | suse_vex | SUSE CVE CVE-2023-53191 | known affected: 547 known not affected: 233 recommended: 23 | 2026-07-26T00:06:24+00:00 | Vulnerability · Source |
| CVE-2023-53267 | suse_vex | SUSE CVE CVE-2023-53267 | known not affected: 416 | 2026-07-26T00:06:22+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-53405 | suse_vex | SUSE CVE CVE-2023-53405 | known affected: 344 known not affected: 304 recommended: 206 | 2026-07-26T00:06:18+00:00 | Vulnerability · Source |
| CVE-2023-53406 | suse_vex | SUSE CVE CVE-2023-53406 | known affected: 401 known not affected: 286 recommended: 206 | 2026-07-26T00:06:16+00:00 | Vulnerability · Source |
| CVE-2023-53445 | suse_vex | SUSE CVE CVE-2023-53445 | known affected: 55 known not affected: 361 | 2026-07-26T00:06:15+00:00 | Vulnerability · Source |
| CVE-2023-53460 | suse_vex | SUSE CVE CVE-2023-53460 | known affected: 163 known not affected: 253 | 2026-07-26T00:06:13+00:00 | Vulnerability · Source |
| CVE-2023-53661 | suse_vex | SUSE CVE CVE-2023-53661 | known not affected: 384 recommended: 49 | 2026-07-26T00:06:10+00:00 | Vulnerability · Source |
| CVE-2023-53675 | suse_vex | SUSE CVE CVE-2023-53675 | known affected: 478 known not affected: 181 recommended: 295 | 2026-07-26T00:06:09+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-2023-53833 | suse_vex | SUSE CVE CVE-2023-53833 | known affected: 374 known not affected: 351 recommended: 116 | 2026-07-26T00:06:04+00:00 | Vulnerability · Source |
| CVE-2023-54009 | suse_vex | SUSE CVE CVE-2023-54009 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-26T00:06:02+00:00 | Vulnerability · Source |
| CVE-2023-54040 | suse_vex | SUSE CVE CVE-2023-54040 | known affected: 354 known not affected: 341 recommended: 245 | 2026-07-26T00:06:00+00:00 | Vulnerability · Source |
| CVE-2023-54151 | suse_vex | SUSE CVE CVE-2023-54151 | known not affected: 453 | 2026-07-26T00:05:58+00:00 | Vulnerability · Source |
| CVE-2023-54206 | suse_vex | SUSE CVE CVE-2023-54206 | known not affected: 453 recommended: 49 | 2026-07-26T00:05:57+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-25584 | suse_vex | SUSE CVE CVE-2024-25584 | known not affected: 399 | 2026-07-26T00:05:42+00:00 | Vulnerability · Source |
| CVE-2024-26942 | suse_vex | SUSE CVE CVE-2024-26942 | known not affected: 330 | 2026-07-26T00:05:34+00:00 | Vulnerability · Source |
| CVE-2024-27039 | suse_vex | SUSE CVE CVE-2024-27039 | known affected: 316 known not affected: 314 recommended: 531 | 2026-07-26T00:05:30+00:00 | Vulnerability · Source |
| CVE-2024-35235 | suse_vex | SUSE CVE CVE-2024-35235 | known affected: 409 recommended: 502 | 2026-07-26T00:05:21+00:00 | Vulnerability · Source |
| CVE-2024-35325 | suse_vex | SUSE CVE CVE-2024-35325 | known not affected: 336 | 2026-07-26T00:05:19+00:00 | Vulnerability · Source |
| CVE-2024-35884 | suse_vex | SUSE CVE CVE-2024-35884 | known affected: 418 known not affected: 181 recommended: 676 | 2026-07-26T00:05:11+00:00 | Vulnerability · Source |
| CVE-2024-35924 | suse_vex | SUSE CVE CVE-2024-35924 | known affected: 315 known not affected: 121 recommended: 695 | 2026-07-26T00:05:08+00:00 | Vulnerability · Source |
| CVE-2024-35939 | suse_vex | SUSE CVE CVE-2024-35939 | known affected: 315 known not affected: 244 recommended: 693 | 2026-07-26T00:05:05+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-2024-38394 | suse_vex | SUSE CVE CVE-2024-38394 | known not affected: 57 recommended: 74 | 2026-07-26T00:04:52+00:00 | Vulnerability · Source |
| CVE-2024-41000 | suse_vex | SUSE CVE CVE-2024-41000 | known affected: 340 known not affected: 231 recommended: 660 | 2026-07-26T00:04:42+00:00 | Vulnerability · Source |
| CVE-2024-42255 | suse_vex | SUSE CVE CVE-2024-42255 | known not affected: 310 | 2026-07-26T00:04:35+00:00 | Vulnerability · Source |
| CVE-2024-46683 | suse_vex | SUSE CVE CVE-2024-46683 | known not affected: 324 recommended: 59 | 2026-07-26T00:04:25+00:00 | Vulnerability · Source |
| CVE-2024-47539 | suse_vex | SUSE CVE CVE-2024-47539 | known affected: 27 known not affected: 16 recommended: 101 | 2026-07-26T00:04:17+00:00 | Vulnerability · Source |
| CVE-2024-47708 | suse_vex | SUSE CVE CVE-2024-47708 | known not affected: 402 recommended: 6 | 2026-07-26T00:04:14+00:00 | Vulnerability · Source |
| CVE-2024-47724 | suse_vex | SUSE CVE CVE-2024-47724 | known not affected: 402 recommended: 65 | 2026-07-26T00:04:12+00:00 | Vulnerability · Source |
| CVE-2024-50303 | suse_vex | SUSE CVE CVE-2024-50303 | known not affected: 372 | 2026-07-26T00:04:04+00:00 | Vulnerability · Source |
| CVE-2024-53065 | suse_vex | SUSE CVE CVE-2024-53065 | known not affected: 372 | 2026-07-26T00:03:57+00:00 | Vulnerability · Source |
| CVE-2025-8941 | suse_vex | SUSE CVE CVE-2025-8941 | known not affected: 285 recommended: 7 | 2026-07-26T00:03:34+00:00 | Vulnerability · Source |
| CVE-2025-23050 | suse_vex | SUSE CVE CVE-2025-23050 | known affected: 262 recommended: 49 | 2026-07-26T00:03:17+00:00 | Vulnerability · Source |
| CVE-2025-32913 | suse_vex | SUSE CVE CVE-2025-32913 | known affected: 55 known not affected: 6 recommended: 246 | 2026-07-26T00:03:11+00:00 | Vulnerability · Source |
| CVE-2025-38233 | suse_vex | SUSE CVE CVE-2025-38233 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-26T00:03:05+00:00 | Vulnerability · Source |
| CVE-2025-38421 | suse_vex | SUSE CVE CVE-2025-38421 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-26T00:03:02+00:00 | Vulnerability · Source |
| CVE-2025-38558 | suse_vex | SUSE CVE CVE-2025-38558 | known not affected: 416 | 2026-07-26T00:02:59+00:00 | Vulnerability · Source |
| CVE-2025-38589 | suse_vex | SUSE CVE CVE-2025-38589 | first fixed: 2 known not affected: 431 recommended: 172 | 2026-07-26T00:02:58+00:00 | Vulnerability · Source |
| 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 |