VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306221 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-52885 | suse_vex | SUSE CVE CVE-2025-52885 | known affected: 32 known not affected: 132 recommended: 213 | 2026-10-10T01:47:03+00:00 | Vulnerability · Source |
| CVE-2025-52889 | suse_vex | SUSE CVE CVE-2025-52889 | recommended: 9 | 2026-10-10T01:47:00+00:00 | Vulnerability · Source |
| CVE-2025-52890 | suse_vex | SUSE CVE CVE-2025-52890 | recommended: 9 | 2026-10-10T01:46:57+00:00 | Vulnerability · Source |
| CVE-2025-52891 | suse_vex | SUSE CVE CVE-2025-52891 | known not affected: 58 recommended: 4 | 2026-10-10T01:46:54+00:00 | Vulnerability · Source |
| CVE-2025-52900 | suse_vex | SUSE CVE CVE-2025-52900 | recommended: 4 | 2026-10-10T01:46:52+00:00 | Vulnerability · Source |
| CVE-2025-52904 | suse_vex | SUSE CVE CVE-2025-52904 | recommended: 4 | 2026-10-10T01:46:49+00:00 | Vulnerability · Source |
| CVE-2025-52996 | suse_vex | SUSE CVE CVE-2025-52996 | recommended: 4 | 2026-10-10T01:46:47+00:00 | Vulnerability · Source |
| CVE-2025-52999 | suse_vex | SUSE CVE CVE-2025-52999 | known not affected: 43 recommended: 46 | 2026-10-10T01:46:45+00:00 | Vulnerability · Source |
| CVE-2025-53023 | suse_vex | SUSE CVE CVE-2025-53023 | recommended: 25 | 2026-10-10T01:46:43+00:00 | Vulnerability · Source |
| CVE-2025-53066 | suse_vex | SUSE CVE CVE-2025-53066 | known affected: 394 known not affected: 208 recommended: 954 | 2026-10-10T01:46:41+00:00 | Vulnerability · Source |
| CVE-2025-53192 | suse_vex | SUSE CVE CVE-2025-53192 | known affected: 3 recommended: 58 | 2026-10-10T01:46:38+00:00 | Vulnerability · Source |
| CVE-2025-53367 | suse_vex | SUSE CVE CVE-2025-53367 | known affected: 114 recommended: 44 | 2026-10-10T01:46:36+00:00 | Vulnerability · Source |
| CVE-2025-53633 | suse_vex | SUSE CVE CVE-2025-53633 | recommended: 4 | 2026-10-10T01:46:33+00:00 | Vulnerability · Source |
| CVE-2025-53634 | suse_vex | SUSE CVE CVE-2025-53634 | recommended: 4 | 2026-10-10T01:46:30+00:00 | Vulnerability · Source |
| CVE-2025-53816 | suse_vex | SUSE CVE CVE-2025-53816 | known not affected: 19 recommended: 6 | 2026-10-10T01:46:27+00:00 | Vulnerability · Source |
| CVE-2025-53826 | suse_vex | SUSE CVE CVE-2025-53826 | recommended: 4 | 2026-10-10T01:46:25+00:00 | Vulnerability · Source |
| CVE-2025-53884 | suse_vex | SUSE CVE CVE-2025-53884 | recommended: 1 | 2026-10-10T01:46:22+00:00 | Vulnerability · Source |
| CVE-2025-53905 | suse_vex | SUSE CVE CVE-2025-53905 | known affected: 582 recommended: 148 | 2026-10-10T01:46:19+00:00 | Vulnerability · Source |
| CVE-2025-53906 | suse_vex | SUSE CVE CVE-2025-53906 | known affected: 477 recommended: 240 | 2026-10-10T01:46:17+00:00 | Vulnerability · Source |
| CVE-2025-54090 | suse_vex | SUSE CVE CVE-2025-54090 | known not affected: 307 recommended: 1 | 2026-10-10T01:46:13+00:00 | Vulnerability · Source |
| CVE-2025-54286 | suse_vex | SUSE CVE CVE-2025-54286 | recommended: 1 | 2026-10-10T01:46:11+00:00 | Vulnerability · Source |
| CVE-2025-54287 | suse_vex | SUSE CVE CVE-2025-54287 | recommended: 1 | 2026-10-10T01:46:09+00:00 | Vulnerability · Source |
| CVE-2025-54290 | suse_vex | SUSE CVE CVE-2025-54290 | recommended: 1 | 2026-10-10T01:46:07+00:00 | Vulnerability · Source |
| CVE-2025-54291 | suse_vex | SUSE CVE CVE-2025-54291 | recommended: 1 | 2026-10-10T01:46:05+00:00 | Vulnerability · Source |
| CVE-2025-54293 | suse_vex | SUSE CVE CVE-2025-54293 | recommended: 1 | 2026-10-10T01:46:03+00:00 | Vulnerability · Source |
| CVE-2025-54349 | suse_vex | SUSE CVE CVE-2025-54349 | recommended: 27 | 2026-10-10T01:46:00+00:00 | Vulnerability · Source |
| CVE-2025-54351 | suse_vex | SUSE CVE CVE-2025-54351 | recommended: 23 | 2026-10-10T01:45:58+00:00 | Vulnerability · Source |
| CVE-2025-54386 | suse_vex | SUSE CVE CVE-2025-54386 | recommended: 5 | 2026-10-10T01:45:55+00:00 | Vulnerability · Source |
| CVE-2025-54389 | suse_vex | SUSE CVE CVE-2025-54389 | known affected: 4 known not affected: 67 recommended: 8 | 2026-10-10T01:45:53+00:00 | Vulnerability · Source |
| CVE-2025-54410 | suse_vex | SUSE CVE CVE-2025-54410 | known affected: 15 known not affected: 7 recommended: 4 | 2026-10-10T01:45:51+00:00 | Vulnerability · Source |
| CVE-2025-54458 | suse_vex | SUSE CVE CVE-2025-54458 | recommended: 1 | 2026-10-10T01:45:49+00:00 | Vulnerability · Source |
| CVE-2025-54468 | suse_vex | SUSE CVE CVE-2025-54468 | recommended: 1 | 2026-10-10T01:45:47+00:00 | Vulnerability · Source |
| CVE-2025-54471 | suse_vex | SUSE CVE CVE-2025-54471 | recommended: 1 | 2026-10-10T01:45:46+00:00 | Vulnerability · Source |
| CVE-2025-54478 | suse_vex | SUSE CVE CVE-2025-54478 | recommended: 1 | 2026-10-10T01:45:44+00:00 | Vulnerability · Source |
| CVE-2025-54499 | suse_vex | SUSE CVE CVE-2025-54499 | recommended: 1 | 2026-10-10T01:45:42+00:00 | Vulnerability · Source |
| CVE-2025-54518 | suse_vex | SUSE CVE CVE-2025-54518 | known affected: 603 recommended: 878 | 2026-10-10T01:45:40+00:00 | Vulnerability · Source |
| CVE-2025-54567 | suse_vex | SUSE CVE CVE-2025-54567 | known not affected: 1832 recommended: 120 | 2026-10-10T01:45:38+00:00 | Vulnerability · Source |
| CVE-2025-54571 | suse_vex | SUSE CVE CVE-2025-54571 | known affected: 48 recommended: 15 | 2026-10-10T01:45:36+00:00 | Vulnerability · Source |
| CVE-2025-54627 | suse_vex | SUSE CVE CVE-2025-54627 | known affected: 214 | 2026-10-10T01:45:34+00:00 | Vulnerability · Source |
| CVE-2025-54799 | suse_vex | SUSE CVE CVE-2025-54799 | recommended: 4 | 2026-10-10T01:45:32+00:00 | Vulnerability · Source |
| CVE-2025-54998 | suse_vex | SUSE CVE CVE-2025-54998 | recommended: 4 | 2026-10-10T01:45:30+00:00 | Vulnerability · Source |
| CVE-2025-55000 | suse_vex | SUSE CVE CVE-2025-55000 | recommended: 12 | 2026-10-10T01:45:28+00:00 | Vulnerability · Source |
| CVE-2025-55003 | suse_vex | SUSE CVE CVE-2025-55003 | recommended: 12 | 2026-10-10T01:45:26+00:00 | Vulnerability · Source |
| CVE-2025-55004 | suse_vex | SUSE CVE CVE-2025-55004 | known affected: 108 known not affected: 77 recommended: 283 | 2026-10-10T01:45:24+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-10T01:45:23+00:00 | Vulnerability · Source |
| CVE-2025-55131 | suse_vex | SUSE CVE CVE-2025-55131 | known affected: 168 recommended: 196 | 2026-10-10T01:45:20+00:00 | Vulnerability · Source |
| CVE-2025-55132 | suse_vex | SUSE CVE CVE-2025-55132 | known affected: 24 known not affected: 226 recommended: 122 | 2026-10-10T01:45:19+00:00 | Vulnerability · Source |
| CVE-2025-55158 | suse_vex | SUSE CVE CVE-2025-55158 | known affected: 565 known not affected: 1 recommended: 126 | 2026-10-10T01:45:17+00:00 | Vulnerability · Source |
| CVE-2025-55160 | suse_vex | SUSE CVE CVE-2025-55160 | known affected: 149 recommended: 318 | 2026-10-10T01:45:14+00:00 | Vulnerability · Source |
| CVE-2025-55190 | suse_vex | SUSE CVE CVE-2025-55190 | recommended: 1 | 2026-10-10T01:45:13+00:00 | Vulnerability · Source |