VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291911 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-47112 | suse_vex | SUSE CVE CVE-2021-47112 | known affected: 483 known not affected: 198 recommended: 221 | 2026-08-08T00:05:52+00:00 | Vulnerability · Source |
| CVE-2021-47338 | suse_vex | SUSE CVE CVE-2021-47338 | known affected: 388 known not affected: 271 recommended: 155 | 2026-08-08T00:05:48+00:00 | Vulnerability · Source |
| CVE-2021-47358 | suse_vex | SUSE CVE CVE-2021-47358 | known affected: 340 known not affected: 93 recommended: 452 | 2026-08-08T00:05:46+00:00 | Vulnerability · Source |
| CVE-2021-47366 | suse_vex | SUSE CVE CVE-2021-47366 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-08T00:05:45+00:00 | Vulnerability · Source |
| CVE-2021-47620 | suse_vex | SUSE CVE CVE-2021-47620 | known affected: 347 known not affected: 162 recommended: 494 | 2026-08-08T00:05:37+00:00 | Vulnerability · Source |
| CVE-2022-0330 | suse_vex | SUSE CVE CVE-2022-0330 | known affected: 351 known not affected: 87 recommended: 1598 | 2026-08-08T00:05:34+00:00 | Vulnerability · Source |
| CVE-2022-20166 | suse_vex | SUSE CVE CVE-2022-20166 | known affected: 394 known not affected: 63 recommended: 862 | 2026-08-08T00:05:20+00:00 | Vulnerability · Source |
| CVE-2022-21702 | suse_vex | SUSE CVE CVE-2022-21702 | recommended: 164 | 2026-08-08T00:05:16+00:00 | Vulnerability · Source |
| CVE-2022-41915 | suse_vex | SUSE CVE CVE-2022-41915 | known affected: 1 known not affected: 36 recommended: 58 | 2026-08-08T00:04:59+00:00 | Vulnerability · Source |
| CVE-2022-49236 | suse_vex | SUSE CVE CVE-2022-49236 | known affected: 334 known not affected: 298 recommended: 250 | 2026-08-08T00:04:39+00:00 | Vulnerability · Source |
| CVE-2023-25577 | suse_vex | SUSE CVE CVE-2023-25577 | recommended: 157 | 2026-08-08T00:03:59+00:00 | Vulnerability · Source |
| CVE-2023-45853 | suse_vex | SUSE CVE CVE-2023-45853 | known affected: 398 recommended: 501 | 2026-08-08T00:03:44+00:00 | Vulnerability · Source |
| CVE-2023-47627 | suse_vex | SUSE CVE CVE-2023-47627 | known affected: 16 recommended: 30 | 2026-08-08T00:03:41+00:00 | Vulnerability · Source |
| CVE-2023-52599 | suse_vex | SUSE CVE CVE-2023-52599 | known affected: 305 known not affected: 251 recommended: 532 | 2026-08-08T00:03:34+00:00 | Vulnerability · Source |
| CVE-2024-1488 | suse_vex | SUSE CVE CVE-2024-1488 | known not affected: 148 recommended: 8 | 2026-08-08T00:03:08+00:00 | Vulnerability · Source |
| CVE-2024-6409 | suse_vex | SUSE CVE CVE-2024-6409 | known not affected: 226 recommended: 6 | 2026-08-08T00:03:03+00:00 | Vulnerability · Source |
| CVE-2024-11168 | suse_vex | SUSE CVE CVE-2024-11168 | known affected: 582 known not affected: 127 recommended: 615 | 2026-08-08T00:02:58+00:00 | Vulnerability · Source |
| CVE-2024-39705 | suse_vex | SUSE CVE CVE-2024-39705 | recommended: 9 | 2026-08-08T00:02:31+00:00 | Vulnerability · Source |
| CVE-2024-45338 | suse_vex | SUSE CVE CVE-2024-45338 | known affected: 33 known not affected: 921 recommended: 255 | 2026-08-08T00:02:16+00:00 | Vulnerability · Source |
| CVE-2024-45818 | suse_vex | SUSE CVE CVE-2024-45818 | known affected: 380 known not affected: 1 recommended: 302 | 2026-08-08T00:02:12+00:00 | Vulnerability · Source |
| CVE-2024-47607 | suse_vex | SUSE CVE CVE-2024-47607 | known affected: 412 recommended: 1051 | 2026-08-08T00:02:05+00:00 | Vulnerability · Source |
| CVE-2024-49904 | suse_vex | SUSE CVE CVE-2024-49904 | known not affected: 379 recommended: 108 | 2026-08-08T00:01:57+00:00 | Vulnerability · Source |
| CVE-2024-56768 | suse_vex | SUSE CVE CVE-2024-56768 | known not affected: 462 | 2026-08-08T00:01:35+00:00 | Vulnerability · Source |
| CVE-2024-58000 | suse_vex | SUSE CVE CVE-2024-58000 | known not affected: 352 | 2026-08-08T00:01:30+00:00 | Vulnerability · Source |
| CVE-2024-58073 | suse_vex | SUSE CVE CVE-2024-58073 | known not affected: 352 | 2026-08-08T00:01:28+00:00 | Vulnerability · Source |
| CVE-2025-21843 | suse_vex | SUSE CVE CVE-2025-21843 | known affected: 57 known not affected: 295 | 2026-08-08T00:01:08+00:00 | Vulnerability · Source |
| CVE-2025-22048 | suse_vex | SUSE CVE CVE-2025-22048 | known not affected: 439 | 2026-08-08T00:01:04+00:00 | Vulnerability · Source |
| CVE-2025-22092 | suse_vex | SUSE CVE CVE-2025-22092 | known not affected: 348 recommended: 83 | 2026-08-08T00:01:02+00:00 | Vulnerability · Source |
| CVE-2025-22098 | suse_vex | SUSE CVE CVE-2025-22098 | known not affected: 348 | 2026-08-08T00:01:01+00:00 | Vulnerability · Source |
| CVE-2025-32910 | suse_vex | SUSE CVE CVE-2025-32910 | known affected: 55 known not affected: 6 recommended: 240 | 2026-08-08T00:00:52+00:00 | Vulnerability · Source |
| CVE-2025-37783 | suse_vex | SUSE CVE CVE-2025-37783 | known not affected: 397 | 2026-08-08T00:00:49+00:00 | Vulnerability · Source |
| CVE-2025-37807 | suse_vex | SUSE CVE CVE-2025-37807 | known not affected: 78 | 2026-08-08T00:00:47+00:00 | Vulnerability · Source |
| CVE-2025-37893 | suse_vex | SUSE CVE CVE-2025-37893 | known not affected: 443 | 2026-08-08T00:00:44+00:00 | Vulnerability · Source |
| CVE-2025-38021 | suse_vex | SUSE CVE CVE-2025-38021 | known not affected: 401 | 2026-08-08T00:00:40+00:00 | Vulnerability · Source |
| CVE-2025-38049 | suse_vex | SUSE CVE CVE-2025-38049 | known not affected: 447 | 2026-08-08T00:00:37+00:00 | Vulnerability · Source |
| CVE-2025-38121 | suse_vex | SUSE CVE CVE-2025-38121 | known not affected: 416 | 2026-08-08T00:00:33+00:00 | Vulnerability · Source |
| CVE-2025-38280 | suse_vex | SUSE CVE CVE-2025-38280 | known affected: 195 known not affected: 263 | 2026-08-08T00:00:23+00:00 | Vulnerability · Source |
| CVE-2025-38281 | suse_vex | SUSE CVE CVE-2025-38281 | known not affected: 416 | 2026-08-08T00:00:22+00:00 | Vulnerability · Source |
| CVE-2025-38285 | suse_vex | SUSE CVE CVE-2025-38285 | known affected: 195 known not affected: 104 | 2026-08-08T00:00:21+00:00 | Vulnerability · Source |
| CVE-2025-38294 | suse_vex | SUSE CVE CVE-2025-38294 | known not affected: 416 | 2026-08-08T00:00:19+00:00 | Vulnerability · Source |
| CVE-2025-38388 | suse_vex | SUSE CVE CVE-2025-38388 | known not affected: 458 | 2026-08-08T00:00:14+00:00 | Vulnerability · Source |
| CVE-2025-38596 | suse_vex | SUSE CVE CVE-2025-38596 | known not affected: 346 | 2026-08-07T23:59:59+00:00 | Vulnerability · Source |
| CVE-2025-38641 | suse_vex | SUSE CVE CVE-2025-38641 | known not affected: 416 | 2026-08-07T23:59:52+00:00 | Vulnerability · Source |
| CVE-2025-38647 | suse_vex | SUSE CVE CVE-2025-38647 | known not affected: 416 | 2026-08-07T23:59:50+00:00 | Vulnerability · Source |
| CVE-2025-38669 | suse_vex | SUSE CVE CVE-2025-38669 | known not affected: 416 | 2026-08-07T23:59:46+00:00 | Vulnerability · Source |
| CVE-2025-39741 | suse_vex | SUSE CVE CVE-2025-39741 | known not affected: 416 | 2026-08-07T23:59:37+00:00 | Vulnerability · Source |
| CVE-2025-39762 | suse_vex | SUSE CVE CVE-2025-39762 | known not affected: 416 | 2026-08-07T23:59:34+00:00 | Vulnerability · Source |
| CVE-2025-39820 | suse_vex | SUSE CVE CVE-2025-39820 | known not affected: 416 | 2026-08-07T23:59:26+00:00 | Vulnerability · Source |
| CVE-2025-40023 | suse_vex | SUSE CVE CVE-2025-40023 | known not affected: 407 | 2026-08-07T23:59:08+00:00 | Vulnerability · Source |
| CVE-2025-40066 | suse_vex | SUSE CVE CVE-2025-40066 | known not affected: 407 recommended: 6 | 2026-08-07T23:59:01+00:00 | Vulnerability · Source |