VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
306222 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2025-55191 | suse_vex | SUSE CVE CVE-2025-55191 | recommended: 1 | 2026-10-10T01:45:11+00:00 | Vulnerability · Source |
| CVE-2025-55196 | suse_vex | SUSE CVE CVE-2025-55196 | recommended: 1 | 2026-10-10T01:45:09+00:00 | Vulnerability · Source |
| CVE-2025-55198 | suse_vex | SUSE CVE CVE-2025-55198 | known not affected: 98 recommended: 1 | 2026-10-10T01:45:08+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-10T01:45:06+00:00 | Vulnerability · Source |
| CVE-2025-55315 | suse_vex | SUSE CVE CVE-2025-55315 | recommended: 96 | 2026-10-10T01:45:04+00:00 | Vulnerability · Source |
| CVE-2025-55668 | suse_vex | SUSE CVE CVE-2025-55668 | known affected: 121 known not affected: 464 recommended: 16 | 2026-10-10T01:45:02+00:00 | Vulnerability · Source |
| CVE-2025-55752 | suse_vex | SUSE CVE CVE-2025-55752 | known affected: 515 known not affected: 37 recommended: 515 | 2026-10-10T01:45:00+00:00 | Vulnerability · Source |
| CVE-2025-56760 | suse_vex | SUSE CVE CVE-2025-56760 | recommended: 1 | 2026-10-10T01:44:58+00:00 | Vulnerability · Source |
| CVE-2025-58068 | suse_vex | SUSE CVE CVE-2025-58068 | known affected: 5 recommended: 14 | 2026-10-10T01:44:56+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-10T01:44:53+00:00 | Vulnerability · Source |
| CVE-2025-58188 | suse_vex | SUSE CVE CVE-2025-58188 | known affected: 30 known not affected: 69 recommended: 294 | 2026-10-10T01:44:51+00:00 | Vulnerability · Source |
| CVE-2025-58190 | suse_vex | SUSE CVE CVE-2025-58190 | known affected: 517 known not affected: 1455 recommended: 425 | 2026-10-10T01:44:48+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-10T01:44:46+00:00 | Vulnerability · Source |
| CVE-2025-58445 | suse_vex | SUSE CVE CVE-2025-58445 | recommended: 1 | 2026-10-10T01:44:44+00:00 | Vulnerability · Source |
| CVE-2025-58767 | suse_vex | SUSE CVE CVE-2025-58767 | known affected: 583 known not affected: 196 recommended: 154 | 2026-10-10T01:44:42+00:00 | Vulnerability · Source |
| CVE-2025-59032 | suse_vex | SUSE CVE CVE-2025-59032 | known affected: 149 known not affected: 47 recommended: 201 | 2026-10-10T01:44:40+00:00 | Vulnerability · Source |
| CVE-2025-59044 | suse_vex | SUSE CVE CVE-2025-59044 | known affected: 394 known not affected: 16 recommended: 18 | 2026-10-10T01:44:39+00:00 | Vulnerability · Source |
| CVE-2025-59048 | suse_vex | SUSE CVE CVE-2025-59048 | recommended: 1 | 2026-10-10T01:44:37+00:00 | Vulnerability · Source |
| CVE-2025-59342 | suse_vex | SUSE CVE CVE-2025-59342 | recommended: 1 | 2026-10-10T01:44:35+00:00 | Vulnerability · Source |
| CVE-2025-59346 | suse_vex | SUSE CVE CVE-2025-59346 | recommended: 1 | 2026-10-10T01:44:32+00:00 | Vulnerability · Source |
| CVE-2025-59348 | suse_vex | SUSE CVE CVE-2025-59348 | recommended: 1 | 2026-10-10T01:44:30+00:00 | Vulnerability · Source |
| CVE-2025-59351 | suse_vex | SUSE CVE CVE-2025-59351 | recommended: 1 | 2026-10-10T01:44:28+00:00 | Vulnerability · Source |
| CVE-2025-59352 | suse_vex | SUSE CVE CVE-2025-59352 | recommended: 1 | 2026-10-10T01:44:26+00:00 | Vulnerability · Source |
| CVE-2025-59353 | suse_vex | SUSE CVE CVE-2025-59353 | recommended: 1 | 2026-10-10T01:44:24+00:00 | Vulnerability · Source |
| CVE-2025-59354 | suse_vex | SUSE CVE CVE-2025-59354 | recommended: 1 | 2026-10-10T01:44:22+00:00 | Vulnerability · Source |
| CVE-2025-59358 | suse_vex | SUSE CVE CVE-2025-59358 | recommended: 1 | 2026-10-10T01:44:20+00:00 | Vulnerability · Source |
| CVE-2025-59359 | suse_vex | SUSE CVE CVE-2025-59359 | recommended: 1 | 2026-10-10T01:44:17+00:00 | Vulnerability · Source |
| CVE-2025-59361 | suse_vex | SUSE CVE CVE-2025-59361 | recommended: 1 | 2026-10-10T01:44:15+00:00 | Vulnerability · Source |
| CVE-2025-59362 | suse_vex | SUSE CVE CVE-2025-59362 | known affected: 415 recommended: 33 | 2026-10-10T01:44:13+00:00 | Vulnerability · Source |
| CVE-2025-59410 | suse_vex | SUSE CVE CVE-2025-59410 | recommended: 1 | 2026-10-10T01:44:12+00:00 | Vulnerability · Source |
| CVE-2025-59529 | suse_vex | SUSE CVE CVE-2025-59529 | known affected: 1055 recommended: 252 | 2026-10-10T01:44:10+00:00 | Vulnerability · Source |
| CVE-2025-59531 | suse_vex | SUSE CVE CVE-2025-59531 | recommended: 1 | 2026-10-10T01:44:08+00:00 | Vulnerability · Source |
| CVE-2025-59537 | suse_vex | SUSE CVE CVE-2025-59537 | recommended: 1 | 2026-10-10T01:44:07+00:00 | Vulnerability · Source |
| CVE-2025-59729 | suse_vex | SUSE CVE CVE-2025-59729 | known not affected: 794 | 2026-10-10T01:44:05+00:00 | Vulnerability · Source |
| CVE-2025-59731 | suse_vex | SUSE CVE CVE-2025-59731 | known affected: 73 known not affected: 741 | 2026-10-10T01:44:03+00:00 | Vulnerability · Source |
| CVE-2025-59732 | suse_vex | SUSE CVE CVE-2025-59732 | known affected: 73 known not affected: 741 | 2026-10-10T01:44:01+00:00 | Vulnerability · Source |
| CVE-2025-59734 | suse_vex | SUSE CVE CVE-2025-59734 | known not affected: 794 | 2026-10-10T01:44:00+00:00 | Vulnerability · Source |
| CVE-2025-59775 | suse_vex | SUSE CVE CVE-2025-59775 | known affected: 394 known not affected: 289 recommended: 29 | 2026-10-10T01:43:58+00:00 | Vulnerability · Source |
| CVE-2025-59777 | suse_vex | SUSE CVE CVE-2025-59777 | known not affected: 132 recommended: 29 | 2026-10-10T01:43:56+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-10T01:43:54+00:00 | Vulnerability · Source |
| CVE-2025-59823 | suse_vex | SUSE CVE CVE-2025-59823 | recommended: 1 | 2026-10-10T01:43:52+00:00 | Vulnerability · Source |
| CVE-2025-59836 | suse_vex | SUSE CVE CVE-2025-59836 | recommended: 1 | 2026-10-10T01:43:51+00:00 | Vulnerability · Source |
| CVE-2025-59937 | suse_vex | SUSE CVE CVE-2025-59937 | recommended: 1 | 2026-10-10T01:43:49+00:00 | Vulnerability · Source |
| CVE-2025-59942 | suse_vex | SUSE CVE CVE-2025-59942 | recommended: 1 | 2026-10-10T01:43:48+00:00 | Vulnerability · Source |
| CVE-2025-60753 | suse_vex | SUSE CVE CVE-2025-60753 | known affected: 506 recommended: 62 | 2026-10-10T01:43:46+00:00 | Vulnerability · Source |
| CVE-2025-60876 | suse_vex | SUSE CVE CVE-2025-60876 | known affected: 35 recommended: 115 | 2026-10-10T01:43: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-10T01:43:42+00:00 | Vulnerability · Source |