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-37821 | suse_vex | SUSE CVE CVE-2025-37821 | known affected: 74 known not affected: 481 recommended: 227 | 2026-10-15T16:50:14+00:00 | Vulnerability · Source |
| CVE-2025-37823 | suse_vex | SUSE CVE CVE-2025-37823 | known affected: 498 known not affected: 94 recommended: 872 | 2026-10-15T16:50:12+00:00 | Vulnerability · Source |
| CVE-2025-37825 | suse_vex | SUSE CVE CVE-2025-37825 | known affected: 0 known not affected: 502 recommended: 150 | 2026-10-15T16:50:10+00:00 | Vulnerability · Source |
| CVE-2025-37829 | suse_vex | SUSE CVE CVE-2025-37829 | known affected: 649 known not affected: 187 recommended: 431 | 2026-10-15T16:50:08+00:00 | Vulnerability · Source |
| CVE-2025-37830 | suse_vex | SUSE CVE CVE-2025-37830 | known affected: 649 known not affected: 187 recommended: 431 | 2026-10-15T16:50:06+00:00 | Vulnerability · Source |
| CVE-2025-37832 | suse_vex | SUSE CVE CVE-2025-37832 | known affected: 2 known not affected: 435 | 2026-10-15T16:50:04+00:00 | Vulnerability · Source |
| CVE-2025-37833 | suse_vex | SUSE CVE CVE-2025-37833 | known affected: 653 known not affected: 129 recommended: 454 | 2026-10-15T16:50:03+00:00 | Vulnerability · Source |
| CVE-2025-37835 | suse_vex | SUSE CVE CVE-2025-37835 | known affected: 143 known not affected: 368 | 2026-10-15T16:50:01+00:00 | Vulnerability · Source |
| CVE-2025-37836 | suse_vex | SUSE CVE CVE-2025-37836 | known affected: 699 known not affected: 125 recommended: 464 | 2026-10-15T16:49:58+00:00 | Vulnerability · Source |
| CVE-2025-37841 | suse_vex | SUSE CVE CVE-2025-37841 | known affected: 714 known not affected: 49 recommended: 521 | 2026-10-15T16:49:57+00:00 | Vulnerability · Source |
| CVE-2025-37845 | suse_vex | SUSE CVE CVE-2025-37845 | known affected: 2 known not affected: 502 recommended: 203 | 2026-10-15T16:49:55+00:00 | Vulnerability · Source |
| CVE-2025-37847 | suse_vex | SUSE CVE CVE-2025-37847 | known affected: 461 known not affected: 396 recommended: 202 | 2026-10-15T16:49:53+00:00 | Vulnerability · Source |
| CVE-2025-37851 | suse_vex | SUSE CVE CVE-2025-37851 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-15T16:49:51+00:00 | Vulnerability · Source |
| CVE-2025-37859 | suse_vex | SUSE CVE CVE-2025-37859 | known affected: 649 known not affected: 187 recommended: 427 | 2026-10-15T16:49:49+00:00 | Vulnerability · Source |
| CVE-2025-37864 | suse_vex | SUSE CVE CVE-2025-37864 | known affected: 511 known not affected: 338 recommended: 503 | 2026-10-15T16:49:47+00:00 | Vulnerability · Source |
| CVE-2025-37865 | suse_vex | SUSE CVE CVE-2025-37865 | known affected: 504 known not affected: 332 recommended: 412 | 2026-10-15T16:49:45+00:00 | Vulnerability · Source |
| CVE-2025-37866 | suse_vex | SUSE CVE CVE-2025-37866 | known affected: 0 known not affected: 502 | 2026-10-15T16:49:43+00:00 | Vulnerability · Source |
| CVE-2025-37868 | suse_vex | SUSE CVE CVE-2025-37868 | known affected: 394 known not affected: 463 recommended: 202 | 2026-10-15T16:49:40+00:00 | Vulnerability · Source |
| CVE-2025-37871 | suse_vex | SUSE CVE CVE-2025-37871 | known affected: 394 known not affected: 371 recommended: 464 | 2026-10-15T16:49:38+00:00 | Vulnerability · Source |
| CVE-2025-37873 | suse_vex | SUSE CVE CVE-2025-37873 | known affected: 461 known not affected: 360 recommended: 427 | 2026-10-15T16:49:36+00:00 | Vulnerability · Source |
| CVE-2025-37875 | suse_vex | SUSE CVE CVE-2025-37875 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:49:34+00:00 | Vulnerability · Source |
| CVE-2025-37877 | suse_vex | SUSE CVE CVE-2025-37877 | known affected: 0 known not affected: 542 recommended: 109 | 2026-10-15T16:49:32+00:00 | Vulnerability · Source |
| CVE-2025-37879 | suse_vex | SUSE CVE CVE-2025-37879 | known affected: 778 known not affected: 6 recommended: 468 | 2026-10-15T16:49:29+00:00 | Vulnerability · Source |
| CVE-2025-37880 | suse_vex | SUSE CVE CVE-2025-37880 | known affected: 0 known not affected: 554 | 2026-10-15T16:49:27+00:00 | Vulnerability · Source |
| CVE-2025-37881 | suse_vex | SUSE CVE CVE-2025-37881 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:49:25+00:00 | Vulnerability · Source |
| CVE-2025-37886 | suse_vex | SUSE CVE CVE-2025-37886 | known affected: 504 known not affected: 332 recommended: 431 | 2026-10-15T16:49:23+00:00 | Vulnerability · Source |
| CVE-2025-37887 | suse_vex | SUSE CVE CVE-2025-37887 | known affected: 504 known not affected: 332 recommended: 431 | 2026-10-15T16:49:21+00:00 | Vulnerability · Source |
| CVE-2025-37891 | suse_vex | SUSE CVE CVE-2025-37891 | known affected: 410 known not affected: 426 recommended: 427 | 2026-10-15T16:49:19+00:00 | Vulnerability · Source |
| CVE-2025-37893 | suse_vex | SUSE CVE CVE-2025-37893 | known affected: 0 known not affected: 549 recommended: 58 | 2026-10-15T16:49:17+00:00 | Vulnerability · Source |
| CVE-2025-37894 | suse_vex | SUSE CVE CVE-2025-37894 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-15T16:49:15+00:00 | Vulnerability · Source |
| CVE-2025-37895 | suse_vex | SUSE CVE CVE-2025-37895 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-15T16:49:13+00:00 | Vulnerability · Source |
| CVE-2025-37899 | suse_vex | SUSE CVE CVE-2025-37899 | known affected: 0 known not affected: 562 | 2026-10-15T16:49:11+00:00 | Vulnerability · Source |
| CVE-2025-37901 | suse_vex | SUSE CVE CVE-2025-37901 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-15T16:49:09+00:00 | Vulnerability · Source |
| CVE-2025-37909 | suse_vex | SUSE CVE CVE-2025-37909 | known affected: 649 known not affected: 187 recommended: 427 | 2026-10-15T16:49:06+00:00 | Vulnerability · Source |
| CVE-2025-37912 | suse_vex | SUSE CVE CVE-2025-37912 | known affected: 488 known not affected: 348 recommended: 427 | 2026-10-15T16:49:04+00:00 | Vulnerability · Source |
| CVE-2025-37915 | suse_vex | SUSE CVE CVE-2025-37915 | known affected: 591 known not affected: 230 recommended: 427 | 2026-10-15T16:49:02+00:00 | Vulnerability · Source |
| CVE-2025-37916 | suse_vex | SUSE CVE CVE-2025-37916 | known affected: 396 known not affected: 405 recommended: 495 | 2026-10-15T16:49:00+00:00 | Vulnerability · Source |
| CVE-2025-37917 | suse_vex | SUSE CVE CVE-2025-37917 | known affected: 437 known not affected: 399 recommended: 412 | 2026-10-15T16:48:58+00:00 | Vulnerability · Source |
| CVE-2025-37918 | suse_vex | SUSE CVE CVE-2025-37918 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-15T16:48:56+00:00 | Vulnerability · Source |
| CVE-2025-37919 | suse_vex | SUSE CVE CVE-2025-37919 | known affected: 0 known not affected: 502 recommended: 109 | 2026-10-15T16:48:54+00:00 | Vulnerability · Source |
| CVE-2025-37920 | suse_vex | SUSE CVE CVE-2025-37920 | known affected: 686 known not affected: 96 recommended: 450 | 2026-10-15T16:48:52+00:00 | Vulnerability · Source |
| CVE-2025-37925 | suse_vex | SUSE CVE CVE-2025-37925 | known affected: 586 known not affected: 315 recommended: 318 | 2026-10-15T16:48:50+00:00 | Vulnerability · Source |
| CVE-2025-37929 | suse_vex | SUSE CVE CVE-2025-37929 | known affected: 394 known not affected: 427 recommended: 427 | 2026-10-15T16:48:48+00:00 | Vulnerability · Source |
| CVE-2025-37930 | suse_vex | SUSE CVE CVE-2025-37930 | known affected: 565 known not affected: 256 recommended: 427 | 2026-10-15T16:48:46+00:00 | Vulnerability · Source |
| CVE-2025-37931 | suse_vex | SUSE CVE CVE-2025-37931 | known affected: 522 known not affected: 299 recommended: 427 | 2026-10-15T16:48:44+00:00 | Vulnerability · Source |
| CVE-2025-37932 | suse_vex | SUSE CVE CVE-2025-37932 | known affected: 199 known not affected: 47 recommended: 699 | 2026-10-15T16:48:42+00:00 | Vulnerability · Source |
| CVE-2025-37933 | suse_vex | SUSE CVE CVE-2025-37933 | known affected: 437 known not affected: 399 recommended: 412 | 2026-10-15T16:48:40+00:00 | Vulnerability · Source |
| CVE-2025-37934 | suse_vex | SUSE CVE CVE-2025-37934 | known affected: 461 known not affected: 409 recommended: 202 | 2026-10-15T16:48:38+00:00 | Vulnerability · Source |
| CVE-2025-37939 | suse_vex | SUSE CVE CVE-2025-37939 | known affected: 67 known not affected: 435 recommended: 58 | 2026-10-15T16:48:37+00:00 | Vulnerability · Source |
| CVE-2025-37940 | suse_vex | SUSE CVE CVE-2025-37940 | known affected: 305 known not affected: 36 | 2026-10-15T16:48:36+00:00 | Vulnerability · Source |