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-38535 | suse_vex | SUSE CVE CVE-2025-38535 | known affected: 582 known not affected: 264 recommended: 521 | 2026-10-16T00:54:59+00:00 | Vulnerability · Source |
| CVE-2025-38590 | suse_vex | SUSE CVE CVE-2025-38590 | known affected: 593 known not affected: 213 recommended: 521 | 2026-10-16T00:54:56+00:00 | Vulnerability · Source |
| CVE-2025-38613 | suse_vex | SUSE CVE CVE-2025-38613 | known affected: 0 known not affected: 521 | 2026-10-16T00:54:51+00:00 | Vulnerability · Source |
| CVE-2025-38635 | suse_vex | SUSE CVE CVE-2025-38635 | known affected: 396 known not affected: 450 recommended: 503 | 2026-10-16T00:54:49+00:00 | Vulnerability · Source |
| CVE-2025-38640 | suse_vex | SUSE CVE CVE-2025-38640 | known affected: 401 known not affected: 405 recommended: 503 | 2026-10-16T00:54:46+00:00 | Vulnerability · Source |
| CVE-2025-38652 | suse_vex | SUSE CVE CVE-2025-38652 | known affected: 394 known not affected: 530 recommended: 4 | 2026-10-16T00:54:44+00:00 | Vulnerability · Source |
| CVE-2025-38660 | suse_vex | SUSE CVE CVE-2025-38660 | known affected: 468 known not affected: 338 recommended: 503 | 2026-10-16T00:54:42+00:00 | Vulnerability · Source |
| CVE-2025-38678 | suse_vex | SUSE CVE CVE-2025-38678 | known affected: 351 known not affected: 262 recommended: 806 | 2026-10-16T00:54:39+00:00 | Vulnerability · Source |
| CVE-2025-39701 | suse_vex | SUSE CVE CVE-2025-39701 | known affected: 463 known not affected: 317 recommended: 495 | 2026-10-16T00:54:36+00:00 | Vulnerability · Source |
| CVE-2025-39706 | suse_vex | SUSE CVE CVE-2025-39706 | known affected: 632 known not affected: 124 recommended: 518 | 2026-10-16T00:54:34+00:00 | Vulnerability · Source |
| CVE-2025-39734 | suse_vex | SUSE CVE CVE-2025-39734 | known affected: 0 known not affected: 520 | 2026-10-16T00:54:32+00:00 | Vulnerability · Source |
| CVE-2025-39945 | suse_vex | SUSE CVE CVE-2025-39945 | known affected: 356 known not affected: 199 recommended: 728 | 2026-10-16T00:54:26+00:00 | Vulnerability · Source |
| CVE-2025-40016 | suse_vex | SUSE CVE CVE-2025-40016 | known affected: 402 known not affected: 399 recommended: 501 | 2026-10-16T00:54:21+00:00 | Vulnerability · Source |
| CVE-2025-40035 | suse_vex | SUSE CVE CVE-2025-40035 | known affected: 726 recommended: 538 | 2026-10-16T00:54:18+00:00 | Vulnerability · Source |
| CVE-2025-40041 | suse_vex | SUSE CVE CVE-2025-40041 | known affected: 0 known not affected: 511 recommended: 64 | 2026-10-16T00:54:16+00:00 | Vulnerability · Source |
| CVE-2025-40074 | suse_vex | SUSE CVE CVE-2025-40074 | known affected: 692 known not affected: 36 recommended: 501 | 2026-10-16T00:54:13+00:00 | Vulnerability · Source |
| CVE-2025-40085 | suse_vex | SUSE CVE CVE-2025-40085 | known affected: 524 known not affected: 256 recommended: 501 | 2026-10-16T00:54:10+00:00 | Vulnerability · Source |
| CVE-2025-40120 | suse_vex | SUSE CVE CVE-2025-40120 | known affected: 524 known not affected: 260 recommended: 495 | 2026-10-16T00:54:06+00:00 | Vulnerability · Source |
| CVE-2025-40153 | suse_vex | SUSE CVE CVE-2025-40153 | known affected: 768 recommended: 434 | 2026-10-16T00:54:03+00:00 | Vulnerability · Source |
| CVE-2025-40170 | suse_vex | SUSE CVE CVE-2025-40170 | known affected: 734 known not affected: 36 recommended: 541 | 2026-10-16T00:54:00+00:00 | Vulnerability · Source |
| CVE-2025-40180 | suse_vex | SUSE CVE CVE-2025-40180 | known affected: 591 known not affected: 187 recommended: 495 | 2026-10-16T00:53:58+00:00 | Vulnerability · Source |
| CVE-2025-40212 | suse_vex | SUSE CVE CVE-2025-40212 | known affected: 396 known not affected: 509 recommended: 215 | 2026-10-16T00:53:54+00:00 | Vulnerability · Source |
| CVE-2025-40220 | suse_vex | SUSE CVE CVE-2025-40220 | known affected: 593 recommended: 652 | 2026-10-16T00:53:51+00:00 | Vulnerability · Source |
| CVE-2025-40251 | suse_vex | SUSE CVE CVE-2025-40251 | known affected: 609 known not affected: 260 recommended: 403 | 2026-10-16T00:53:48+00:00 | Vulnerability · Source |
| CVE-2025-43216 | suse_vex | SUSE CVE CVE-2025-43216 | known affected: 195 known not affected: 105 recommended: 584 | 2026-10-16T00:53:42+00:00 | Vulnerability · Source |
| CVE-2025-43265 | suse_vex | SUSE CVE CVE-2025-43265 | known affected: 195 known not affected: 105 recommended: 584 | 2026-10-16T00:53:40+00:00 | Vulnerability · Source |
| CVE-2025-43343 | suse_vex | SUSE CVE CVE-2025-43343 | known affected: 237 recommended: 582 | 2026-10-16T00:53:37+00:00 | Vulnerability · Source |
| CVE-2025-43962 | suse_vex | SUSE CVE CVE-2025-43962 | known affected: 34 recommended: 51 | 2026-10-16T00:53:34+00:00 | Vulnerability · Source |
| CVE-2025-46404 | suse_vex | SUSE CVE CVE-2025-46404 | known affected: 12 recommended: 56 | 2026-10-16T00:53:31+00:00 | Vulnerability · Source |
| CVE-2025-47281 | suse_vex | SUSE CVE CVE-2025-47281 | recommended: 5 | 2026-10-16T00:53:28+00:00 | Vulnerability · Source |
| CVE-2025-52886 | suse_vex | SUSE CVE CVE-2025-52886 | known affected: 160 recommended: 286 | 2026-10-16T00:53:22+00:00 | Vulnerability · Source |
| CVE-2025-52894 | suse_vex | SUSE CVE CVE-2025-52894 | recommended: 13 | 2026-10-16T00:53:19+00:00 | Vulnerability · Source |
| CVE-2025-54469 | suse_vex | SUSE CVE CVE-2025-54469 | recommended: 3 | 2026-10-16T00:53:15+00:00 | Vulnerability · Source |
| CVE-2025-54571 | suse_vex | SUSE CVE CVE-2025-54571 | known affected: 48 recommended: 16 | 2026-10-16T00:53:12+00:00 | Vulnerability · Source |
| CVE-2025-59410 | suse_vex | SUSE CVE CVE-2025-59410 | recommended: 3 | 2026-10-16T00:53:05+00:00 | Vulnerability · Source |
| CVE-2025-59956 | suse_vex | SUSE CVE CVE-2025-59956 | recommended: 3 | 2026-10-16T00:53:01+00:00 | Vulnerability · Source |
| CVE-2025-60019 | suse_vex | SUSE CVE CVE-2025-60019 | known affected: 0 known not affected: 120 | 2026-10-16T00:52:58+00:00 | Vulnerability · Source |
| CVE-2025-61725 | suse_vex | SUSE CVE CVE-2025-61725 | known affected: 126 known not affected: 77 recommended: 277 | 2026-10-16T00:52:55+00:00 | Vulnerability · Source |
| CVE-2025-61912 | suse_vex | SUSE CVE CVE-2025-61912 | known affected: 28 recommended: 16 | 2026-10-16T00:52:53+00:00 | Vulnerability · Source |
| CVE-2025-62156 | suse_vex | SUSE CVE CVE-2025-62156 | recommended: 3 | 2026-10-16T00:52:50+00:00 | Vulnerability · Source |
| CVE-2025-62506 | suse_vex | SUSE CVE CVE-2025-62506 | recommended: 3 | 2026-10-16T00:52:47+00:00 | Vulnerability · Source |
| CVE-2025-62877 | suse_vex | SUSE CVE CVE-2025-62877 | recommended: 2 | 2026-10-16T00:52:45+00:00 | Vulnerability · Source |
| CVE-2025-64103 | suse_vex | SUSE CVE CVE-2025-64103 | recommended: 3 | 2026-10-16T00:52:43+00:00 | Vulnerability · Source |
| CVE-2025-64522 | suse_vex | SUSE CVE CVE-2025-64522 | recommended: 2 | 2026-10-16T00:52:38+00:00 | Vulnerability · Source |
| CVE-2025-64719 | suse_vex | SUSE CVE CVE-2025-64719 | recommended: 2 | 2026-10-16T00:52:35+00:00 | Vulnerability · Source |
| CVE-2025-65105 | suse_vex | SUSE CVE CVE-2025-65105 | known affected: 4 recommended: 32 | 2026-10-16T00:52:33+00:00 | Vulnerability · Source |
| CVE-2025-66038 | suse_vex | SUSE CVE CVE-2025-66038 | known affected: 406 known not affected: 14 recommended: 35 | 2026-10-16T00:52:30+00:00 | Vulnerability · Source |
| CVE-2025-66507 | suse_vex | SUSE CVE CVE-2025-66507 | recommended: 2 | 2026-10-16T00:52:28+00:00 | Vulnerability · Source |
| CVE-2025-68216 | suse_vex | SUSE CVE CVE-2025-68216 | known affected: 0 known not affected: 522 recommended: 58 | 2026-10-16T00:52:24+00:00 | Vulnerability · Source |
| CVE-2025-68231 | suse_vex | SUSE CVE CVE-2025-68231 | known affected: 488 known not affected: 6 | 2026-10-16T00:52:21+00:00 | Vulnerability · Source |