VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292225 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-11232 | suse_vex | SUSE CVE CVE-2025-11232 | known not affected: 359 recommended: 155 | 2026-07-17T13:17:12+00:00 | Vulnerability · Source |
| CVE-2025-11687 | suse_vex | SUSE CVE CVE-2025-11687 | known affected: 3 recommended: 6 | 2026-07-17T13:17:08+00:00 | Vulnerability · Source |
| CVE-2025-15275 | suse_vex | SUSE CVE CVE-2025-15275 | known affected: 7 recommended: 34 | 2026-07-17T13:16:51+00:00 | Vulnerability · Source |
| CVE-2025-15570 | suse_vex | SUSE CVE CVE-2025-15570 | recommended: 2 | 2026-07-17T13:16:47+00:00 | Vulnerability · Source |
| CVE-2025-20086 | suse_vex | SUSE CVE CVE-2025-20086 | recommended: 3 | 2026-07-17T13:16:46+00:00 | Vulnerability · Source |
| CVE-2025-21779 | suse_vex | SUSE CVE CVE-2025-21779 | known affected: 588 known not affected: 104 recommended: 388 | 2026-07-17T13:16:06+00:00 | Vulnerability · Source |
| CVE-2025-21848 | suse_vex | SUSE CVE CVE-2025-21848 | known affected: 598 known not affected: 52 recommended: 462 | 2026-07-17T13:15:49+00:00 | Vulnerability · Source |
| CVE-2025-21963 | suse_vex | SUSE CVE CVE-2025-21963 | known affected: 628 known not affected: 69 recommended: 487 | 2026-07-17T13:15:02+00:00 | Vulnerability · Source |
| CVE-2025-22866 | suse_vex | SUSE CVE CVE-2025-22866 | known affected: 78 known not affected: 79 recommended: 245 | 2026-07-17T13:14:34+00:00 | Vulnerability · Source |
| CVE-2025-24787 | suse_vex | SUSE CVE CVE-2025-24787 | recommended: 3 | 2026-07-17T13:14:08+00:00 | Vulnerability · Source |
| CVE-2025-24806 | suse_vex | SUSE CVE CVE-2025-24806 | recommended: 3 | 2026-07-17T13:14:06+00:00 | Vulnerability · Source |
| CVE-2025-25068 | suse_vex | SUSE CVE CVE-2025-25068 | recommended: 3 | 2026-07-17T13:14:05+00:00 | Vulnerability · Source |
| CVE-2025-27151 | suse_vex | SUSE CVE CVE-2025-27151 | known not affected: 23 recommended: 56 | 2026-07-17T13:13:57+00:00 | Vulnerability · Source |
| CVE-2025-27616 | suse_vex | SUSE CVE CVE-2025-27616 | recommended: 3 | 2026-07-17T13:13:51+00:00 | Vulnerability · Source |
| CVE-2025-27715 | suse_vex | SUSE CVE CVE-2025-27715 | recommended: 3 | 2026-07-17T13:13:50+00:00 | Vulnerability · Source |
| CVE-2025-30077 | suse_vex | SUSE CVE CVE-2025-30077 | recommended: 3 | 2026-07-17T13:13:44+00:00 | Vulnerability · Source |
| CVE-2025-30086 | suse_vex | SUSE CVE CVE-2025-30086 | recommended: 3 | 2026-07-17T13:13:42+00:00 | Vulnerability · Source |
| CVE-2025-30206 | suse_vex | SUSE CVE CVE-2025-30206 | recommended: 3 | 2026-07-17T13:13:40+00:00 | Vulnerability · Source |
| CVE-2025-32024 | suse_vex | SUSE CVE CVE-2025-32024 | recommended: 3 | 2026-07-17T13:13:36+00:00 | Vulnerability · Source |
| CVE-2025-32441 | suse_vex | SUSE CVE CVE-2025-32441 | known affected: 416 known not affected: 10 recommended: 93 | 2026-07-17T13:13:29+00:00 | Vulnerability · Source |
| CVE-2025-38040 | suse_vex | SUSE CVE CVE-2025-38040 | known affected: 623 known not affected: 80 recommended: 430 | 2026-07-17T13:12:03+00:00 | Vulnerability · Source |
| CVE-2025-38064 | suse_vex | SUSE CVE CVE-2025-38064 | known affected: 695 known not affected: 2 recommended: 430 | 2026-07-17T13:11:54+00:00 | Vulnerability · Source |
| CVE-2025-38147 | suse_vex | SUSE CVE CVE-2025-38147 | known affected: 669 known not affected: 22 recommended: 430 | 2026-07-17T13:11:23+00:00 | Vulnerability · Source |
| CVE-2025-38569 | suse_vex | SUSE CVE CVE-2025-38569 | first fixed: 2 known not affected: 446 recommended: 172 | 2026-07-17T13:09:45+00:00 | Vulnerability · Source |
| CVE-2025-38637 | suse_vex | SUSE CVE CVE-2025-38637 | known affected: 624 known not affected: 52 recommended: 434 | 2026-07-17T13:09:23+00:00 | Vulnerability · Source |
| CVE-2025-39700 | suse_vex | SUSE CVE CVE-2025-39700 | first fixed: 2 known not affected: 408 recommended: 154 | 2026-07-17T13:08:51+00:00 | Vulnerability · Source |
| CVE-2025-39926 | suse_vex | SUSE CVE CVE-2025-39926 | first fixed: 2 known affected: 5 known not affected: 433 recommended: 154 | 2026-07-17T13:07:35+00:00 | Vulnerability · Source |
| CVE-2025-40122 | suse_vex | SUSE CVE CVE-2025-40122 | known not affected: 406 recommended: 27 | 2026-07-17T13:06:43+00:00 | Vulnerability · Source |
| CVE-2025-40132 | suse_vex | SUSE CVE CVE-2025-40132 | first fixed: 2 known affected: 394 known not affected: 346 recommended: 265 | 2026-07-17T13:06:40+00:00 | Vulnerability · Source |
| CVE-2025-40779 | suse_vex | SUSE CVE CVE-2025-40779 | known not affected: 453 recommended: 150 | 2026-07-17T13:05:46+00:00 | Vulnerability · Source |
| CVE-2025-41423 | suse_vex | SUSE CVE CVE-2025-41423 | recommended: 3 | 2026-07-17T13:05:43+00:00 | Vulnerability · Source |
| CVE-2025-44779 | suse_vex | SUSE CVE CVE-2025-44779 | recommended: 3 | 2026-07-17T13:05:29+00:00 | Vulnerability · Source |
| CVE-2025-46817 | suse_vex | SUSE CVE CVE-2025-46817 | known affected: 2 known not affected: 7 recommended: 85 | 2026-07-17T13:05:25+00:00 | Vulnerability · Source |
| CVE-2025-48072 | suse_vex | SUSE CVE CVE-2025-48072 | known not affected: 142 recommended: 30 | 2026-07-17T13:05:17+00:00 | Vulnerability · Source |
| CVE-2025-48374 | suse_vex | SUSE CVE CVE-2025-48374 | recommended: 3 | 2026-07-17T13:05:15+00:00 | Vulnerability · Source |
| CVE-2025-49136 | suse_vex | SUSE CVE CVE-2025-49136 | recommended: 3 | 2026-07-17T13:05:10+00:00 | Vulnerability · Source |
| CVE-2025-50949 | suse_vex | SUSE CVE CVE-2025-50949 | known affected: 16 recommended: 29 | 2026-07-17T13:05:00+00:00 | Vulnerability · Source |
| CVE-2025-52893 | suse_vex | SUSE CVE CVE-2025-52893 | recommended: 11 | 2026-07-17T13:04:57+00:00 | Vulnerability · Source |
| CVE-2025-52894 | suse_vex | SUSE CVE CVE-2025-52894 | recommended: 11 | 2026-07-17T13:04:55+00:00 | Vulnerability · Source |
| CVE-2025-52900 | suse_vex | SUSE CVE CVE-2025-52900 | recommended: 3 | 2026-07-17T13:04:54+00:00 | Vulnerability · Source |
| CVE-2025-53816 | suse_vex | SUSE CVE CVE-2025-53816 | known not affected: 18 recommended: 6 | 2026-07-17T13:04:49+00:00 | Vulnerability · Source |
| CVE-2025-54059 | suse_vex | SUSE CVE CVE-2025-54059 | recommended: 3 | 2026-07-17T13:04:45+00:00 | Vulnerability · Source |
| CVE-2025-54576 | suse_vex | SUSE CVE CVE-2025-54576 | recommended: 3 | 2026-07-17T13:04:37+00:00 | Vulnerability · Source |
| CVE-2025-54801 | suse_vex | SUSE CVE CVE-2025-54801 | recommended: 3 | 2026-07-17T13:04:36+00:00 | Vulnerability · Source |
| CVE-2025-55131 | suse_vex | SUSE CVE CVE-2025-55131 | known affected: 163 recommended: 126 | 2026-07-17T13:04:33+00:00 | Vulnerability · Source |
| CVE-2025-57052 | suse_vex | SUSE CVE CVE-2025-57052 | recommended: 11 | 2026-07-17T13:04:29+00:00 | Vulnerability · Source |
| CVE-2025-59031 | suse_vex | SUSE CVE CVE-2025-59031 | known affected: 215 known not affected: 34 recommended: 51 | 2026-07-17T13:04:20+00:00 | Vulnerability · Source |
| CVE-2025-61103 | suse_vex | SUSE CVE CVE-2025-61103 | known affected: 233 recommended: 112 | 2026-07-17T13:04:14+00:00 | Vulnerability · Source |
| CVE-2025-61106 | suse_vex | SUSE CVE CVE-2025-61106 | known affected: 233 recommended: 112 | 2026-07-17T13:04:12+00:00 | Vulnerability · Source |
| CVE-2025-62725 | suse_vex | SUSE CVE CVE-2025-62725 | recommended: 8 | 2026-07-17T13:04:01+00:00 | Vulnerability · Source |