VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292115 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-38368 | suse_vex | SUSE CVE CVE-2025-38368 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T16:50:54+00:00 | Vulnerability · Source |
| CVE-2025-38381 | suse_vex | SUSE CVE CVE-2025-38381 | first fixed: 2 known not affected: 416 recommended: 154 | 2026-07-25T16:50:52+00:00 | Vulnerability · Source |
| CVE-2025-38508 | suse_vex | SUSE CVE CVE-2025-38508 | first fixed: 2 known affected: 5 known not affected: 448 recommended: 154 | 2026-07-25T16:50:49+00:00 | Vulnerability · Source |
| CVE-2025-38598 | suse_vex | SUSE CVE CVE-2025-38598 | known not affected: 416 | 2026-07-25T16:50:47+00:00 | Vulnerability · Source |
| CVE-2025-38711 | suse_vex | SUSE CVE CVE-2025-38711 | known not affected: 416 | 2026-07-25T16:50:45+00:00 | Vulnerability · Source |
| CVE-2025-38723 | suse_vex | SUSE CVE CVE-2025-38723 | known affected: 196 known not affected: 205 | 2026-07-25T16:50:43+00:00 | Vulnerability · Source |
| CVE-2025-39712 | suse_vex | SUSE CVE CVE-2025-39712 | first fixed: 2 known affected: 57 known not affected: 353 recommended: 154 | 2026-07-25T16:50:42+00:00 | Vulnerability · Source |
| CVE-2025-39734 | suse_vex | SUSE CVE CVE-2025-39734 | known not affected: 416 | 2026-07-25T16:50:40+00:00 | Vulnerability · Source |
| CVE-2025-39736 | suse_vex | SUSE CVE CVE-2025-39736 | known not affected: 453 | 2026-07-25T16:50:39+00:00 | Vulnerability · Source |
| CVE-2025-39745 | suse_vex | SUSE CVE CVE-2025-39745 | known affected: 24 known not affected: 433 | 2026-07-25T16:50:37+00:00 | Vulnerability · Source |
| CVE-2025-39755 | suse_vex | SUSE CVE CVE-2025-39755 | known not affected: 348 | 2026-07-25T16:50:36+00:00 | Vulnerability · Source |
| CVE-2025-40050 | suse_vex | SUSE CVE CVE-2025-40050 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:27+00:00 | Vulnerability · Source |
| CVE-2025-40068 | suse_vex | SUSE CVE CVE-2025-40068 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:26+00:00 | Vulnerability · Source |
| CVE-2025-40084 | suse_vex | SUSE CVE CVE-2025-40084 | known not affected: 407 recommended: 6 | 2026-07-25T16:50:24+00:00 | Vulnerability · Source |
| CVE-2025-40093 | suse_vex | SUSE CVE CVE-2025-40093 | known affected: 26 known not affected: 403 recommended: 6 | 2026-07-25T16:50:23+00:00 | Vulnerability · Source |
| CVE-2025-40161 | suse_vex | SUSE CVE CVE-2025-40161 | first fixed: 2 known not affected: 405 recommended: 154 | 2026-07-25T16:50:21+00:00 | Vulnerability · Source |
| CVE-2025-40182 | suse_vex | SUSE CVE CVE-2025-40182 | known not affected: 408 | 2026-07-25T16:50:19+00:00 | Vulnerability · Source |
| CVE-2025-40295 | suse_vex | SUSE CVE CVE-2025-40295 | known not affected: 414 | 2026-07-25T16:50:17+00:00 | Vulnerability · Source |
| CVE-2025-40354 | suse_vex | SUSE CVE CVE-2025-40354 | first fixed: 2 known affected: 394 known not affected: 372 recommended: 283 | 2026-07-25T16:50:15+00:00 | Vulnerability · Source |
| CVE-2025-43265 | suse_vex | SUSE CVE CVE-2025-43265 | known affected: 99 known not affected: 52 recommended: 592 | 2026-07-25T16:50:13+00:00 | Vulnerability · Source |
| CVE-2025-43531 | suse_vex | SUSE CVE CVE-2025-43531 | known affected: 133 recommended: 624 | 2026-07-25T16:50:11+00:00 | Vulnerability · Source |
| CVE-2025-43921 | suse_vex | SUSE CVE CVE-2025-43921 | known not affected: 10 | 2026-07-25T16:50:10+00:00 | Vulnerability · Source |
| CVE-2025-49812 | suse_vex | SUSE CVE CVE-2025-49812 | known affected: 474 recommended: 310 | 2026-07-25T16:50:03+00:00 | Vulnerability · Source |
| CVE-2025-68298 | suse_vex | SUSE CVE CVE-2025-68298 | first fixed: 2 known affected: 394 known not affected: 358 recommended: 283 | 2026-07-25T16:49:53+00:00 | Vulnerability · Source |
| CVE-2025-71122 | suse_vex | SUSE CVE CVE-2025-71122 | known not affected: 340 | 2026-07-25T16:48:42+00:00 | Vulnerability · Source |
| CVE-2025-71141 | suse_vex | SUSE CVE CVE-2025-71141 | first fixed: 2 known affected: 453 known not affected: 205 recommended: 283 | 2026-07-25T16:48:40+00:00 | Vulnerability · Source |
| CVE-2026-12547 | suse_vex | SUSE CVE CVE-2026-12547 | known affected: 238 | 2026-07-25T16:48:33+00:00 | Vulnerability · Source |
| CVE-2026-63878 | suse_vex | SUSE CVE CVE-2026-63878 | known not affected: 298 | 2026-07-25T16:47:52+00:00 | Vulnerability · Source |
| CVE-2025-41244 | microsoft_vex | VMSA-2025-0015: VMware Aria Operations and VMware Tools updates address multiple vulnerabilities (CVE-2025-41244,CVE-2025-41245, CVE-2025-41246) | fixed: 1 known affected: 1 | 2026-07-25T14:40:29+00:00 | Vulnerability · Source |
| CVE-2026-5223 | redhat_vex | cargo: Cargo: Source code overwrite due to symlink mishandling in third-party registries | fixed: 4 known affected: 19 | 2026-07-25T03:03:03+00:00 | Vulnerability · Source |
| CVE-2026-63818 | redhat_vex | kernel: f2fs: validate orphan inode entry count | known not affected: 274 | 2026-07-25T03:02:57+00:00 | Vulnerability · Source |
| CVE-2026-65703 | redhat_vex | FFmpeg: FFmpeg: Arbitrary code execution via crafted AVI file in TDSC video decoder | known affected: 8 | 2026-07-25T03:02:55+00:00 | Vulnerability · Source |
| CVE-2026-64831 | redhat_vex | ffmpeg: FFmpeg: Arbitrary code execution via crafted HEVC/H.265 bitstream | known not affected: 8 | 2026-07-25T03:02:52+00:00 | Vulnerability · Source |
| CVE-2023-1161 | suse_vex | SUSE CVE CVE-2023-1161 | known affected: 144 known not affected: 74 recommended: 168 | 2026-07-25T02:47:23+00:00 | Vulnerability · Source |
| CVE-2023-1170 | suse_vex | SUSE CVE CVE-2023-1170 | known affected: 286 recommended: 391 | 2026-07-25T02:47:21+00:00 | Vulnerability · Source |
| CVE-2023-1195 | suse_vex | SUSE CVE CVE-2023-1195 | known not affected: 288 recommended: 70 | 2026-07-25T02:47:14+00:00 | Vulnerability · Source |
| CVE-2023-1252 | suse_vex | SUSE CVE CVE-2023-1252 | known not affected: 288 recommended: 49 | 2026-07-25T02:47:10+00:00 | Vulnerability · Source |
| CVE-2023-1355 | suse_vex | SUSE CVE CVE-2023-1355 | known affected: 387 known not affected: 27 recommended: 325 | 2026-07-25T02:47:05+00:00 | Vulnerability · Source |
| CVE-2023-1386 | suse_vex | SUSE CVE CVE-2023-1386 | known not affected: 829 | 2026-07-25T02:47:03+00:00 | Vulnerability · Source |
| CVE-2023-1916 | suse_vex | SUSE CVE CVE-2023-1916 | known affected: 436 known not affected: 1 recommended: 138 | 2026-07-25T02:46:42+00:00 | Vulnerability · Source |
| CVE-2023-2491 | suse_vex | SUSE CVE CVE-2023-2491 | known not affected: 334 recommended: 11 | 2026-07-25T02:46:19+00:00 | Vulnerability · Source |
| CVE-2023-2598 | suse_vex | SUSE CVE CVE-2023-2598 | known not affected: 327 | 2026-07-25T02:46:16+00:00 | Vulnerability · Source |
| CVE-2023-2612 | suse_vex | SUSE CVE CVE-2023-2612 | known not affected: 389 | 2026-07-25T02:46:11+00:00 | Vulnerability · Source |
| CVE-2023-2662 | suse_vex | SUSE CVE CVE-2023-2662 | known not affected: 371 | 2026-07-25T02:46:08+00:00 | Vulnerability · Source |
| CVE-2023-2663 | suse_vex | SUSE CVE CVE-2023-2663 | known not affected: 410 | 2026-07-25T02:46:06+00:00 | Vulnerability · Source |
| CVE-2023-2731 | suse_vex | SUSE CVE CVE-2023-2731 | known affected: 453 known not affected: 22 recommended: 141 | 2026-07-25T02:46:01+00:00 | Vulnerability · Source |
| CVE-2023-2858 | suse_vex | SUSE CVE CVE-2023-2858 | known affected: 103 known not affected: 137 recommended: 198 | 2026-07-25T02:45:53+00:00 | Vulnerability · Source |
| CVE-2023-3044 | suse_vex | SUSE CVE CVE-2023-3044 | known not affected: 394 | 2026-07-25T02:45:46+00:00 | Vulnerability · Source |
| CVE-2023-3106 | suse_vex | SUSE CVE CVE-2023-3106 | known not affected: 325 recommended: 42 | 2026-07-25T02:45:43+00:00 | Vulnerability · Source |
| CVE-2023-3138 | suse_vex | SUSE CVE CVE-2023-3138 | known affected: 427 recommended: 382 | 2026-07-25T02:45:38+00:00 | Vulnerability · Source |