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-1795 | suse_vex | SUSE CVE CVE-2025-1795 | known affected: 55 known not affected: 500 recommended: 312 | 2026-10-16T01:11:20+00:00 | Vulnerability · Source |
| CVE-2025-1816 | suse_vex | SUSE CVE CVE-2025-1816 | known affected: 0 known not affected: 673 recommended: 61 | 2026-10-16T01:11:18+00:00 | Vulnerability · Source |
| CVE-2025-1930 | suse_vex | SUSE CVE CVE-2025-1930 | known affected: 73 recommended: 181 | 2026-10-16T01:11:16+00:00 | Vulnerability · Source |
| CVE-2025-1931 | suse_vex | SUSE CVE CVE-2025-1931 | known affected: 73 recommended: 184 | 2026-10-16T01:11:14+00:00 | Vulnerability · Source |
| CVE-2025-1933 | suse_vex | SUSE CVE CVE-2025-1933 | known affected: 73 recommended: 181 | 2026-10-16T01:11:13+00:00 | Vulnerability · Source |
| CVE-2025-1936 | suse_vex | SUSE CVE CVE-2025-1936 | known affected: 73 recommended: 181 | 2026-10-16T01:11:11+00:00 | Vulnerability · Source |
| CVE-2025-1937 | suse_vex | SUSE CVE CVE-2025-1937 | known affected: 73 recommended: 174 | 2026-10-16T01:11:09+00:00 | Vulnerability · Source |
| CVE-2025-1974 | suse_vex | SUSE CVE CVE-2025-1974 | recommended: 14 | 2026-10-16T01:11:07+00:00 | Vulnerability · Source |
| CVE-2025-2151 | suse_vex | SUSE CVE CVE-2025-2151 | recommended: 12 | 2026-10-16T01:11:05+00:00 | Vulnerability · Source |
| CVE-2025-2173 | suse_vex | SUSE CVE CVE-2025-2173 | known affected: 16 recommended: 68 | 2026-10-16T01:11:03+00:00 | Vulnerability · Source |
| CVE-2025-2174 | suse_vex | SUSE CVE CVE-2025-2174 | known affected: 16 recommended: 68 | 2026-10-16T01:11:02+00:00 | Vulnerability · Source |
| CVE-2025-2241 | suse_vex | SUSE CVE CVE-2025-2241 | recommended: 5 | 2026-10-16T01:11:00+00:00 | Vulnerability · Source |
| CVE-2025-2296 | suse_vex | SUSE CVE CVE-2025-2296 | known affected: 137 known not affected: 97 recommended: 16 | 2026-10-16T01:10:59+00:00 | Vulnerability · Source |
| CVE-2025-2312 | suse_vex | SUSE CVE CVE-2025-2312 | known affected: 342 known not affected: 499 recommended: 460 | 2026-10-16T01:10:56+00:00 | Vulnerability · Source |
| CVE-2025-2361 | suse_vex | SUSE CVE CVE-2025-2361 | known affected: 12 recommended: 37 | 2026-10-16T01:10:55+00:00 | Vulnerability · Source |
| CVE-2025-2475 | suse_vex | SUSE CVE CVE-2025-2475 | recommended: 5 | 2026-10-16T01:10:53+00:00 | Vulnerability · Source |
| CVE-2025-2487 | suse_vex | SUSE CVE CVE-2025-2487 | known affected: 0 known not affected: 161 recommended: 47 | 2026-10-16T01:10:51+00:00 | Vulnerability · Source |
| CVE-2025-2527 | suse_vex | SUSE CVE CVE-2025-2527 | recommended: 5 | 2026-10-16T01:10:49+00:00 | Vulnerability · Source |
| CVE-2025-2571 | suse_vex | SUSE CVE CVE-2025-2571 | recommended: 5 | 2026-10-16T01:10:47+00:00 | Vulnerability · Source |
| CVE-2025-2574 | suse_vex | SUSE CVE CVE-2025-2574 | known affected: 0 known not affected: 476 | 2026-10-16T01:10:46+00:00 | Vulnerability · Source |
| CVE-2025-2588 | suse_vex | SUSE CVE CVE-2025-2588 | known affected: 500 recommended: 181 | 2026-10-16T01:10:44+00:00 | Vulnerability · Source |
| CVE-2025-2842 | suse_vex | SUSE CVE CVE-2025-2842 | recommended: 2 | 2026-10-16T01:10:42+00:00 | Vulnerability · Source |
| CVE-2025-2843 | suse_vex | SUSE CVE CVE-2025-2843 | recommended: 2 | 2026-10-16T01:10:40+00:00 | Vulnerability · Source |
| CVE-2025-3015 | suse_vex | SUSE CVE CVE-2025-3015 | known affected: 1283 known not affected: 174 recommended: 12 | 2026-10-16T01:10:38+00:00 | Vulnerability · Source |
| CVE-2025-3029 | suse_vex | SUSE CVE CVE-2025-3029 | known affected: 73 recommended: 154 | 2026-10-16T01:10:36+00:00 | Vulnerability · Source |
| CVE-2025-3030 | suse_vex | SUSE CVE CVE-2025-3030 | known affected: 73 recommended: 154 | 2026-10-16T01:10:34+00:00 | Vulnerability · Source |
| CVE-2025-3155 | suse_vex | SUSE CVE CVE-2025-3155 | known affected: 138 recommended: 98 | 2026-10-16T01:10:31+00:00 | Vulnerability · Source |
| CVE-2025-3198 | suse_vex | SUSE CVE CVE-2025-3198 | known affected: 519 known not affected: 1 recommended: 495 | 2026-10-16T01:10:29+00:00 | Vulnerability · Source |
| CVE-2025-3227 | suse_vex | SUSE CVE CVE-2025-3227 | recommended: 5 | 2026-10-16T01:10:27+00:00 | Vulnerability · Source |
| CVE-2025-3260 | suse_vex | SUSE CVE CVE-2025-3260 | known affected: 0 known not affected: 2 recommended: 5 | 2026-10-16T01:10:24+00:00 | Vulnerability · Source |
| CVE-2025-3277 | suse_vex | SUSE CVE CVE-2025-3277 | known affected: 208 known not affected: 16 recommended: 213 | 2026-10-16T01:10:22+00:00 | Vulnerability · Source |
| CVE-2025-3360 | suse_vex | SUSE CVE CVE-2025-3360 | known affected: 639 known not affected: 285 recommended: 310 | 2026-10-16T01:10:19+00:00 | Vulnerability · Source |
| CVE-2025-3415 | suse_vex | SUSE CVE CVE-2025-3415 | recommended: 132 | 2026-10-16T01:10:17+00:00 | Vulnerability · Source |
| CVE-2025-3445 | suse_vex | SUSE CVE CVE-2025-3445 | recommended: 10 | 2026-10-16T01:10:15+00:00 | Vulnerability · Source |
| CVE-2025-3446 | suse_vex | SUSE CVE CVE-2025-3446 | recommended: 5 | 2026-10-16T01:10:13+00:00 | Vulnerability · Source |
| CVE-2025-3611 | suse_vex | SUSE CVE CVE-2025-3611 | recommended: 5 | 2026-10-16T01:10:10+00:00 | Vulnerability · Source |
| CVE-2025-3757 | suse_vex | SUSE CVE CVE-2025-3757 | recommended: 5 | 2026-10-16T01:10:07+00:00 | Vulnerability · Source |
| CVE-2025-3770 | suse_vex | SUSE CVE CVE-2025-3770 | known affected: 1809 known not affected: 402 | 2026-10-16T01:10:05+00:00 | Vulnerability · Source |
| CVE-2025-3801 | suse_vex | SUSE CVE CVE-2025-3801 | recommended: 5 | 2026-10-16T01:10:03+00:00 | Vulnerability · Source |
| CVE-2025-3879 | suse_vex | SUSE CVE CVE-2025-3879 | known affected: 0 known not affected: 94 recommended: 5 | 2026-10-16T01:10:01+00:00 | Vulnerability · Source |
| CVE-2025-3913 | suse_vex | SUSE CVE CVE-2025-3913 | recommended: 5 | 2026-10-16T01:09:58+00:00 | Vulnerability · Source |
| CVE-2025-3931 | suse_vex | SUSE CVE CVE-2025-3931 | recommended: 5 | 2026-10-16T01:09:56+00:00 | Vulnerability · Source |
| CVE-2025-4035 | suse_vex | SUSE CVE CVE-2025-4035 | known affected: 452 recommended: 3 | 2026-10-16T01:09:54+00:00 | Vulnerability · Source |
| CVE-2025-4057 | suse_vex | SUSE CVE CVE-2025-4057 | recommended: 5 | 2026-10-16T01:09:53+00:00 | Vulnerability · Source |
| CVE-2025-4166 | suse_vex | SUSE CVE CVE-2025-4166 | recommended: 13 | 2026-10-16T01:09:50+00:00 | Vulnerability · Source |
| CVE-2025-4207 | suse_vex | SUSE CVE CVE-2025-4207 | known affected: 692 known not affected: 542 recommended: 1334 | 2026-10-16T01:09:48+00:00 | Vulnerability · Source |
| CVE-2025-4210 | suse_vex | SUSE CVE CVE-2025-4210 | recommended: 5 | 2026-10-16T01:09:47+00:00 | Vulnerability · Source |
| CVE-2025-4330 | suse_vex | SUSE CVE CVE-2025-4330 | known affected: 394 known not affected: 256 recommended: 944 | 2026-10-16T01:09:45+00:00 | Vulnerability · Source |
| CVE-2025-4373 | suse_vex | SUSE CVE CVE-2025-4373 | known affected: 994 recommended: 271 | 2026-10-16T01:09:43+00:00 | Vulnerability · Source |
| CVE-2025-4382 | suse_vex | SUSE CVE CVE-2025-4382 | known affected: 499 recommended: 160 | 2026-10-16T01:09:41+00:00 | Vulnerability · Source |