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-68284 | suse_vex | SUSE CVE CVE-2025-68284 | known affected: 409 known not affected: 260 recommended: 698 | 2026-10-16T00:52:17+00:00 | Vulnerability · Source |
| CVE-2025-68297 | suse_vex | SUSE CVE CVE-2025-68297 | known affected: 553 known not affected: 321 recommended: 320 | 2026-10-16T00:52:14+00:00 | Vulnerability · Source |
| CVE-2025-68303 | suse_vex | SUSE CVE CVE-2025-68303 | known affected: 690 known not affected: 80 recommended: 438 | 2026-10-16T00:52:11+00:00 | Vulnerability · Source |
| CVE-2025-68313 | suse_vex | SUSE CVE CVE-2025-68313 | known affected: 396 known not affected: 457 recommended: 415 | 2026-10-16T00:52:09+00:00 | Vulnerability · Source |
| CVE-2025-68354 | suse_vex | SUSE CVE CVE-2025-68354 | known affected: 720 known not affected: 55 recommended: 444 | 2026-10-16T00:52:06+00:00 | Vulnerability · Source |
| CVE-2025-68743 | suse_vex | SUSE CVE CVE-2025-68743 | known affected: 7 known not affected: 535 recommended: 209 | 2026-10-16T00:52:03+00:00 | Vulnerability · Source |
| CVE-2025-68758 | suse_vex | SUSE CVE CVE-2025-68758 | known affected: 546 known not affected: 204 recommended: 421 | 2026-10-16T00:52:01+00:00 | Vulnerability · Source |
| CVE-2025-68940 | suse_vex | SUSE CVE CVE-2025-68940 | recommended: 2 | 2026-10-16T00:51:57+00:00 | Vulnerability · Source |
| CVE-2025-71069 | suse_vex | SUSE CVE CVE-2025-71069 | known affected: 0 known not affected: 457 | 2026-10-16T00:51:53+00:00 | Vulnerability · Source |
| CVE-2025-71124 | suse_vex | SUSE CVE CVE-2025-71124 | known affected: 0 known not affected: 426 recommended: 58 | 2026-10-16T00:51:50+00:00 | Vulnerability · Source |
| CVE-2025-71146 | suse_vex | SUSE CVE CVE-2025-71146 | known affected: 0 known not affected: 437 | 2026-10-16T00:51:49+00:00 | Vulnerability · Source |
| CVE-2025-71158 | suse_vex | SUSE CVE CVE-2025-71158 | known affected: 0 known not affected: 441 | 2026-10-16T00:51:46+00:00 | Vulnerability · Source |
| CVE-2025-71182 | suse_vex | SUSE CVE CVE-2025-71182 | known affected: 554 known not affected: 234 recommended: 311 | 2026-10-16T00:51:43+00:00 | Vulnerability · Source |
| CVE-2025-71236 | suse_vex | SUSE CVE CVE-2025-71236 | known affected: 505 known not affected: 227 recommended: 338 | 2026-10-16T00:51:40+00:00 | Vulnerability · Source |
| CVE-2025-71287 | suse_vex | SUSE CVE CVE-2025-71287 | known affected: 366 known not affected: 23 recommended: 203 | 2026-10-16T00:51:37+00:00 | Vulnerability · Source |
| CVE-2026-0636 | suse_vex | SUSE CVE CVE-2026-0636 | known affected: 40 recommended: 108 | 2026-10-16T00:51:35+00:00 | Vulnerability · Source |
| CVE-2026-0665 | suse_vex | SUSE CVE CVE-2026-0665 | known affected: 534 known not affected: 1032 recommended: 656 | 2026-10-16T00:51:33+00:00 | Vulnerability · Source |
| CVE-2026-0672 | suse_vex | SUSE CVE CVE-2026-0672 | known affected: 486 known not affected: 60 recommended: 885 | 2026-10-16T00:51:30+00:00 | Vulnerability · Source |
| CVE-2026-0799 | suse_vex | SUSE CVE CVE-2026-0799 | known affected: 430 recommended: 65 | 2026-10-16T00:51:28+00:00 | Vulnerability · Source |
| CVE-2026-0861 | suse_vex | SUSE CVE CVE-2026-0861 | known affected: 407 known not affected: 349 recommended: 888 | 2026-10-16T00:51:25+00:00 | Vulnerability · Source |
| CVE-2026-0865 | suse_vex | SUSE CVE CVE-2026-0865 | known affected: 546 recommended: 939 | 2026-10-16T00:51:19+00:00 | Vulnerability · Source |
| CVE-2026-0877 | suse_vex | SUSE CVE CVE-2026-0877 | known affected: 72 recommended: 147 | 2026-10-16T00:51:17+00:00 | Vulnerability · Source |
| CVE-2026-0878 | suse_vex | SUSE CVE CVE-2026-0878 | known affected: 72 recommended: 147 | 2026-10-16T00:51:15+00:00 | Vulnerability · Source |
| CVE-2026-0879 | suse_vex | SUSE CVE CVE-2026-0879 | known affected: 72 recommended: 147 | 2026-10-16T00:51:13+00:00 | Vulnerability · Source |
| CVE-2026-0880 | suse_vex | SUSE CVE CVE-2026-0880 | known affected: 72 recommended: 147 | 2026-10-16T00:51:10+00:00 | Vulnerability · Source |
| CVE-2026-0882 | suse_vex | SUSE CVE CVE-2026-0882 | known affected: 72 recommended: 147 | 2026-10-16T00:51:08+00:00 | Vulnerability · Source |
| CVE-2026-0883 | suse_vex | SUSE CVE CVE-2026-0883 | known affected: 72 recommended: 147 | 2026-10-16T00:51:05+00:00 | Vulnerability · Source |
| CVE-2026-0884 | suse_vex | SUSE CVE CVE-2026-0884 | known affected: 72 recommended: 147 | 2026-10-16T00:51:03+00:00 | Vulnerability · Source |
| CVE-2026-0885 | suse_vex | SUSE CVE CVE-2026-0885 | known affected: 72 recommended: 147 | 2026-10-16T00:51:02+00:00 | Vulnerability · Source |
| CVE-2026-0886 | suse_vex | SUSE CVE CVE-2026-0886 | known affected: 72 recommended: 147 | 2026-10-16T00:51:00+00:00 | Vulnerability · Source |
| CVE-2026-0887 | suse_vex | SUSE CVE CVE-2026-0887 | known affected: 72 recommended: 147 | 2026-10-16T00:50:58+00:00 | Vulnerability · Source |
| CVE-2026-0890 | suse_vex | SUSE CVE CVE-2026-0890 | known affected: 72 recommended: 147 | 2026-10-16T00:50:57+00:00 | Vulnerability · Source |
| CVE-2026-0891 | suse_vex | SUSE CVE CVE-2026-0891 | known affected: 72 recommended: 147 | 2026-10-16T00:50:55+00:00 | Vulnerability · Source |
| CVE-2026-0915 | suse_vex | SUSE CVE CVE-2026-0915 | known affected: 619 recommended: 995 | 2026-10-16T00:50:52+00:00 | Vulnerability · Source |
| CVE-2026-0959 | suse_vex | SUSE CVE CVE-2026-0959 | known affected: 18 known not affected: 237 recommended: 184 | 2026-10-16T00:50:50+00:00 | Vulnerability · Source |
| CVE-2026-0961 | suse_vex | SUSE CVE CVE-2026-0961 | known affected: 0 known not affected: 261 recommended: 166 | 2026-10-16T00:50:48+00:00 | Vulnerability · Source |
| CVE-2026-0962 | suse_vex | SUSE CVE CVE-2026-0962 | known affected: 18 known not affected: 237 recommended: 184 | 2026-10-16T00:50:45+00:00 | Vulnerability · Source |
| CVE-2026-0964 | suse_vex | SUSE CVE CVE-2026-0964 | known affected: 507 recommended: 108 | 2026-10-16T00:50:43+00:00 | Vulnerability · Source |
| CVE-2026-0965 | suse_vex | SUSE CVE CVE-2026-0965 | known affected: 507 recommended: 108 | 2026-10-16T00:50:41+00:00 | Vulnerability · Source |
| CVE-2026-0966 | suse_vex | SUSE CVE CVE-2026-0966 | known affected: 507 recommended: 108 | 2026-10-16T00:50:39+00:00 | Vulnerability · Source |
| CVE-2026-0967 | suse_vex | SUSE CVE CVE-2026-0967 | known affected: 507 recommended: 108 | 2026-10-16T00:50:37+00:00 | Vulnerability · Source |
| CVE-2026-0968 | suse_vex | SUSE CVE CVE-2026-0968 | known affected: 354 known not affected: 153 recommended: 108 | 2026-10-16T00:50:35+00:00 | Vulnerability · Source |
| CVE-2026-0989 | suse_vex | SUSE CVE CVE-2026-0989 | known affected: 564 recommended: 151 | 2026-10-16T00:50:33+00:00 | Vulnerability · Source |
| CVE-2026-0990 | suse_vex | SUSE CVE CVE-2026-0990 | known affected: 552 recommended: 165 | 2026-10-16T00:50:31+00:00 | Vulnerability · Source |
| CVE-2026-0992 | suse_vex | SUSE CVE CVE-2026-0992 | known affected: 564 recommended: 165 | 2026-10-16T00:50:29+00:00 | Vulnerability · Source |
| CVE-2026-1299 | suse_vex | SUSE CVE CVE-2026-1299 | known affected: 585 known not affected: 40 recommended: 892 | 2026-10-16T00:50:24+00:00 | Vulnerability · Source |
| CVE-2026-1502 | suse_vex | SUSE CVE CVE-2026-1502 | known affected: 568 known not affected: 21 recommended: 854 | 2026-10-16T00:50:22+00:00 | Vulnerability · Source |
| CVE-2026-1709 | suse_vex | SUSE CVE CVE-2026-1709 | known affected: 0 known not affected: 163 recommended: 65 | 2026-10-16T00:50:19+00:00 | Vulnerability · Source |
| CVE-2026-1757 | suse_vex | SUSE CVE CVE-2026-1757 | known affected: 552 recommended: 165 | 2026-10-16T00:50:17+00:00 | Vulnerability · Source |
| CVE-2026-1858 | suse_vex | SUSE CVE CVE-2026-1858 | known affected: 0 known not affected: 51 | 2026-10-16T00:50:15+00:00 | Vulnerability · Source |