VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-49125 | suse_vex | SUSE CVE CVE-2025-49125 | known affected: 514 known not affected: 38 recommended: 506 | 2026-10-16T12:50:56+00:00 | Vulnerability · Source |
| CVE-2025-49795 | suse_vex | SUSE CVE CVE-2025-49795 | known affected: 369 known not affected: 331 recommended: 138 | 2026-10-16T12:50:54+00:00 | Vulnerability · Source |
| CVE-2025-50420 | suse_vex | SUSE CVE CVE-2025-50420 | known affected: 230 known not affected: 21 recommended: 215 | 2026-10-16T12:50:52+00:00 | Vulnerability · Source |
| CVE-2025-50946 | suse_vex | SUSE CVE CVE-2025-50946 | recommended: 3 | 2026-10-16T12:50:51+00:00 | Vulnerability · Source |
| CVE-2025-51667 | suse_vex | SUSE CVE CVE-2025-51667 | recommended: 3 | 2026-10-16T12:50:50+00:00 | Vulnerability · Source |
| CVE-2025-52194 | suse_vex | SUSE CVE CVE-2025-52194 | known affected: 112 known not affected: 1 recommended: 57 | 2026-10-16T12:50:48+00:00 | Vulnerability · Source |
| CVE-2025-52885 | suse_vex | SUSE CVE CVE-2025-52885 | known affected: 32 known not affected: 132 recommended: 219 | 2026-10-16T12:50:47+00:00 | Vulnerability · Source |
| CVE-2025-52900 | suse_vex | SUSE CVE CVE-2025-52900 | recommended: 5 | 2026-10-16T12:50:45+00:00 | Vulnerability · Source |
| CVE-2025-52903 | suse_vex | SUSE CVE CVE-2025-52903 | recommended: 5 | 2026-10-16T12:50:44+00:00 | Vulnerability · Source |
| CVE-2025-52904 | suse_vex | SUSE CVE CVE-2025-52904 | recommended: 5 | 2026-10-16T12:50:42+00:00 | Vulnerability · Source |
| CVE-2025-52995 | suse_vex | SUSE CVE CVE-2025-52995 | recommended: 5 | 2026-10-16T12:50:41+00:00 | Vulnerability · Source |
| CVE-2025-52997 | suse_vex | SUSE CVE CVE-2025-52997 | recommended: 5 | 2026-10-16T12:50:40+00:00 | Vulnerability · Source |
| CVE-2025-53534 | suse_vex | SUSE CVE CVE-2025-53534 | recommended: 5 | 2026-10-16T12:50:38+00:00 | Vulnerability · Source |
| CVE-2025-54293 | suse_vex | SUSE CVE CVE-2025-54293 | recommended: 3 | 2026-10-16T12:50:35+00:00 | Vulnerability · Source |
| CVE-2025-54368 | suse_vex | SUSE CVE CVE-2025-54368 | recommended: 16 | 2026-10-16T12:50:34+00:00 | Vulnerability · Source |
| CVE-2025-54770 | suse_vex | SUSE CVE CVE-2025-54770 | known affected: 394 known not affected: 417 recommended: 199 | 2026-10-16T12:50:31+00:00 | Vulnerability · Source |
| CVE-2025-54999 | suse_vex | SUSE CVE CVE-2025-54999 | recommended: 5 | 2026-10-16T12:50:29+00:00 | Vulnerability · Source |
| CVE-2025-55001 | suse_vex | SUSE CVE CVE-2025-55001 | recommended: 5 | 2026-10-16T12:50:28+00:00 | Vulnerability · Source |
| CVE-2025-55131 | suse_vex | SUSE CVE CVE-2025-55131 | known affected: 168 recommended: 201 | 2026-10-16T12:50:26+00:00 | Vulnerability · Source |
| CVE-2025-55193 | suse_vex | SUSE CVE CVE-2025-55193 | known affected: 12 known not affected: 123 recommended: 5 | 2026-10-16T12:50:23+00:00 | Vulnerability · Source |
| CVE-2025-55199 | suse_vex | SUSE CVE CVE-2025-55199 | known affected: 0 known not affected: 84 recommended: 52 | 2026-10-16T12:50:21+00:00 | Vulnerability · Source |
| CVE-2025-55752 | suse_vex | SUSE CVE CVE-2025-55752 | known affected: 515 known not affected: 37 recommended: 548 | 2026-10-16T12:50:19+00:00 | Vulnerability · Source |
| CVE-2025-57804 | suse_vex | SUSE CVE CVE-2025-57804 | known affected: 64 recommended: 25 | 2026-10-16T12:50:17+00:00 | Vulnerability · Source |
| CVE-2025-58050 | suse_vex | SUSE CVE CVE-2025-58050 | known affected: 0 known not affected: 7058 recommended: 53 | 2026-10-16T12:50:14+00:00 | Vulnerability · Source |
| CVE-2025-58060 | suse_vex | SUSE CVE CVE-2025-58060 | known affected: 564 recommended: 428 | 2026-10-16T12:50:12+00:00 | Vulnerability · Source |
| CVE-2025-58075 | suse_vex | SUSE CVE CVE-2025-58075 | recommended: 3 | 2026-10-16T12:50:10+00:00 | Vulnerability · Source |
| CVE-2025-58147 | suse_vex | SUSE CVE CVE-2025-58147 | known affected: 358 known not affected: 184 recommended: 172 | 2026-10-16T12:50:08+00:00 | Vulnerability · Source |
| CVE-2025-58186 | suse_vex | SUSE CVE CVE-2025-58186 | known affected: 30 known not affected: 69 recommended: 281 | 2026-10-16T12:50:04+00:00 | Vulnerability · Source |
| CVE-2025-58189 | suse_vex | SUSE CVE CVE-2025-58189 | known affected: 30 known not affected: 69 recommended: 281 | 2026-10-16T12:50:02+00:00 | Vulnerability · Source |
| CVE-2025-58767 | suse_vex | SUSE CVE CVE-2025-58767 | known affected: 583 known not affected: 197 recommended: 166 | 2026-10-16T12:49:59+00:00 | Vulnerability · Source |
| CVE-2025-59352 | suse_vex | SUSE CVE CVE-2025-59352 | recommended: 3 | 2026-10-16T12:49:57+00:00 | Vulnerability · Source |
| CVE-2025-59358 | suse_vex | SUSE CVE CVE-2025-59358 | recommended: 3 | 2026-10-16T12:49:55+00:00 | Vulnerability · Source |
| CVE-2025-59465 | suse_vex | SUSE CVE CVE-2025-59465 | known affected: 168 recommended: 201 | 2026-10-16T12:49:53+00:00 | Vulnerability · Source |
| CVE-2025-59777 | suse_vex | SUSE CVE CVE-2025-59777 | known affected: 0 known not affected: 132 recommended: 31 | 2026-10-16T12:49:51+00:00 | Vulnerability · Source |
| CVE-2025-59824 | suse_vex | SUSE CVE CVE-2025-59824 | recommended: 3 | 2026-10-16T12:49:48+00:00 | Vulnerability · Source |
| CVE-2025-61101 | suse_vex | SUSE CVE CVE-2025-61101 | known affected: 267 known not affected: 335 recommended: 112 | 2026-10-16T12:49:46+00:00 | Vulnerability · Source |
| CVE-2025-61662 | suse_vex | SUSE CVE CVE-2025-61662 | known affected: 734 recommended: 348 | 2026-10-16T12:49:43+00:00 | Vulnerability · Source |
| CVE-2025-61727 | suse_vex | SUSE CVE CVE-2025-61727 | known affected: 0 known not affected: 296 recommended: 285 | 2026-10-16T12:49:41+00:00 | Vulnerability · Source |
| CVE-2025-61915 | suse_vex | SUSE CVE CVE-2025-61915 | known affected: 766 recommended: 230 | 2026-10-16T12:49:39+00:00 | Vulnerability · Source |
| CVE-2025-62513 | suse_vex | SUSE CVE CVE-2025-62513 | recommended: 11 | 2026-10-16T12:49:36+00:00 | Vulnerability · Source |
| CVE-2025-62518 | suse_vex | SUSE CVE CVE-2025-62518 | recommended: 14 | 2026-10-16T12:49:34+00:00 | Vulnerability · Source |
| CVE-2025-62714 | suse_vex | SUSE CVE CVE-2025-62714 | recommended: 3 | 2026-10-16T12:49:33+00:00 | Vulnerability · Source |
| CVE-2025-62727 | suse_vex | SUSE CVE CVE-2025-62727 | known affected: 0 known not affected: 2 recommended: 11 | 2026-10-16T12:49:32+00:00 | Vulnerability · Source |
| CVE-2025-62820 | suse_vex | SUSE CVE CVE-2025-62820 | recommended: 3 | 2026-10-16T12:49:30+00:00 | Vulnerability · Source |
| CVE-2025-62878 | suse_vex | SUSE CVE CVE-2025-62878 | recommended: 2 | 2026-10-16T12:49:29+00:00 | Vulnerability · Source |
| CVE-2025-64076 | suse_vex | SUSE CVE CVE-2025-64076 | recommended: 5 | 2026-10-16T12:49:27+00:00 | Vulnerability · Source |
| CVE-2025-64324 | suse_vex | SUSE CVE CVE-2025-64324 | known affected: 1 known not affected: 76 recommended: 25 | 2026-10-16T12:49:26+00:00 | Vulnerability · Source |
| CVE-2025-64432 | suse_vex | SUSE CVE CVE-2025-64432 | known affected: 1 known not affected: 76 recommended: 27 | 2026-10-16T12:49:24+00:00 | Vulnerability · Source |
| CVE-2025-64434 | suse_vex | SUSE CVE CVE-2025-64434 | known affected: 1 known not affected: 76 recommended: 25 | 2026-10-16T12:49:22+00:00 | Vulnerability · Source |
| CVE-2025-64443 | suse_vex | SUSE CVE CVE-2025-64443 | recommended: 2 | 2026-10-16T12:49:21+00:00 | Vulnerability · Source |