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-2024-40966 | suse_vex | SUSE CVE CVE-2024-40966 | known affected: 586 recommended: 735 | 2026-10-16T01:53:24+00:00 | Vulnerability · Source |
| CVE-2024-40970 | suse_vex | SUSE CVE CVE-2024-40970 | known affected: 397 known not affected: 225 recommended: 651 | 2026-10-16T01:53:22+00:00 | Vulnerability · Source |
| CVE-2024-40971 | suse_vex | SUSE CVE CVE-2024-40971 | known not affected: 373 | 2026-10-16T01:53:20+00:00 | Vulnerability · Source |
| CVE-2024-40975 | suse_vex | SUSE CVE CVE-2024-40975 | known affected: 394 known not affected: 361 recommended: 353 | 2026-10-16T01:53:18+00:00 | Vulnerability · Source |
| CVE-2024-40976 | suse_vex | SUSE CVE CVE-2024-40976 | known affected: 368 known not affected: 159 recommended: 653 | 2026-10-16T01:53:17+00:00 | Vulnerability · Source |
| CVE-2024-40977 | suse_vex | SUSE CVE CVE-2024-40977 | known affected: 330 known not affected: 287 recommended: 731 | 2026-10-16T01:53:15+00:00 | Vulnerability · Source |
| CVE-2024-40978 | suse_vex | SUSE CVE CVE-2024-40978 | known affected: 590 known not affected: 6 recommended: 805 | 2026-10-16T01:53:13+00:00 | Vulnerability · Source |
| CVE-2024-40979 | suse_vex | SUSE CVE CVE-2024-40979 | known affected: 394 known not affected: 356 recommended: 353 | 2026-10-16T01:53:11+00:00 | Vulnerability · Source |
| CVE-2024-40980 | suse_vex | SUSE CVE CVE-2024-40980 | known affected: 557 known not affected: 175 recommended: 514 | 2026-10-16T01:53:09+00:00 | Vulnerability · Source |
| CVE-2024-40982 | suse_vex | SUSE CVE CVE-2024-40982 | known affected: 586 known not affected: 12 recommended: 737 | 2026-10-16T01:53:07+00:00 | Vulnerability · Source |
| CVE-2024-40983 | suse_vex | SUSE CVE CVE-2024-40983 | known affected: 410 known not affected: 260 recommended: 718 | 2026-10-16T01:53:05+00:00 | Vulnerability · Source |
| CVE-2024-40984 | suse_vex | SUSE CVE CVE-2024-40984 | known affected: 586 known not affected: 12 recommended: 786 | 2026-10-16T01:53:03+00:00 | Vulnerability · Source |
| CVE-2024-40986 | suse_vex | SUSE CVE CVE-2024-40986 | known not affected: 373 | 2026-10-16T01:53:01+00:00 | Vulnerability · Source |
| CVE-2024-40988 | suse_vex | SUSE CVE CVE-2024-40988 | known affected: 608 known not affected: 6 recommended: 757 | 2026-10-16T01:52:59+00:00 | Vulnerability · Source |
| CVE-2024-40990 | suse_vex | SUSE CVE CVE-2024-40990 | known affected: 504 known not affected: 2 recommended: 737 | 2026-10-16T01:52:57+00:00 | Vulnerability · Source |
| CVE-2024-40991 | suse_vex | SUSE CVE CVE-2024-40991 | known not affected: 373 | 2026-10-16T01:52:55+00:00 | Vulnerability · Source |
| CVE-2024-40993 | suse_vex | SUSE CVE CVE-2024-40993 | known not affected: 373 | 2026-10-16T01:52:53+00:00 | Vulnerability · Source |
| CVE-2024-40995 | suse_vex | SUSE CVE CVE-2024-40995 | known affected: 576 known not affected: 74 recommended: 737 | 2026-10-16T01:52:51+00:00 | Vulnerability · Source |
| CVE-2024-40997 | suse_vex | SUSE CVE CVE-2024-40997 | known affected: 354 known not affected: 300 recommended: 644 | 2026-10-16T01:52:49+00:00 | Vulnerability · Source |
| CVE-2024-41000 | suse_vex | SUSE CVE CVE-2024-41000 | known affected: 340 known not affected: 293 recommended: 655 | 2026-10-16T01:52:47+00:00 | Vulnerability · Source |
| CVE-2024-41001 | suse_vex | SUSE CVE CVE-2024-41001 | known affected: 394 known not affected: 320 recommended: 355 | 2026-10-16T01:52:45+00:00 | Vulnerability · Source |
| CVE-2024-41002 | suse_vex | SUSE CVE CVE-2024-41002 | known affected: 421 known not affected: 159 recommended: 653 | 2026-10-16T01:52:43+00:00 | Vulnerability · Source |
| CVE-2024-41003 | suse_vex | SUSE CVE CVE-2024-41003 | known not affected: 373 | 2026-10-16T01:52:42+00:00 | Vulnerability · Source |
| CVE-2024-41004 | suse_vex | SUSE CVE CVE-2024-41004 | known affected: 330 known not affected: 201 recommended: 653 | 2026-10-16T01:52:40+00:00 | Vulnerability · Source |
| CVE-2024-41005 | suse_vex | SUSE CVE CVE-2024-41005 | known affected: 758 recommended: 424 | 2026-10-16T01:52:38+00:00 | Vulnerability · Source |
| CVE-2024-41006 | suse_vex | SUSE CVE CVE-2024-41006 | known affected: 397 known not affected: 225 recommended: 651 | 2026-10-16T01:52:36+00:00 | Vulnerability · Source |
| CVE-2024-41007 | suse_vex | SUSE CVE CVE-2024-41007 | known affected: 489 known not affected: 139 recommended: 700 | 2026-10-16T01:52:34+00:00 | Vulnerability · Source |
| CVE-2024-41009 | suse_vex | SUSE CVE CVE-2024-41009 | known affected: 330 known not affected: 176 recommended: 885 | 2026-10-16T01:52:32+00:00 | Vulnerability · Source |
| CVE-2024-41010 | suse_vex | SUSE CVE CVE-2024-41010 | known affected: 394 known not affected: 361 recommended: 441 | 2026-10-16T01:52:30+00:00 | Vulnerability · Source |
| CVE-2024-41011 | suse_vex | SUSE CVE CVE-2024-41011 | known affected: 292 known not affected: 130 recommended: 926 | 2026-10-16T01:52:28+00:00 | Vulnerability · Source |
| CVE-2024-41012 | suse_vex | SUSE CVE CVE-2024-41012 | known affected: 435 recommended: 885 | 2026-10-16T01:52:26+00:00 | Vulnerability · Source |
| CVE-2024-41015 | suse_vex | SUSE CVE CVE-2024-41015 | known affected: 586 recommended: 737 | 2026-10-16T01:52:23+00:00 | Vulnerability · Source |
| CVE-2024-41016 | suse_vex | SUSE CVE CVE-2024-41016 | known affected: 586 recommended: 788 | 2026-10-16T01:52:22+00:00 | Vulnerability · Source |
| CVE-2024-41021 | suse_vex | SUSE CVE CVE-2024-41021 | known not affected: 379 | 2026-10-16T01:52:20+00:00 | Vulnerability · Source |
| CVE-2025-1149 | microsoft_vex | GNU Binutils ld xmalloc.c xstrdup memory leak | known affected: 4 known not affected: 1 under investigation: 31 | 2026-10-16T01:52:19+00:00 | Vulnerability · Source |
| CVE-2024-41022 | suse_vex | SUSE CVE CVE-2024-41022 | known affected: 340 known not affected: 264 recommended: 643 | 2026-10-16T01:52:18+00:00 | Vulnerability · Source |
| CVE-2025-1152 | microsoft_vex | GNU Binutils ld xstrdup.c xstrdup memory leak | known affected: 35 known not affected: 1 | 2026-10-16T01:52:17+00:00 | Vulnerability · Source |
| CVE-2024-41026 | suse_vex | SUSE CVE CVE-2024-41026 | known not affected: 379 | 2026-10-16T01:52:16+00:00 | Vulnerability · Source |
| CVE-2025-1151 | microsoft_vex | GNU Binutils ld xmemdup.c xmemdup memory leak | known affected: 34 known not affected: 1 | 2026-10-16T01:52:15+00:00 | Vulnerability · Source |
| CVE-2024-41028 | suse_vex | SUSE CVE CVE-2024-41028 | known affected: 394 known not affected: 326 recommended: 355 | 2026-10-16T01:52:14+00:00 | Vulnerability · Source |
| CVE-2024-41029 | suse_vex | SUSE CVE CVE-2024-41029 | known not affected: 379 | 2026-10-16T01:52:12+00:00 | Vulnerability · Source |
| CVE-2024-41031 | suse_vex | SUSE CVE CVE-2024-41031 | known affected: 398 known not affected: 414 recommended: 361 | 2026-10-16T01:52:10+00:00 | Vulnerability · Source |
| CVE-2024-41032 | suse_vex | SUSE CVE CVE-2024-41032 | known affected: 394 known not affected: 354 recommended: 355 | 2026-10-16T01:52:08+00:00 | Vulnerability · Source |
| CVE-2024-41035 | suse_vex | SUSE CVE CVE-2024-41035 | known affected: 590 known not affected: 18 recommended: 747 | 2026-10-16T01:52:06+00:00 | Vulnerability · Source |
| CVE-2024-41036 | suse_vex | SUSE CVE CVE-2024-41036 | known affected: 340 known not affected: 266 recommended: 643 | 2026-10-16T01:52:04+00:00 | Vulnerability · Source |
| CVE-2026-108266 | microsoft_vex | Privasys rustls fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session | known not affected: 3 | 2026-10-16T01:52:02+00:00 | Vulnerability · Source |
| CVE-2024-41038 | suse_vex | SUSE CVE CVE-2024-41038 | known affected: 393 known not affected: 207 recommended: 663 | 2026-10-16T01:52:02+00:00 | Vulnerability · Source |
| CVE-2024-41039 | suse_vex | SUSE CVE CVE-2024-41039 | known affected: 393 known not affected: 207 recommended: 663 | 2026-10-16T01:52:00+00:00 | Vulnerability · Source |
| CVE-2026-108267 | microsoft_vex | Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session | known not affected: 5 | 2026-10-16T01:51:58+00:00 | Vulnerability · Source |
| CVE-2024-41043 | suse_vex | SUSE CVE CVE-2024-41043 | known not affected: 379 | 2026-10-16T01:51:58+00:00 | Vulnerability · Source |