VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288716 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 260 recommended: 311 | 2026-07-31T17:03:45+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 112 known not affected: 240 | 2026-07-31T17:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known not affected: 302 recommended: 70 | 2026-07-31T17:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49245 | suse_vex | SUSE CVE CVE-2022-49245 | known not affected: 352 | 2026-07-31T17:03:33+00:00 | Vulnerability · Source |
| CVE-2022-49510 | suse_vex | SUSE CVE CVE-2022-49510 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:28+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-31T17:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known not affected: 397 | 2026-07-31T17:03:19+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-31T17:03:17+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 154 known not affected: 258 | 2026-07-31T17:03:16+00:00 | Vulnerability · Source |
| CVE-2022-50039 | suse_vex | SUSE CVE CVE-2022-50039 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-31T17:03:14+00:00 | Vulnerability · Source |
| CVE-2022-50113 | suse_vex | SUSE CVE CVE-2022-50113 | known not affected: 401 recommended: 47 | 2026-07-31T17:03:12+00:00 | Vulnerability · Source |
| CVE-2022-50639 | suse_vex | SUSE CVE CVE-2022-50639 | known not affected: 408 recommended: 29 | 2026-07-31T17:03:03+00:00 | Vulnerability · Source |
| CVE-2022-50645 | suse_vex | SUSE CVE CVE-2022-50645 | known affected: 191 known not affected: 217 recommended: 29 | 2026-07-31T17:03:01+00:00 | Vulnerability · Source |
| CVE-2022-50758 | suse_vex | SUSE CVE CVE-2022-50758 | known affected: 354 known not affected: 329 recommended: 200 | 2026-07-31T17:02:59+00:00 | Vulnerability · Source |
| CVE-2022-50763 | suse_vex | SUSE CVE CVE-2022-50763 | known affected: 354 known not affected: 309 recommended: 196 | 2026-07-31T17:02:57+00:00 | Vulnerability · Source |
| CVE-2022-50779 | suse_vex | SUSE CVE CVE-2022-50779 | known affected: 354 known not affected: 204 recommended: 219 | 2026-07-31T17:02:55+00:00 | Vulnerability · Source |
| CVE-2023-1601 | suse_vex | SUSE CVE CVE-2023-1601 | known not affected: 340 | 2026-07-31T17:02:51+00:00 | Vulnerability · Source |
| CVE-2023-3341 | suse_vex | SUSE CVE CVE-2023-3341 | known affected: 236 known not affected: 11 recommended: 742 | 2026-07-31T17:02:46+00:00 | Vulnerability · Source |
| CVE-2023-4046 | suse_vex | SUSE CVE CVE-2023-4046 | known affected: 43 recommended: 271 | 2026-07-31T17:02:44+00:00 | Vulnerability · Source |
| CVE-2023-32360 | suse_vex | SUSE CVE CVE-2023-32360 | known affected: 364 recommended: 677 | 2026-07-31T17:02:33+00:00 | Vulnerability · Source |
| CVE-2023-36661 | suse_vex | SUSE CVE CVE-2023-36661 | known affected: 84 known not affected: 178 recommended: 108 | 2026-07-31T17:02:31+00:00 | Vulnerability · Source |
| CVE-2023-42465 | suse_vex | SUSE CVE CVE-2023-42465 | known affected: 302 recommended: 317 | 2026-07-31T17:02:28+00:00 | Vulnerability · Source |
| CVE-2023-47108 | suse_vex | SUSE CVE CVE-2023-47108 | known affected: 320 known not affected: 499 recommended: 326 | 2026-07-31T17:02:24+00:00 | Vulnerability · Source |
| CVE-2024-26801 | suse_vex | SUSE CVE CVE-2024-26801 | known affected: 557 known not affected: 70 recommended: 608 | 2026-07-31T17:01:49+00:00 | Vulnerability · Source |
| CVE-2024-26886 | suse_vex | SUSE CVE CVE-2024-26886 | known affected: 620 known not affected: 114 recommended: 385 | 2026-07-31T17:01:46+00:00 | Vulnerability · Source |
| CVE-2024-26894 | suse_vex | SUSE CVE CVE-2024-26894 | known affected: 545 known not affected: 76 recommended: 623 | 2026-07-31T17:01:45+00:00 | Vulnerability · Source |
| CVE-2024-38541 | suse_vex | SUSE CVE CVE-2024-38541 | known affected: 284 known not affected: 113 recommended: 989 | 2026-07-31T17:01:29+00:00 | Vulnerability · Source |
| CVE-2024-41053 | suse_vex | SUSE CVE CVE-2024-41053 | known not affected: 324 | 2026-07-31T17:01:23+00:00 | Vulnerability · Source |
| CVE-2024-49940 | suse_vex | SUSE CVE CVE-2024-49940 | known affected: 759 known not affected: 38 recommended: 355 | 2026-07-31T17:01:08+00:00 | Vulnerability · Source |
| CVE-2024-50191 | suse_vex | SUSE CVE CVE-2024-50191 | known affected: 129 recommended: 49 | 2026-07-31T17:01:04+00:00 | Vulnerability · Source |
| CVE-2024-50251 | suse_vex | SUSE CVE CVE-2024-50251 | known affected: 702 known not affected: 60 recommended: 372 | 2026-07-31T17:01:02+00:00 | Vulnerability · Source |
| CVE-2024-50304 | suse_vex | SUSE CVE CVE-2024-50304 | known affected: 705 known not affected: 42 recommended: 393 | 2026-07-31T17:01:00+00:00 | Vulnerability · Source |
| CVE-2024-53051 | suse_vex | SUSE CVE CVE-2024-53051 | known affected: 624 known not affected: 36 recommended: 463 | 2026-07-31T17:00:58+00:00 | Vulnerability · Source |
| CVE-2024-53217 | suse_vex | SUSE CVE CVE-2024-53217 | known affected: 580 known not affected: 73 recommended: 504 | 2026-07-31T17:00:49+00:00 | Vulnerability · Source |
| CVE-2024-56378 | suse_vex | SUSE CVE CVE-2024-56378 | known affected: 284 recommended: 186 | 2026-07-31T17:00:45+00:00 | Vulnerability · Source |
| CVE-2024-56590 | suse_vex | SUSE CVE CVE-2024-56590 | known affected: 662 known not affected: 52 recommended: 533 | 2026-07-31T17:00:41+00:00 | Vulnerability · Source |
| CVE-2024-56603 | suse_vex | SUSE CVE CVE-2024-56603 | known affected: 737 known not affected: 36 recommended: 488 | 2026-07-31T17:00:39+00:00 | Vulnerability · Source |
| CVE-2024-56694 | suse_vex | SUSE CVE CVE-2024-56694 | known affected: 529 known not affected: 240 recommended: 363 | 2026-07-31T17:00:34+00:00 | Vulnerability · Source |
| CVE-2024-56779 | suse_vex | SUSE CVE CVE-2024-56779 | known affected: 690 known not affected: 36 recommended: 443 | 2026-07-31T17:00:28+00:00 | Vulnerability · Source |
| CVE-2024-58075 | suse_vex | SUSE CVE CVE-2024-58075 | known not affected: 352 recommended: 136 | 2026-07-31T17:00:21+00:00 | Vulnerability · Source |
| CVE-2025-2830 | suse_vex | SUSE CVE CVE-2025-2830 | known affected: 16 known not affected: 134 recommended: 24 | 2026-07-31T17:00:17+00:00 | Vulnerability · Source |
| CVE-2025-21860 | suse_vex | SUSE CVE CVE-2025-21860 | known affected: 57 known not affected: 291 | 2026-07-31T16:59:50+00:00 | Vulnerability · Source |
| CVE-2025-23153 | suse_vex | SUSE CVE CVE-2025-23153 | known not affected: 397 | 2026-07-31T16:59:40+00:00 | Vulnerability · Source |
| CVE-2025-31133 | suse_vex | SUSE CVE CVE-2025-31133 | known affected: 388 known not affected: 1148 recommended: 237 | 2026-07-31T16:59:33+00:00 | Vulnerability · Source |
| CVE-2025-47906 | suse_vex | SUSE CVE CVE-2025-47906 | known affected: 42 known not affected: 67 recommended: 505 | 2026-07-31T16:57:57+00:00 | Vulnerability · Source |
| CVE-2025-52565 | suse_vex | SUSE CVE CVE-2025-52565 | known affected: 388 known not affected: 1148 recommended: 236 | 2026-07-31T16:57:50+00:00 | Vulnerability · Source |
| CVE-2025-52881 | suse_vex | SUSE CVE CVE-2025-52881 | known affected: 388 known not affected: 1148 recommended: 288 | 2026-07-31T16:57:48+00:00 | Vulnerability · Source |
| CVE-2025-64181 | suse_vex | SUSE CVE CVE-2025-64181 | known not affected: 143 recommended: 67 | 2026-07-31T16:57:18+00:00 | Vulnerability · Source |
| CVE-2025-64344 | suse_vex | SUSE CVE CVE-2025-64344 | recommended: 3 | 2026-07-31T16:57:15+00:00 | Vulnerability · Source |
| CVE-2025-64432 | suse_vex | SUSE CVE CVE-2025-64432 | first fixed: 1 known not affected: 70 recommended: 28 | 2026-07-31T16:57:14+00:00 | Vulnerability · Source |