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-61102 | suse_vex | SUSE CVE CVE-2025-61102 | known affected: 267 known not affected: 335 recommended: 101 | 2026-10-15T16:01:40+00:00 | Vulnerability · Source |
| CVE-2025-61103 | suse_vex | SUSE CVE CVE-2025-61103 | known affected: 267 recommended: 101 | 2026-10-15T16:01:38+00:00 | Vulnerability · Source |
| CVE-2025-61104 | suse_vex | SUSE CVE CVE-2025-61104 | known affected: 267 recommended: 111 | 2026-10-15T16:01:37+00:00 | Vulnerability · Source |
| CVE-2025-61105 | suse_vex | SUSE CVE CVE-2025-61105 | known affected: 267 known not affected: 335 recommended: 101 | 2026-10-15T16:01:35+00:00 | Vulnerability · Source |
| CVE-2025-61106 | suse_vex | SUSE CVE CVE-2025-61106 | known affected: 267 recommended: 101 | 2026-10-15T16:01:34+00:00 | Vulnerability · Source |
| CVE-2025-61107 | suse_vex | SUSE CVE CVE-2025-61107 | known affected: 267 recommended: 101 | 2026-10-15T16:01:32+00:00 | Vulnerability · Source |
| CVE-2025-61524 | suse_vex | SUSE CVE CVE-2025-61524 | recommended: 1 | 2026-10-15T16:01:30+00:00 | Vulnerability · Source |
| CVE-2025-61581 | suse_vex | SUSE CVE CVE-2025-61581 | recommended: 1 | 2026-10-15T16:01:28+00:00 | Vulnerability · Source |
| CVE-2025-61594 | suse_vex | SUSE CVE CVE-2025-61594 | known not affected: 246 recommended: 131 | 2026-10-15T16:01:26+00:00 | Vulnerability · Source |
| CVE-2025-61661 | suse_vex | SUSE CVE CVE-2025-61661 | known affected: 734 recommended: 284 | 2026-10-15T16:01:24+00:00 | Vulnerability · Source |
| CVE-2025-61663 | suse_vex | SUSE CVE CVE-2025-61663 | known affected: 734 recommended: 284 | 2026-10-15T16:01:21+00:00 | Vulnerability · Source |
| CVE-2025-61688 | suse_vex | SUSE CVE CVE-2025-61688 | recommended: 1 | 2026-10-15T16:01:19+00:00 | Vulnerability · Source |
| CVE-2025-61728 | suse_vex | SUSE CVE CVE-2025-61728 | known affected: 48 known not affected: 61 recommended: 355 | 2026-10-15T16:01:16+00:00 | Vulnerability · Source |
| CVE-2025-61729 | suse_vex | SUSE CVE CVE-2025-61729 | known not affected: 296 recommended: 416 | 2026-10-15T16:01:14+00:00 | Vulnerability · Source |
| CVE-2025-61732 | suse_vex | SUSE CVE CVE-2025-61732 | known affected: 36 known not affected: 121 recommended: 285 | 2026-10-15T16:01:12+00:00 | Vulnerability · Source |
| CVE-2025-61748 | suse_vex | SUSE CVE CVE-2025-61748 | known affected: 394 known not affected: 567 recommended: 342 | 2026-10-15T16:01:09+00:00 | Vulnerability · Source |
| CVE-2025-61795 | suse_vex | SUSE CVE CVE-2025-61795 | known affected: 551 recommended: 517 | 2026-10-15T16:01:07+00:00 | Vulnerability · Source |
| CVE-2025-61911 | suse_vex | SUSE CVE CVE-2025-61911 | known affected: 28 recommended: 15 | 2026-10-15T16:01:04+00:00 | Vulnerability · Source |
| CVE-2025-61962 | suse_vex | SUSE CVE CVE-2025-61962 | known affected: 85 recommended: 33 | 2026-10-15T16:01:02+00:00 | Vulnerability · Source |
| CVE-2025-62155 | suse_vex | SUSE CVE CVE-2025-62155 | No product status | 2026-10-15T16:00:57+00:00 | Vulnerability · Source |
| CVE-2025-62168 | suse_vex | SUSE CVE CVE-2025-62168 | known affected: 29 recommended: 40 | 2026-10-15T16:00:55+00:00 | Vulnerability · Source |
| CVE-2025-62190 | suse_vex | SUSE CVE CVE-2025-62190 | No product status | 2026-10-15T16:00:53+00:00 | Vulnerability · Source |
| CVE-2025-62229 | suse_vex | SUSE CVE CVE-2025-62229 | known affected: 438 known not affected: 9 recommended: 196 | 2026-10-15T16:00:51+00:00 | Vulnerability · Source |
| CVE-2025-62230 | suse_vex | SUSE CVE CVE-2025-62230 | known affected: 447 recommended: 196 | 2026-10-15T16:00:50+00:00 | Vulnerability · Source |
| CVE-2025-62291 | suse_vex | SUSE CVE CVE-2025-62291 | known not affected: 106 recommended: 198 | 2026-10-15T16:00:47+00:00 | Vulnerability · Source |
| CVE-2025-62375 | suse_vex | SUSE CVE CVE-2025-62375 | recommended: 1 | 2026-10-15T16:00:44+00:00 | Vulnerability · Source |
| CVE-2025-62408 | suse_vex | SUSE CVE CVE-2025-62408 | known affected: 394 known not affected: 80 recommended: 105 | 2026-10-15T16:00:42+00:00 | Vulnerability · Source |
| CVE-2025-62689 | suse_vex | SUSE CVE CVE-2025-62689 | known not affected: 132 recommended: 29 | 2026-10-15T16:00:39+00:00 | Vulnerability · Source |
| CVE-2025-62690 | suse_vex | SUSE CVE CVE-2025-62690 | No product status | 2026-10-15T16:00:37+00:00 | Vulnerability · Source |
| CVE-2025-62705 | suse_vex | SUSE CVE CVE-2025-62705 | recommended: 9 | 2026-10-15T16:00:35+00:00 | Vulnerability · Source |
| CVE-2025-62725 | suse_vex | SUSE CVE CVE-2025-62725 | recommended: 8 | 2026-10-15T16:00:33+00:00 | Vulnerability · Source |
| CVE-2025-63389 | suse_vex | SUSE CVE CVE-2025-63389 | known not affected: 4 | 2026-10-15T16:00:30+00:00 | Vulnerability · Source |
| CVE-2025-64031 | suse_vex | SUSE CVE CVE-2025-64031 | known affected: 11 known not affected: 193 | 2026-10-15T16:00:28+00:00 | Vulnerability · Source |
| CVE-2025-64101 | suse_vex | SUSE CVE CVE-2025-64101 | recommended: 1 | 2026-10-15T16:00:27+00:00 | Vulnerability · Source |
| CVE-2025-64102 | suse_vex | SUSE CVE CVE-2025-64102 | recommended: 1 | 2026-10-15T16:00:25+00:00 | Vulnerability · Source |
| CVE-2025-64171 | suse_vex | SUSE CVE CVE-2025-64171 | No product status | 2026-10-15T16:00:24+00:00 | Vulnerability · Source |
| CVE-2025-64175 | suse_vex | SUSE CVE CVE-2025-64175 | No product status | 2026-10-15T16:00:21+00:00 | Vulnerability · Source |
| CVE-2025-64178 | suse_vex | SUSE CVE CVE-2025-64178 | No product status | 2026-10-15T16:00:20+00:00 | Vulnerability · Source |
| CVE-2025-64181 | suse_vex | SUSE CVE CVE-2025-64181 | known not affected: 186 recommended: 67 | 2026-10-15T16:00:18+00:00 | Vulnerability · Source |
| CVE-2025-64183 | suse_vex | SUSE CVE CVE-2025-64183 | known not affected: 186 recommended: 30 | 2026-10-15T16:00:17+00:00 | Vulnerability · Source |
| CVE-2025-64186 | suse_vex | SUSE CVE CVE-2025-64186 | No product status | 2026-10-15T16:00:15+00:00 | Vulnerability · Source |
| CVE-2025-64329 | suse_vex | SUSE CVE CVE-2025-64329 | known affected: 378 recommended: 127 | 2026-10-15T16:00:14+00:00 | Vulnerability · Source |
| CVE-2025-64431 | suse_vex | SUSE CVE CVE-2025-64431 | No product status | 2026-10-15T16:00:12+00:00 | Vulnerability · Source |
| CVE-2025-64436 | suse_vex | SUSE CVE CVE-2025-64436 | known not affected: 90 | 2026-10-15T16:00:08+00:00 | Vulnerability · Source |
| CVE-2025-64506 | suse_vex | SUSE CVE CVE-2025-64506 | known affected: 473 known not affected: 207 recommended: 200 | 2026-10-15T16:00:06+00:00 | Vulnerability · Source |
| CVE-2025-64529 | suse_vex | SUSE CVE CVE-2025-64529 | No product status | 2026-10-15T16:00:04+00:00 | Vulnerability · Source |
| CVE-2025-64708 | suse_vex | SUSE CVE CVE-2025-64708 | No product status | 2026-10-15T16:00:02+00:00 | Vulnerability · Source |
| CVE-2025-64751 | suse_vex | SUSE CVE CVE-2025-64751 | recommended: 21 | 2026-10-15T15:59:59+00:00 | Vulnerability · Source |
| CVE-2025-64761 | suse_vex | SUSE CVE CVE-2025-64761 | recommended: 8 | 2026-10-15T15:59:57+00:00 | Vulnerability · Source |
| CVE-2025-65026 | suse_vex | SUSE CVE CVE-2025-65026 | No product status | 2026-10-15T15:59:55+00:00 | Vulnerability · Source |