VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294149 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48833 | suse_vex | SUSE CVE CVE-2022-48833 | known not affected: 318 | 2026-07-25T17:19:15+00:00 | Vulnerability · Source |
| CVE-2022-48895 | suse_vex | SUSE CVE CVE-2022-48895 | known not affected: 310 | 2026-07-25T17:18:40+00:00 | Vulnerability · Source |
| CVE-2022-48908 | suse_vex | SUSE CVE CVE-2022-48908 | known not affected: 514 | 2026-07-25T17:18:31+00:00 | Vulnerability · Source |
| CVE-2022-49047 | suse_vex | SUSE CVE CVE-2022-49047 | known not affected: 352 | 2026-07-25T17:17:16+00:00 | Vulnerability · Source |
| CVE-2022-49103 | suse_vex | SUSE CVE CVE-2022-49103 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49186 | suse_vex | SUSE CVE CVE-2022-49186 | known not affected: 352 | 2026-07-25T17:15:47+00:00 | Vulnerability · Source |
| CVE-2022-49206 | suse_vex | SUSE CVE CVE-2022-49206 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-25T17:15:34+00:00 | Vulnerability · Source |
| CVE-2022-49578 | suse_vex | SUSE CVE CVE-2022-49578 | known affected: 618 known not affected: 104 recommended: 53 | 2026-07-25T17:12:48+00:00 | Vulnerability · Source |
| CVE-2022-49602 | suse_vex | SUSE CVE CVE-2022-49602 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:32+00:00 | Vulnerability · Source |
| CVE-2022-49817 | suse_vex | SUSE CVE CVE-2022-49817 | known affected: 112 known not affected: 285 | 2026-07-25T17:11:04+00:00 | Vulnerability · Source |
| CVE-2022-49947 | suse_vex | SUSE CVE CVE-2022-49947 | known not affected: 401 | 2026-07-25T17:10:21+00:00 | Vulnerability · Source |
| CVE-2022-50114 | suse_vex | SUSE CVE CVE-2022-50114 | known affected: 106 known not affected: 295 | 2026-07-25T17:09:20+00:00 | Vulnerability · Source |
| CVE-2022-50163 | suse_vex | SUSE CVE CVE-2022-50163 | known affected: 92 known not affected: 309 | 2026-07-25T17:08:51+00:00 | Vulnerability · Source |
| CVE-2022-50205 | suse_vex | SUSE CVE CVE-2022-50205 | known affected: 245 known not affected: 171 | 2026-07-25T17:08:30+00:00 | Vulnerability · Source |
| CVE-2022-50415 | suse_vex | SUSE CVE CVE-2022-50415 | known not affected: 416 | 2026-07-25T17:06:52+00:00 | Vulnerability · Source |
| CVE-2022-50550 | suse_vex | SUSE CVE CVE-2022-50550 | known affected: 106 known not affected: 310 recommended: 29 | 2026-07-25T17:06:10+00:00 | Vulnerability · Source |
| CVE-2022-50725 | suse_vex | SUSE CVE CVE-2022-50725 | known not affected: 453 | 2026-07-25T17:05:17+00:00 | Vulnerability · Source |
| CVE-2022-50857 | suse_vex | SUSE CVE CVE-2022-50857 | known affected: 61 known not affected: 193 | 2026-07-25T17:04:21+00:00 | Vulnerability · Source |
| CVE-2023-3355 | suse_vex | SUSE CVE CVE-2023-3355 | known not affected: 361 | 2026-07-25T17:03:23+00:00 | Vulnerability · Source |
| CVE-2023-7216 | suse_vex | SUSE CVE CVE-2023-7216 | known affected: 3 known not affected: 74 | 2026-07-25T17:02:46+00:00 | Vulnerability · Source |
| CVE-2023-29454 | suse_vex | SUSE CVE CVE-2023-29454 | known not affected: 21 recommended: 50 | 2026-07-25T17:02:20+00:00 | Vulnerability · Source |
| CVE-2023-32722 | suse_vex | SUSE CVE CVE-2023-32722 | known not affected: 17 recommended: 10 | 2026-07-25T17:02:01+00:00 | Vulnerability · Source |
| CVE-2023-34322 | suse_vex | SUSE CVE CVE-2023-34322 | known affected: 239 recommended: 464 | 2026-07-25T17:01:55+00:00 | Vulnerability · Source |
| CVE-2023-35825 | suse_vex | SUSE CVE CVE-2023-35825 | recommended: 49 | 2026-07-25T17:01:49+00:00 | Vulnerability · Source |
| CVE-2023-39327 | suse_vex | SUSE CVE CVE-2023-39327 | known affected: 748 known not affected: 7 recommended: 79 | 2026-07-25T17:01:36+00:00 | Vulnerability · Source |
| CVE-2023-45468 | suse_vex | SUSE CVE CVE-2023-45468 | recommended: 18 | 2026-07-25T17:01:17+00:00 | Vulnerability · Source |
| CVE-2023-46839 | suse_vex | SUSE CVE CVE-2023-46839 | known affected: 361 recommended: 390 | 2026-07-25T17:01:07+00:00 | Vulnerability · Source |
| CVE-2023-52444 | suse_vex | SUSE CVE CVE-2023-52444 | known not affected: 312 | 2026-07-25T17:00:56+00:00 | Vulnerability · Source |
| CVE-2023-52516 | suse_vex | SUSE CVE CVE-2023-52516 | known not affected: 292 | 2026-07-25T17:00:41+00:00 | Vulnerability · Source |
| CVE-2023-52609 | suse_vex | SUSE CVE CVE-2023-52609 | known not affected: 292 | 2026-07-25T17:00:34+00:00 | Vulnerability · Source |
| CVE-2023-53259 | suse_vex | SUSE CVE CVE-2023-53259 | known affected: 494 known not affected: 195 recommended: 206 | 2026-07-25T16:59:29+00:00 | Vulnerability · Source |
| CVE-2023-53310 | suse_vex | SUSE CVE CVE-2023-53310 | known not affected: 416 | 2026-07-25T16:59:27+00:00 | Vulnerability · Source |
| CVE-2023-53346 | suse_vex | SUSE CVE CVE-2023-53346 | known affected: 163 known not affected: 253 | 2026-07-25T16:59:24+00:00 | Vulnerability · Source |
| CVE-2023-53413 | suse_vex | SUSE CVE CVE-2023-53413 | known affected: 462 known not affected: 186 recommended: 206 | 2026-07-25T16:59:11+00:00 | Vulnerability · Source |
| CVE-2023-53605 | suse_vex | SUSE CVE CVE-2023-53605 | known affected: 452 known not affected: 206 recommended: 245 | 2026-07-25T16:58:51+00:00 | Vulnerability · Source |
| CVE-2024-22116 | suse_vex | SUSE CVE CVE-2024-22116 | known not affected: 11 | 2026-07-25T16:57:21+00:00 | Vulnerability · Source |
| CVE-2024-22119 | suse_vex | SUSE CVE CVE-2024-22119 | known affected: 13 recommended: 25 | 2026-07-25T16:57:20+00:00 | Vulnerability · Source |
| CVE-2024-22123 | suse_vex | SUSE CVE CVE-2024-22123 | known not affected: 11 | 2026-07-25T16:57:18+00:00 | Vulnerability · Source |
| CVE-2024-24479 | suse_vex | SUSE CVE CVE-2024-24479 | known not affected: 316 | 2026-07-25T16:57:12+00:00 | Vulnerability · Source |
| CVE-2024-26731 | suse_vex | SUSE CVE CVE-2024-26731 | known not affected: 296 recommended: 356 | 2026-07-25T16:56:49+00:00 | Vulnerability · Source |
| CVE-2024-26941 | suse_vex | SUSE CVE CVE-2024-26941 | known not affected: 330 recommended: 59 | 2026-07-25T16:56:27+00:00 | Vulnerability · Source |
| CVE-2024-26945 | suse_vex | SUSE CVE CVE-2024-26945 | known affected: 394 known not affected: 270 recommended: 358 | 2026-07-25T16:56:25+00:00 | Vulnerability · Source |
| CVE-2024-46863 | suse_vex | SUSE CVE CVE-2024-46863 | known not affected: 324 recommended: 59 | 2026-07-25T16:53:32+00:00 | Vulnerability · Source |
| CVE-2024-50097 | suse_vex | SUSE CVE CVE-2024-50097 | known not affected: 370 recommended: 6 | 2026-07-25T16:53:17+00:00 | Vulnerability · Source |
| CVE-2024-58022 | suse_vex | SUSE CVE CVE-2024-58022 | known not affected: 352 | 2026-07-25T16:52:33+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-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 |