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-54997 | suse_vex | SUSE CVE CVE-2025-54997 | recommended: 4 | 2026-10-15T16:03:06+00:00 | Vulnerability · Source |
| CVE-2025-55005 | suse_vex | SUSE CVE CVE-2025-55005 | known affected: 149 known not affected: 8 recommended: 303 | 2026-10-15T16:03:05+00:00 | Vulnerability · Source |
| CVE-2025-55070 | suse_vex | SUSE CVE CVE-2025-55070 | No product status | 2026-10-15T16:03:03+00:00 | Vulnerability · Source |
| CVE-2025-55074 | suse_vex | SUSE CVE CVE-2025-55074 | No product status | 2026-10-15T16:03:02+00:00 | Vulnerability · Source |
| CVE-2025-55130 | suse_vex | SUSE CVE CVE-2025-55130 | known affected: 24 known not affected: 226 recommended: 132 | 2026-10-15T16:03:00+00:00 | Vulnerability · Source |
| CVE-2025-55154 | suse_vex | SUSE CVE CVE-2025-55154 | known affected: 149 known not affected: 1 recommended: 342 | 2026-10-15T16:02:59+00:00 | Vulnerability · Source |
| CVE-2025-55160 | suse_vex | SUSE CVE CVE-2025-55160 | known affected: 149 recommended: 318 | 2026-10-15T16:02:57+00:00 | Vulnerability · Source |
| CVE-2025-55190 | suse_vex | SUSE CVE CVE-2025-55190 | recommended: 1 | 2026-10-15T16:02:55+00:00 | Vulnerability · Source |
| CVE-2025-55191 | suse_vex | SUSE CVE CVE-2025-55191 | recommended: 1 | 2026-10-15T16:02:54+00:00 | Vulnerability · Source |
| CVE-2025-55198 | suse_vex | SUSE CVE CVE-2025-55198 | known not affected: 98 recommended: 1 | 2026-10-15T16:02:52+00:00 | Vulnerability · Source |
| CVE-2025-55212 | suse_vex | SUSE CVE CVE-2025-55212 | known affected: 149 known not affected: 24 recommended: 340 | 2026-10-15T16:02:51+00:00 | Vulnerability · Source |
| CVE-2025-55304 | suse_vex | SUSE CVE CVE-2025-55304 | known affected: 139 known not affected: 33 recommended: 23 | 2026-10-15T16:02:49+00:00 | Vulnerability · Source |
| CVE-2025-55754 | suse_vex | SUSE CVE CVE-2025-55754 | known affected: 551 recommended: 509 | 2026-10-15T16:02:47+00:00 | Vulnerability · Source |
| CVE-2025-56760 | suse_vex | SUSE CVE CVE-2025-56760 | recommended: 1 | 2026-10-15T16:02:46+00:00 | Vulnerability · Source |
| CVE-2025-56761 | suse_vex | SUSE CVE CVE-2025-56761 | recommended: 1 | 2026-10-15T16:02:44+00:00 | Vulnerability · Source |
| CVE-2025-58058 | suse_vex | SUSE CVE CVE-2025-58058 | known affected: 81 known not affected: 284 recommended: 115 | 2026-10-15T16:02:43+00:00 | Vulnerability · Source |
| CVE-2025-58063 | suse_vex | SUSE CVE CVE-2025-58063 | recommended: 11 | 2026-10-15T16:02:41+00:00 | Vulnerability · Source |
| CVE-2025-58143 | suse_vex | SUSE CVE CVE-2025-58143 | known affected: 432 known not affected: 125 recommended: 179 | 2026-10-15T16:02:39+00:00 | Vulnerability · Source |
| CVE-2025-58148 | suse_vex | SUSE CVE CVE-2025-58148 | known not affected: 184 recommended: 129 | 2026-10-15T16:02:38+00:00 | Vulnerability · Source |
| CVE-2025-58181 | suse_vex | SUSE CVE CVE-2025-58181 | known affected: 1115 known not affected: 256 recommended: 508 | 2026-10-15T16:02:34+00:00 | Vulnerability · Source |
| CVE-2025-58185 | suse_vex | SUSE CVE CVE-2025-58185 | known affected: 30 known not affected: 69 recommended: 295 | 2026-10-15T16:02:32+00:00 | Vulnerability · Source |
| CVE-2025-58187 | suse_vex | SUSE CVE CVE-2025-58187 | known affected: 42 known not affected: 93 recommended: 294 | 2026-10-15T16:02:31+00:00 | Vulnerability · Source |
| CVE-2025-58356 | suse_vex | SUSE CVE CVE-2025-58356 | recommended: 1 | 2026-10-15T16:02:27+00:00 | Vulnerability · Source |
| CVE-2025-58436 | suse_vex | SUSE CVE CVE-2025-58436 | known affected: 714 known not affected: 137 recommended: 210 | 2026-10-15T16:02:26+00:00 | Vulnerability · Source |
| CVE-2025-58450 | suse_vex | SUSE CVE CVE-2025-58450 | recommended: 1 | 2026-10-15T16:02:24+00:00 | Vulnerability · Source |
| CVE-2025-59028 | suse_vex | SUSE CVE CVE-2025-59028 | known not affected: 222 recommended: 163 | 2026-10-15T16:02:22+00:00 | Vulnerability · Source |
| CVE-2025-59031 | suse_vex | SUSE CVE CVE-2025-59031 | known affected: 149 known not affected: 47 recommended: 181 | 2026-10-15T16:02:20+00:00 | Vulnerability · Source |
| CVE-2025-59163 | suse_vex | SUSE CVE CVE-2025-59163 | recommended: 1 | 2026-10-15T16:02:18+00:00 | Vulnerability · Source |
| CVE-2025-59341 | suse_vex | SUSE CVE CVE-2025-59341 | recommended: 1 | 2026-10-15T16:02:17+00:00 | Vulnerability · Source |
| CVE-2025-59342 | suse_vex | SUSE CVE CVE-2025-59342 | recommended: 1 | 2026-10-15T16:02:15+00:00 | Vulnerability · Source |
| CVE-2025-59343 | suse_vex | SUSE CVE CVE-2025-59343 | known affected: 135 known not affected: 343 recommended: 4 | 2026-10-15T16:02:14+00:00 | Vulnerability · Source |
| CVE-2025-59353 | suse_vex | SUSE CVE CVE-2025-59353 | recommended: 1 | 2026-10-15T16:02:12+00:00 | Vulnerability · Source |
| CVE-2025-59354 | suse_vex | SUSE CVE CVE-2025-59354 | recommended: 1 | 2026-10-15T16:02:10+00:00 | Vulnerability · Source |
| CVE-2025-59360 | suse_vex | SUSE CVE CVE-2025-59360 | recommended: 1 | 2026-10-15T16:02:09+00:00 | Vulnerability · Source |
| CVE-2025-59361 | suse_vex | SUSE CVE CVE-2025-59361 | recommended: 1 | 2026-10-15T16:02:07+00:00 | Vulnerability · Source |
| CVE-2025-59375 | suse_vex | SUSE CVE CVE-2025-59375 | known affected: 494 recommended: 358 | 2026-10-15T16:02:05+00:00 | Vulnerability · Source |
| CVE-2025-59438 | suse_vex | SUSE CVE CVE-2025-59438 | known not affected: 1996 recommended: 119 | 2026-10-15T16:02:04+00:00 | Vulnerability · Source |
| CVE-2025-59464 | suse_vex | SUSE CVE CVE-2025-59464 | known not affected: 322 recommended: 41 | 2026-10-15T16:02:01+00:00 | Vulnerability · Source |
| CVE-2025-59531 | suse_vex | SUSE CVE CVE-2025-59531 | recommended: 1 | 2026-10-15T16:02:00+00:00 | Vulnerability · Source |
| CVE-2025-59537 | suse_vex | SUSE CVE CVE-2025-59537 | recommended: 1 | 2026-10-15T16:01:58+00:00 | Vulnerability · Source |
| CVE-2025-59538 | suse_vex | SUSE CVE CVE-2025-59538 | recommended: 1 | 2026-10-15T16:01:57+00:00 | Vulnerability · Source |
| CVE-2025-59729 | suse_vex | SUSE CVE CVE-2025-59729 | known not affected: 794 | 2026-10-15T16:01:55+00:00 | Vulnerability · Source |
| CVE-2025-59733 | suse_vex | SUSE CVE CVE-2025-59733 | known affected: 73 known not affected: 739 | 2026-10-15T16:01:53+00:00 | Vulnerability · Source |
| CVE-2025-59798 | suse_vex | SUSE CVE CVE-2025-59798 | known affected: 40 known not affected: 94 recommended: 53 | 2026-10-15T16:01:52+00:00 | Vulnerability · Source |
| CVE-2025-59799 | suse_vex | SUSE CVE CVE-2025-59799 | known affected: 40 known not affected: 94 recommended: 53 | 2026-10-15T16:01:50+00:00 | Vulnerability · Source |
| CVE-2025-59800 | suse_vex | SUSE CVE CVE-2025-59800 | known affected: 1 known not affected: 162 recommended: 14 | 2026-10-15T16:01:48+00:00 | Vulnerability · Source |
| CVE-2025-59823 | suse_vex | SUSE CVE CVE-2025-59823 | recommended: 1 | 2026-10-15T16:01:47+00:00 | Vulnerability · Source |
| CVE-2025-59836 | suse_vex | SUSE CVE CVE-2025-59836 | recommended: 1 | 2026-10-15T16:01:45+00:00 | Vulnerability · Source |
| CVE-2025-60633 | suse_vex | SUSE CVE CVE-2025-60633 | No product status | 2026-10-15T16:01:44+00:00 | Vulnerability · Source |
| CVE-2025-61100 | suse_vex | SUSE CVE CVE-2025-61100 | known affected: 267 known not affected: 335 recommended: 111 | 2026-10-15T16:01:42+00:00 | Vulnerability · Source |