VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291265 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-40131 | suse_vex | SUSE CVE CVE-2025-40131 | known not affected: 408 | 2026-08-07T23:58:53+00:00 | Vulnerability · Source |
| CVE-2025-40143 | suse_vex | SUSE CVE CVE-2025-40143 | known not affected: 408 | 2026-08-07T23:58:51+00:00 | Vulnerability · Source |
| CVE-2025-40146 | suse_vex | SUSE CVE CVE-2025-40146 | known affected: 341 known not affected: 6 | 2026-08-07T23:58:50+00:00 | Vulnerability · Source |
| CVE-2025-40265 | suse_vex | SUSE CVE CVE-2025-40265 | known not affected: 408 | 2026-08-07T23:58:40+00:00 | Vulnerability · Source |
| CVE-2025-40267 | suse_vex | SUSE CVE CVE-2025-40267 | known not affected: 408 | 2026-08-07T23:58:38+00:00 | Vulnerability · Source |
| CVE-2025-40780 | suse_vex | SUSE CVE CVE-2025-40780 | known affected: 440 known not affected: 70 recommended: 339 | 2026-08-07T23:58:34+00:00 | Vulnerability · Source |
| CVE-2025-47912 | suse_vex | SUSE CVE CVE-2025-47912 | known affected: 24 known not affected: 67 recommended: 312 | 2026-08-07T23:58:30+00:00 | Vulnerability · Source |
| CVE-2025-58187 | suse_vex | SUSE CVE CVE-2025-58187 | known affected: 39 known not affected: 94 recommended: 312 | 2026-08-07T23:58:21+00:00 | Vulnerability · Source |
| CVE-2025-58188 | suse_vex | SUSE CVE CVE-2025-58188 | known affected: 24 known not affected: 67 recommended: 312 | 2026-08-07T23:58:19+00:00 | Vulnerability · Source |
| CVE-2025-61732 | suse_vex | SUSE CVE CVE-2025-61732 | known affected: 18 known not affected: 114 recommended: 289 | 2026-08-07T23:58:15+00:00 | Vulnerability · Source |
| CVE-2025-68738 | suse_vex | SUSE CVE CVE-2025-68738 | known not affected: 453 recommended: 6 | 2026-08-07T23:58:05+00:00 | Vulnerability · Source |
| CVE-2025-68752 | suse_vex | SUSE CVE CVE-2025-68752 | known not affected: 353 recommended: 6 | 2026-08-07T23:58:03+00:00 | Vulnerability · Source |
| CVE-2025-68756 | suse_vex | SUSE CVE CVE-2025-68756 | known not affected: 217 recommended: 6 | 2026-08-07T23:58:02+00:00 | Vulnerability · Source |
| CVE-2025-71298 | suse_vex | SUSE CVE CVE-2025-71298 | known not affected: 295 | 2026-08-07T23:57:57+00:00 | Vulnerability · Source |
| CVE-2026-18220 | suse_vex | SUSE CVE CVE-2026-18220 | known affected: 155 | 2026-08-07T23:57:08+00:00 | Vulnerability · Source |
| CVE-2026-19079 | suse_vex | SUSE CVE CVE-2026-19079 | No product status | 2026-08-07T23:57:06+00:00 | Vulnerability · Source |
| CVE-2026-23008 | suse_vex | SUSE CVE CVE-2026-23008 | known not affected: 336 | 2026-08-07T23:55:43+00:00 | Vulnerability · Source |
| CVE-2026-23036 | suse_vex | SUSE CVE CVE-2026-23036 | known not affected: 336 | 2026-08-07T23:55:41+00:00 | Vulnerability · Source |