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-39781 | suse_vex | SUSE CVE CVE-2025-39781 | known affected: 0 known not affected: 520 | 2026-10-16T12:54:46+00:00 | Vulnerability · Source |
| CVE-2025-39790 | suse_vex | SUSE CVE CVE-2025-39790 | known affected: 346 known not affected: 259 recommended: 701 | 2026-10-16T12:54:43+00:00 | Vulnerability · Source |
| CVE-2025-39792 | suse_vex | SUSE CVE CVE-2025-39792 | known affected: 7 known not affected: 539 recommended: 185 | 2026-10-16T12:54:41+00:00 | Vulnerability · Source |
| CVE-2025-39812 | suse_vex | SUSE CVE CVE-2025-39812 | known affected: 726 known not affected: 5 recommended: 532 | 2026-10-16T12:54:39+00:00 | Vulnerability · Source |
| CVE-2025-39824 | suse_vex | SUSE CVE CVE-2025-39824 | known affected: 519 known not affected: 36 recommended: 724 | 2026-10-16T12:54:36+00:00 | Vulnerability · Source |
| CVE-2025-39828 | suse_vex | SUSE CVE CVE-2025-39828 | known affected: 731 recommended: 495 | 2026-10-16T12:54:34+00:00 | Vulnerability · Source |
| CVE-2025-39835 | suse_vex | SUSE CVE CVE-2025-39835 | known affected: 529 known not affected: 262 recommended: 495 | 2026-10-16T12:54:32+00:00 | Vulnerability · Source |
| CVE-2025-39857 | suse_vex | SUSE CVE CVE-2025-39857 | known affected: 468 known not affected: 325 recommended: 495 | 2026-10-16T12:54:28+00:00 | Vulnerability · Source |
| CVE-2025-39869 | suse_vex | SUSE CVE CVE-2025-39869 | known affected: 547 known not affected: 6 recommended: 738 | 2026-10-16T12:54:25+00:00 | Vulnerability · Source |
| CVE-2025-39880 | suse_vex | SUSE CVE CVE-2025-39880 | known affected: 614 known not affected: 262 recommended: 320 | 2026-10-16T12:54:23+00:00 | Vulnerability · Source |
| CVE-2025-39889 | suse_vex | SUSE CVE CVE-2025-39889 | known affected: 780 known not affected: 40 recommended: 495 | 2026-10-16T12:54:21+00:00 | Vulnerability · Source |
| CVE-2025-39895 | suse_vex | SUSE CVE CVE-2025-39895 | known affected: 396 known not affected: 390 recommended: 495 | 2026-10-16T12:54:19+00:00 | Vulnerability · Source |
| CVE-2025-39897 | suse_vex | SUSE CVE CVE-2025-39897 | known affected: 2 known not affected: 539 recommended: 185 | 2026-10-16T12:54:18+00:00 | Vulnerability · Source |
| CVE-2025-39898 | suse_vex | SUSE CVE CVE-2025-39898 | known affected: 479 known not affected: 37 recommended: 453 | 2026-10-16T12:54:16+00:00 | Vulnerability · Source |
| CVE-2025-39899 | suse_vex | SUSE CVE CVE-2025-39899 | known affected: 2 known not affected: 520 recommended: 185 | 2026-10-16T12:54:14+00:00 | Vulnerability · Source |
| CVE-2025-39902 | suse_vex | SUSE CVE CVE-2025-39902 | known affected: 604 known not affected: 187 recommended: 514 | 2026-10-16T12:54:13+00:00 | Vulnerability · Source |
| CVE-2025-39911 | suse_vex | SUSE CVE CVE-2025-39911 | known affected: 731 recommended: 532 | 2026-10-16T12:54:11+00:00 | Vulnerability · Source |
| CVE-2025-39914 | suse_vex | SUSE CVE CVE-2025-39914 | known affected: 9 known not affected: 384 | 2026-10-16T12:54:10+00:00 | Vulnerability · Source |
| CVE-2025-39917 | suse_vex | SUSE CVE CVE-2025-39917 | known affected: 7 known not affected: 539 recommended: 185 | 2026-10-16T12:54:08+00:00 | Vulnerability · Source |
| CVE-2025-39918 | suse_vex | SUSE CVE CVE-2025-39918 | known affected: 2 known not affected: 514 recommended: 268 | 2026-10-16T12:54:07+00:00 | Vulnerability · Source |
| CVE-2025-39923 | suse_vex | SUSE CVE CVE-2025-39923 | known affected: 686 known not affected: 39 recommended: 518 | 2026-10-16T12:54:05+00:00 | Vulnerability · Source |
| CVE-2025-39924 | suse_vex | SUSE CVE CVE-2025-39924 | known affected: 0 known not affected: 520 | 2026-10-16T12:54:03+00:00 | Vulnerability · Source |
| CVE-2025-39932 | suse_vex | SUSE CVE CVE-2025-39932 | known affected: 0 known not affected: 520 | 2026-10-16T12:54:01+00:00 | Vulnerability · Source |
| CVE-2025-39939 | suse_vex | SUSE CVE CVE-2025-39939 | known affected: 394 known not affected: 500 recommended: 141 | 2026-10-16T12:53:59+00:00 | Vulnerability · Source |
| CVE-2025-39948 | suse_vex | SUSE CVE CVE-2025-39948 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-16T12:53:56+00:00 | Vulnerability · Source |
| CVE-2025-39961 | suse_vex | SUSE CVE CVE-2025-39961 | known affected: 315 known not affected: 36 recommended: 185 | 2026-10-16T12:53:52+00:00 | Vulnerability · Source |
| CVE-2025-39963 | suse_vex | SUSE CVE CVE-2025-39963 | known affected: 401 known not affected: 537 recommended: 193 | 2026-10-16T12:53:50+00:00 | Vulnerability · Source |
| CVE-2025-39969 | suse_vex | SUSE CVE CVE-2025-39969 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-16T12:53:47+00:00 | Vulnerability · Source |
| CVE-2025-39973 | suse_vex | SUSE CVE CVE-2025-39973 | known affected: 477 recommended: 1050 | 2026-10-16T12:53:43+00:00 | Vulnerability · Source |
| CVE-2025-39979 | suse_vex | SUSE CVE CVE-2025-39979 | known affected: 396 known not affected: 539 recommended: 268 | 2026-10-16T12:53:39+00:00 | Vulnerability · Source |
| CVE-2025-39994 | suse_vex | SUSE CVE CVE-2025-39994 | known affected: 396 known not affected: 327 recommended: 521 | 2026-10-16T12:53:35+00:00 | Vulnerability · Source |
| CVE-2025-40000 | suse_vex | SUSE CVE CVE-2025-40000 | known affected: 468 known not affected: 323 recommended: 501 | 2026-10-16T12:53:33+00:00 | Vulnerability · Source |
| CVE-2025-40001 | suse_vex | SUSE CVE CVE-2025-40001 | known affected: 731 recommended: 538 | 2026-10-16T12:53:31+00:00 | Vulnerability · Source |
| CVE-2025-40003 | suse_vex | SUSE CVE CVE-2025-40003 | known affected: 295 known not affected: 187 recommended: 191 | 2026-10-16T12:53:30+00:00 | Vulnerability · Source |
| CVE-2025-40029 | suse_vex | SUSE CVE CVE-2025-40029 | known affected: 557 known not affected: 235 recommended: 501 | 2026-10-16T12:53:26+00:00 | Vulnerability · Source |
| CVE-2025-40033 | suse_vex | SUSE CVE CVE-2025-40033 | known affected: 440 known not affected: 390 recommended: 403 | 2026-10-16T12:53:24+00:00 | Vulnerability · Source |
| CVE-2025-40037 | suse_vex | SUSE CVE CVE-2025-40037 | known affected: 396 known not affected: 461 recommended: 284 | 2026-10-16T12:53:21+00:00 | Vulnerability · Source |
| CVE-2025-40038 | suse_vex | SUSE CVE CVE-2025-40038 | known affected: 396 known not affected: 390 recommended: 501 | 2026-10-16T12:53:18+00:00 | Vulnerability · Source |
| CVE-2025-40040 | suse_vex | SUSE CVE CVE-2025-40040 | known affected: 509 recommended: 809 | 2026-10-16T12:53:16+00:00 | Vulnerability · Source |
| CVE-2025-40044 | suse_vex | SUSE CVE CVE-2025-40044 | known affected: 558 recommended: 734 | 2026-10-16T12:53:14+00:00 | Vulnerability · Source |
| CVE-2025-40047 | suse_vex | SUSE CVE CVE-2025-40047 | known affected: 396 known not affected: 487 recommended: 396 | 2026-10-16T12:53:12+00:00 | Vulnerability · Source |
| CVE-2025-40048 | suse_vex | SUSE CVE CVE-2025-40048 | known affected: 526 known not affected: 34 recommended: 720 | 2026-10-16T12:53:11+00:00 | Vulnerability · Source |
| CVE-2025-40050 | suse_vex | SUSE CVE CVE-2025-40050 | known affected: 0 known not affected: 511 recommended: 64 | 2026-10-16T12:53:08+00:00 | Vulnerability · Source |
| CVE-2025-40058 | suse_vex | SUSE CVE CVE-2025-40058 | known affected: 463 known not affected: 323 recommended: 584 | 2026-10-16T12:53:05+00:00 | Vulnerability · Source |
| CVE-2025-40059 | suse_vex | SUSE CVE CVE-2025-40059 | known affected: 396 known not affected: 390 recommended: 501 | 2026-10-16T12:53:03+00:00 | Vulnerability · Source |
| CVE-2025-40082 | suse_vex | SUSE CVE CVE-2025-40082 | known affected: 394 known not affected: 281 recommended: 428 | 2026-10-16T12:53:00+00:00 | Vulnerability · Source |
| CVE-2025-40088 | suse_vex | SUSE CVE CVE-2025-40088 | known affected: 637 known not affected: 6 recommended: 462 | 2026-10-16T12:52:58+00:00 | Vulnerability · Source |
| CVE-2025-40099 | suse_vex | SUSE CVE CVE-2025-40099 | known affected: 773 recommended: 449 | 2026-10-16T12:52:56+00:00 | Vulnerability · Source |
| CVE-2025-40104 | suse_vex | SUSE CVE CVE-2025-40104 | known affected: 766 known not affected: 96 recommended: 284 | 2026-10-16T12:52:54+00:00 | Vulnerability · Source |
| CVE-2025-40106 | suse_vex | SUSE CVE CVE-2025-40106 | known affected: 865 known not affected: 6 recommended: 326 | 2026-10-16T12:52:51+00:00 | Vulnerability · Source |