VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287382 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-37776 | suse_vex | SUSE CVE CVE-2025-37776 | known not affected: 456 | 2026-07-31T01:16:08+00:00 | Vulnerability · Source |
| CVE-2025-37777 | suse_vex | SUSE CVE CVE-2025-37777 | known not affected: 456 | 2026-07-31T01:16:06+00:00 | Vulnerability · Source |
| CVE-2025-37791 | suse_vex | SUSE CVE CVE-2025-37791 | known affected: 424 known not affected: 359 recommended: 164 | 2026-07-31T01:16:02+00:00 | Vulnerability · Source |
| CVE-2025-37802 | suse_vex | SUSE CVE CVE-2025-37802 | known not affected: 456 | 2026-07-31T01:15:57+00:00 | Vulnerability · Source |
| CVE-2025-37806 | suse_vex | SUSE CVE CVE-2025-37806 | known not affected: 449 | 2026-07-31T01:15:54+00:00 | Vulnerability · Source |
| CVE-2025-37814 | suse_vex | SUSE CVE CVE-2025-37814 | known affected: 394 known not affected: 374 recommended: 164 | 2026-07-31T01:15:48+00:00 | Vulnerability · Source |
| CVE-2025-37817 | suse_vex | SUSE CVE CVE-2025-37817 | known affected: 224 known not affected: 225 | 2026-07-31T01:15:46+00:00 | Vulnerability · Source |
| CVE-2025-37818 | suse_vex | SUSE CVE CVE-2025-37818 | known not affected: 449 | 2026-07-31T01:15:44+00:00 | Vulnerability · Source |
| CVE-2025-37822 | suse_vex | SUSE CVE CVE-2025-37822 | known not affected: 468 | 2026-07-31T01:15:41+00:00 | Vulnerability · Source |
| CVE-2025-37834 | suse_vex | SUSE CVE CVE-2025-37834 | known not affected: 456 | 2026-07-31T01:15:38+00:00 | Vulnerability · Source |
| CVE-2025-37838 | suse_vex | SUSE CVE CVE-2025-37838 | known not affected: 348 recommended: 53 | 2026-07-31T01:15:36+00:00 | Vulnerability · Source |
| CVE-2025-37845 | suse_vex | SUSE CVE CVE-2025-37845 | first fixed: 2 known not affected: 397 recommended: 172 | 2026-07-31T01:15:33+00:00 | Vulnerability · Source |
| CVE-2025-37849 | suse_vex | SUSE CVE CVE-2025-37849 | first fixed: 2 known affected: 506 known not affected: 196 recommended: 591 | 2026-07-31T01:15:30+00:00 | Vulnerability · Source |
| CVE-2025-37857 | suse_vex | SUSE CVE CVE-2025-37857 | known affected: 275 known not affected: 68 | 2026-07-31T01:15:26+00:00 | Vulnerability · Source |
| CVE-2025-37858 | suse_vex | SUSE CVE CVE-2025-37858 | known affected: 394 known not affected: 208 recommended: 354 | 2026-07-31T01:15:23+00:00 | Vulnerability · Source |
| CVE-2025-37869 | suse_vex | SUSE CVE CVE-2025-37869 | known affected: 451 known not affected: 317 recommended: 164 | 2026-07-31T01:15:20+00:00 | Vulnerability · Source |
| CVE-2025-37876 | suse_vex | SUSE CVE CVE-2025-37876 | known not affected: 455 | 2026-07-31T01:15:16+00:00 | Vulnerability · Source |
| CVE-2025-37880 | suse_vex | SUSE CVE CVE-2025-37880 | known not affected: 449 | 2026-07-31T01:15:12+00:00 | Vulnerability · Source |
| CVE-2025-37883 | suse_vex | SUSE CVE CVE-2025-37883 | known affected: 180 known not affected: 120 | 2026-07-31T01:15:09+00:00 | Vulnerability · Source |
| CVE-2025-37894 | suse_vex | SUSE CVE CVE-2025-37894 | known not affected: 375 recommended: 53 | 2026-07-31T01:15:01+00:00 | Vulnerability · Source |
| CVE-2025-37906 | suse_vex | SUSE CVE CVE-2025-37906 | known not affected: 455 | 2026-07-31T01:14:56+00:00 | Vulnerability · Source |
| CVE-2025-37908 | suse_vex | SUSE CVE CVE-2025-37908 | known not affected: 375 recommended: 53 | 2026-07-31T01:14:54+00:00 | Vulnerability · Source |
| CVE-2025-37925 | suse_vex | SUSE CVE CVE-2025-37925 | known affected: 564 known not affected: 224 recommended: 354 | 2026-07-31T01:14:44+00:00 | Vulnerability · Source |
| CVE-2025-37926 | suse_vex | SUSE CVE CVE-2025-37926 | known not affected: 449 | 2026-07-31T01:14:42+00:00 | Vulnerability · Source |
| CVE-2025-37947 | suse_vex | SUSE CVE CVE-2025-37947 | known not affected: 451 | 2026-07-31T01:14:35+00:00 | Vulnerability · Source |
| CVE-2025-37952 | suse_vex | SUSE CVE CVE-2025-37952 | known not affected: 449 | 2026-07-31T01:14:32+00:00 | Vulnerability · Source |
| CVE-2025-37956 | suse_vex | SUSE CVE CVE-2025-37956 | known not affected: 449 | 2026-07-31T01:14:28+00:00 | Vulnerability · Source |
| CVE-2025-37964 | suse_vex | SUSE CVE CVE-2025-37964 | known not affected: 375 | 2026-07-31T01:14:25+00:00 | Vulnerability · Source |
| CVE-2025-37975 | suse_vex | SUSE CVE CVE-2025-37975 | known affected: 57 known not affected: 398 | 2026-07-31T01:14:22+00:00 | Vulnerability · Source |
| CVE-2025-37988 | suse_vex | SUSE CVE CVE-2025-37988 | known affected: 57 known not affected: 340 recommended: 53 | 2026-07-31T01:14:17+00:00 | Vulnerability · Source |
| CVE-2025-37991 | suse_vex | SUSE CVE CVE-2025-37991 | known not affected: 449 | 2026-07-31T01:14:15+00:00 | Vulnerability · Source |
| CVE-2025-38012 | suse_vex | SUSE CVE CVE-2025-38012 | known not affected: 401 recommended: 42 | 2026-07-31T01:14:07+00:00 | Vulnerability · Source |
| CVE-2025-38016 | suse_vex | SUSE CVE CVE-2025-38016 | known not affected: 401 recommended: 53 | 2026-07-31T01:14:04+00:00 | Vulnerability · Source |
| CVE-2025-38022 | suse_vex | SUSE CVE CVE-2025-38022 | known affected: 543 known not affected: 159 recommended: 510 | 2026-07-31T01:14:01+00:00 | Vulnerability · Source |
| CVE-2025-38028 | suse_vex | SUSE CVE CVE-2025-38028 | known not affected: 401 | 2026-07-31T01:13:58+00:00 | Vulnerability · Source |
| CVE-2025-38029 | suse_vex | SUSE CVE CVE-2025-38029 | known affected: 6 known not affected: 449 | 2026-07-31T01:13:55+00:00 | Vulnerability · Source |
| CVE-2025-38033 | suse_vex | SUSE CVE CVE-2025-38033 | known not affected: 470 | 2026-07-31T01:13:52+00:00 | Vulnerability · Source |
| CVE-2025-38037 | suse_vex | SUSE CVE CVE-2025-38037 | known affected: 269 known not affected: 70 | 2026-07-31T01:13:49+00:00 | Vulnerability · Source |
| CVE-2025-38039 | suse_vex | SUSE CVE CVE-2025-38039 | known affected: 143 known not affected: 186 recommended: 27 | 2026-07-31T01:13:46+00:00 | Vulnerability · Source |
| CVE-2025-38041 | suse_vex | SUSE CVE CVE-2025-38041 | known not affected: 341 | 2026-07-31T01:13:44+00:00 | Vulnerability · Source |
| CVE-2025-38042 | suse_vex | SUSE CVE CVE-2025-38042 | known affected: 127 known not affected: 214 | 2026-07-31T01:13:41+00:00 | Vulnerability · Source |
| CVE-2025-38048 | suse_vex | SUSE CVE CVE-2025-38048 | known affected: 127 known not affected: 214 | 2026-07-31T01:13:39+00:00 | Vulnerability · Source |
| CVE-2025-38065 | suse_vex | SUSE CVE CVE-2025-38065 | known affected: 394 known not affected: 378 recommended: 354 | 2026-07-31T01:13:29+00:00 | Vulnerability · Source |
| CVE-2025-38071 | suse_vex | SUSE CVE CVE-2025-38071 | known not affected: 269 | 2026-07-31T01:13:26+00:00 | Vulnerability · Source |
| CVE-2025-38086 | suse_vex | SUSE CVE CVE-2025-38086 | known not affected: 470 recommended: 63 | 2026-07-31T01:13:18+00:00 | Vulnerability · Source |
| CVE-2025-38101 | suse_vex | SUSE CVE CVE-2025-38101 | first fixed: 2 known not affected: 448 recommended: 154 | 2026-07-31T01:13:12+00:00 | Vulnerability · Source |
| CVE-2025-38106 | suse_vex | SUSE CVE CVE-2025-38106 | first fixed: 2 known affected: 429 known not affected: 391 recommended: 348 | 2026-07-31T01:13:10+00:00 | Vulnerability · Source |
| CVE-2025-38116 | suse_vex | SUSE CVE CVE-2025-38116 | known not affected: 416 recommended: 83 | 2026-07-31T01:13:05+00:00 | Vulnerability · Source |
| CVE-2025-38133 | suse_vex | SUSE CVE CVE-2025-38133 | known not affected: 416 | 2026-07-31T01:12:58+00:00 | Vulnerability · Source |
| CVE-2025-38139 | suse_vex | SUSE CVE CVE-2025-38139 | known not affected: 416 recommended: 53 | 2026-07-31T01:12:55+00:00 | Vulnerability · Source |