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-39925 | suse_vex | SUSE CVE CVE-2025-39925 | known affected: 524 known not affected: 259 recommended: 578 | 2026-10-15T16:31:20+00:00 | Vulnerability · Source |
| CVE-2025-39926 | suse_vex | SUSE CVE CVE-2025-39926 | known affected: 7 known not affected: 539 recommended: 185 | 2026-10-15T16:31:18+00:00 | Vulnerability · Source |
| CVE-2025-39927 | suse_vex | SUSE CVE CVE-2025-39927 | known affected: 298 known not affected: 187 recommended: 203 | 2026-10-15T16:31:16+00:00 | Vulnerability · Source |
| CVE-2025-39929 | suse_vex | SUSE CVE CVE-2025-39929 | known affected: 394 known not affected: 462 recommended: 23 | 2026-10-15T16:31:15+00:00 | Vulnerability · Source |
| CVE-2025-39931 | suse_vex | SUSE CVE CVE-2025-39931 | known affected: 731 recommended: 532 | 2026-10-15T16:31:13+00:00 | Vulnerability · Source |
| CVE-2025-39933 | suse_vex | SUSE CVE CVE-2025-39933 | known affected: 0 known not affected: 520 recommended: 132 | 2026-10-15T16:31:11+00:00 | Vulnerability · Source |
| CVE-2025-39934 | suse_vex | SUSE CVE CVE-2025-39934 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:31:09+00:00 | Vulnerability · Source |
| CVE-2025-39935 | suse_vex | SUSE CVE CVE-2025-39935 | known affected: 67 known not affected: 453 recommended: 58 | 2026-10-15T16:31:08+00:00 | Vulnerability · Source |
| CVE-2025-39937 | suse_vex | SUSE CVE CVE-2025-39937 | known affected: 755 known not affected: 36 recommended: 495 | 2026-10-15T16:31:06+00:00 | Vulnerability · Source |
| CVE-2025-39938 | suse_vex | SUSE CVE CVE-2025-39938 | known affected: 461 known not affected: 322 recommended: 495 | 2026-10-15T16:31:04+00:00 | Vulnerability · Source |
| CVE-2025-39940 | suse_vex | SUSE CVE CVE-2025-39940 | known affected: 318 known not affected: 6 | 2026-10-15T16:31:03+00:00 | Vulnerability · Source |
| CVE-2025-39944 | suse_vex | SUSE CVE CVE-2025-39944 | known affected: 529 known not affected: 262 recommended: 495 | 2026-10-15T16:31:01+00:00 | Vulnerability · Source |
| CVE-2025-39947 | suse_vex | SUSE CVE CVE-2025-39947 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:30:59+00:00 | Vulnerability · Source |
| CVE-2025-39949 | suse_vex | SUSE CVE CVE-2025-39949 | known affected: 660 known not affected: 68 recommended: 518 | 2026-10-15T16:30:57+00:00 | Vulnerability · Source |
| CVE-2025-39950 | suse_vex | SUSE CVE CVE-2025-39950 | known affected: 396 known not affected: 539 recommended: 185 | 2026-10-15T16:30:55+00:00 | Vulnerability · Source |
| CVE-2025-39952 | suse_vex | SUSE CVE CVE-2025-39952 | known affected: 593 known not affected: 208 recommended: 495 | 2026-10-15T16:30:52+00:00 | Vulnerability · Source |
| CVE-2025-39953 | suse_vex | SUSE CVE CVE-2025-39953 | known affected: 296 known not affected: 36 | 2026-10-15T16:30:51+00:00 | Vulnerability · Source |
| CVE-2025-39955 | suse_vex | SUSE CVE CVE-2025-39955 | known affected: 725 known not affected: 6 recommended: 606 | 2026-10-15T16:30:49+00:00 | Vulnerability · Source |
| CVE-2025-39956 | suse_vex | SUSE CVE CVE-2025-39956 | known affected: 396 known not affected: 542 recommended: 185 | 2026-10-15T16:30:47+00:00 | Vulnerability · Source |
| CVE-2025-39957 | suse_vex | SUSE CVE CVE-2025-39957 | known affected: 714 known not affected: 87 recommended: 495 | 2026-10-15T16:30:45+00:00 | Vulnerability · Source |
| CVE-2025-39965 | suse_vex | SUSE CVE CVE-2025-39965 | known affected: 2 known not affected: 277 recommended: 651 | 2026-10-15T16:30:42+00:00 | Vulnerability · Source |
| CVE-2025-39967 | suse_vex | SUSE CVE CVE-2025-39967 | known affected: 431 known not affected: 132 recommended: 714 | 2026-10-15T16:30:39+00:00 | Vulnerability · Source |
| CVE-2025-39968 | suse_vex | SUSE CVE CVE-2025-39968 | known affected: 356 known not affected: 159 recommended: 789 | 2026-10-15T16:30:38+00:00 | Vulnerability · Source |
| CVE-2025-39970 | suse_vex | SUSE CVE CVE-2025-39970 | known affected: 637 known not affected: 96 recommended: 518 | 2026-10-15T16:30:36+00:00 | Vulnerability · Source |
| CVE-2025-39971 | suse_vex | SUSE CVE CVE-2025-39971 | known affected: 637 known not affected: 96 recommended: 663 | 2026-10-15T16:30:34+00:00 | Vulnerability · Source |
| CVE-2025-39972 | suse_vex | SUSE CVE CVE-2025-39972 | known affected: 396 known not affected: 329 recommended: 518 | 2026-10-15T16:30:32+00:00 | Vulnerability · Source |
| CVE-2025-39977 | suse_vex | SUSE CVE CVE-2025-39977 | known affected: 398 known not affected: 262 recommended: 708 | 2026-10-15T16:30:30+00:00 | Vulnerability · Source |
| CVE-2025-39978 | suse_vex | SUSE CVE CVE-2025-39978 | known affected: 356 known not affected: 262 recommended: 691 | 2026-10-15T16:30:28+00:00 | Vulnerability · Source |
| CVE-2025-39980 | suse_vex | SUSE CVE CVE-2025-39980 | known affected: 573 known not affected: 213 recommended: 495 | 2026-10-15T16:30:26+00:00 | Vulnerability · Source |
| CVE-2025-39981 | suse_vex | SUSE CVE CVE-2025-39981 | known affected: 376 known not affected: 323 recommended: 685 | 2026-10-15T16:30:24+00:00 | Vulnerability · Source |
| CVE-2025-39982 | suse_vex | SUSE CVE CVE-2025-39982 | known affected: 396 known not affected: 387 recommended: 618 | 2026-10-15T16:30:22+00:00 | Vulnerability · Source |
| CVE-2025-39983 | suse_vex | SUSE CVE CVE-2025-39983 | known affected: 0 known not affected: 520 recommended: 141 | 2026-10-15T16:30:20+00:00 | Vulnerability · Source |
| CVE-2025-39985 | suse_vex | SUSE CVE CVE-2025-39985 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:30:17+00:00 | Vulnerability · Source |
| CVE-2025-39987 | suse_vex | SUSE CVE CVE-2025-39987 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:30:15+00:00 | Vulnerability · Source |
| CVE-2025-39988 | suse_vex | SUSE CVE CVE-2025-39988 | known affected: 396 known not affected: 387 recommended: 495 | 2026-10-15T16:30:13+00:00 | Vulnerability · Source |
| CVE-2025-39989 | suse_vex | SUSE CVE CVE-2025-39989 | known affected: 143 known not affected: 256 recommended: 109 | 2026-10-15T16:30:11+00:00 | Vulnerability · Source |
| CVE-2025-39990 | suse_vex | SUSE CVE CVE-2025-39990 | known affected: 343 known not affected: 6 recommended: 185 | 2026-10-15T16:30:10+00:00 | Vulnerability · Source |
| CVE-2025-39991 | suse_vex | SUSE CVE CVE-2025-39991 | known affected: 396 known not affected: 387 recommended: 501 | 2026-10-15T16:30:08+00:00 | Vulnerability · Source |
| CVE-2025-39993 | suse_vex | SUSE CVE CVE-2025-39993 | known affected: 396 known not affected: 387 recommended: 534 | 2026-10-15T16:30:06+00:00 | Vulnerability · Source |
| CVE-2025-39995 | suse_vex | SUSE CVE CVE-2025-39995 | known affected: 396 known not affected: 387 recommended: 501 | 2026-10-15T16:30:04+00:00 | Vulnerability · Source |
| CVE-2025-39996 | suse_vex | SUSE CVE CVE-2025-39996 | known affected: 396 known not affected: 387 recommended: 501 | 2026-10-15T16:30:02+00:00 | Vulnerability · Source |
| CVE-2025-39997 | suse_vex | SUSE CVE CVE-2025-39997 | known affected: 401 known not affected: 330 recommended: 538 | 2026-10-15T16:30:00+00:00 | Vulnerability · Source |
| CVE-2025-39998 | suse_vex | SUSE CVE CVE-2025-39998 | known affected: 778 recommended: 385 | 2026-10-15T16:29:59+00:00 | Vulnerability · Source |
| CVE-2025-39999 | suse_vex | SUSE CVE CVE-2025-39999 | known affected: 0 known not affected: 520 recommended: 64 | 2026-10-15T16:29:57+00:00 | Vulnerability · Source |
| CVE-2025-40002 | suse_vex | SUSE CVE CVE-2025-40002 | known affected: 0 known not affected: 520 recommended: 64 | 2026-10-15T16:29:55+00:00 | Vulnerability · Source |
| CVE-2025-40005 | suse_vex | SUSE CVE CVE-2025-40005 | known affected: 697 known not affected: 94 recommended: 495 | 2026-10-15T16:29:53+00:00 | Vulnerability · Source |
| CVE-2025-40006 | suse_vex | SUSE CVE CVE-2025-40006 | known affected: 741 known not affected: 36 recommended: 420 | 2026-10-15T16:29:51+00:00 | Vulnerability · Source |
| CVE-2025-40007 | suse_vex | SUSE CVE CVE-2025-40007 | known affected: 0 known not affected: 520 | 2026-10-15T16:29:49+00:00 | Vulnerability · Source |
| CVE-2025-40009 | suse_vex | SUSE CVE CVE-2025-40009 | known affected: 399 known not affected: 511 recommended: 185 | 2026-10-15T16:29:47+00:00 | Vulnerability · Source |
| CVE-2025-40011 | suse_vex | SUSE CVE CVE-2025-40011 | known affected: 645 known not affected: 135 recommended: 495 | 2026-10-15T16:29:45+00:00 | Vulnerability · Source |