VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-6475 | suse_vex | SUSE CVE CVE-2026-6475 | known affected: 527 known not affected: 265 recommended: 1070 | 2026-07-15T05:39:26+00:00 | Vulnerability · Source |
| CVE-2026-6861 | suse_vex | SUSE CVE CVE-2026-6861 | known affected: 15 known not affected: 166 recommended: 30 | 2026-07-15T05:38:26+00:00 | Vulnerability · Source |
| CVE-2026-7111 | suse_vex | SUSE CVE CVE-2026-7111 | known affected: 7 recommended: 20 | 2026-07-15T05:38:19+00:00 | Vulnerability · Source |
| CVE-2026-7258 | suse_vex | SUSE CVE CVE-2026-7258 | known affected: 706 recommended: 1688 | 2026-07-15T05:38:17+00:00 | Vulnerability · Source |
| CVE-2026-7259 | suse_vex | SUSE CVE CVE-2026-7259 | known affected: 394 known not affected: 855 recommended: 1089 | 2026-07-15T05:38:15+00:00 | Vulnerability · Source |
| CVE-2026-7262 | suse_vex | SUSE CVE CVE-2026-7262 | known affected: 706 recommended: 1688 | 2026-07-15T05:38:13+00:00 | Vulnerability · Source |
| CVE-2026-7263 | suse_vex | SUSE CVE CVE-2026-7263 | known affected: 394 known not affected: 1561 recommended: 232 | 2026-07-15T05:38:11+00:00 | Vulnerability · Source |
| CVE-2026-7320 | suse_vex | SUSE CVE CVE-2026-7320 | known affected: 48 recommended: 124 | 2026-07-15T05:38:10+00:00 | Vulnerability · Source |
| CVE-2026-7321 | suse_vex | SUSE CVE CVE-2026-7321 | known affected: 48 recommended: 119 | 2026-07-15T05:38:09+00:00 | Vulnerability · Source |
| CVE-2026-7322 | suse_vex | SUSE CVE CVE-2026-7322 | known affected: 48 recommended: 124 | 2026-07-15T05:38:08+00:00 | Vulnerability · Source |
| CVE-2026-7323 | suse_vex | SUSE CVE CVE-2026-7323 | known affected: 48 recommended: 124 | 2026-07-15T05:38:07+00:00 | Vulnerability · Source |
| CVE-2026-7568 | suse_vex | SUSE CVE CVE-2026-7568 | known affected: 706 recommended: 1688 | 2026-07-15T05:38:00+00:00 | Vulnerability · Source |
| CVE-2026-8946 | suse_vex | SUSE CVE CVE-2026-8946 | known affected: 30 recommended: 125 | 2026-07-15T05:37:42+00:00 | Vulnerability · Source |
| CVE-2026-8947 | suse_vex | SUSE CVE CVE-2026-8947 | known affected: 30 recommended: 125 | 2026-07-15T05:37:41+00:00 | Vulnerability · Source |
| CVE-2026-8950 | suse_vex | SUSE CVE CVE-2026-8950 | known affected: 30 recommended: 125 | 2026-07-15T05:37:40+00:00 | Vulnerability · Source |
| CVE-2026-8956 | suse_vex | SUSE CVE CVE-2026-8956 | known affected: 30 recommended: 125 | 2026-07-15T05:37:37+00:00 | Vulnerability · Source |
| CVE-2026-8957 | suse_vex | SUSE CVE CVE-2026-8957 | known affected: 30 recommended: 125 | 2026-07-15T05:37:36+00:00 | Vulnerability · Source |
| CVE-2026-8958 | suse_vex | SUSE CVE CVE-2026-8958 | known affected: 30 recommended: 125 | 2026-07-15T05:37:35+00:00 | Vulnerability · Source |
| CVE-2026-8961 | suse_vex | SUSE CVE CVE-2026-8961 | known affected: 30 recommended: 125 | 2026-07-15T05:37:34+00:00 | Vulnerability · Source |
| CVE-2026-8962 | suse_vex | SUSE CVE CVE-2026-8962 | known affected: 30 recommended: 125 | 2026-07-15T05:37:33+00:00 | Vulnerability · Source |
| CVE-2026-8968 | suse_vex | SUSE CVE CVE-2026-8968 | known affected: 30 recommended: 125 | 2026-07-15T05:37:31+00:00 | Vulnerability · Source |
| CVE-2026-8970 | suse_vex | SUSE CVE CVE-2026-8970 | known affected: 30 recommended: 125 | 2026-07-15T05:37:30+00:00 | Vulnerability · Source |
| CVE-2026-8974 | suse_vex | SUSE CVE CVE-2026-8974 | known affected: 30 recommended: 125 | 2026-07-15T05:37:28+00:00 | Vulnerability · Source |
| CVE-2026-8975 | suse_vex | SUSE CVE CVE-2026-8975 | known affected: 30 recommended: 125 | 2026-07-15T05:37:27+00:00 | Vulnerability · Source |
| CVE-2026-9678 | suse_vex | SUSE CVE CVE-2026-9678 | known affected: 209 recommended: 59 | 2026-07-15T05:37:15+00:00 | Vulnerability · Source |
| CVE-2026-10197 | suse_vex | SUSE CVE CVE-2026-10197 | known affected: 5 recommended: 6 | 2026-07-15T05:37:10+00:00 | Vulnerability · Source |
| CVE-2026-10199 | suse_vex | SUSE CVE CVE-2026-10199 | known affected: 5 recommended: 6 | 2026-07-15T05:37:09+00:00 | Vulnerability · Source |
| CVE-2026-10725 | suse_vex | SUSE CVE CVE-2026-10725 | known affected: 3 recommended: 5 | 2026-07-15T05:37:05+00:00 | Vulnerability · Source |
| CVE-2026-10846 | suse_vex | SUSE CVE CVE-2026-10846 | known affected: 35 recommended: 75 | 2026-07-15T05:37:04+00:00 | Vulnerability · Source |
| CVE-2026-12590 | suse_vex | SUSE CVE CVE-2026-12590 | known affected: 148 known not affected: 67 | 2026-07-15T05:36:15+00:00 | Vulnerability · Source |
| CVE-2026-12844 | suse_vex | SUSE CVE CVE-2026-12844 | known affected: 6 recommended: 23 | 2026-07-15T05:36:13+00:00 | Vulnerability · Source |
| CVE-2026-15505 | suse_vex | SUSE CVE CVE-2026-15505 | No product status | 2026-07-15T05:35:55+00:00 | Vulnerability · Source |
| CVE-2026-15685 | suse_vex | SUSE CVE CVE-2026-15685 | No product status | 2026-07-15T05:35:54+00:00 | Vulnerability · Source |
| CVE-2026-20676 | suse_vex | SUSE CVE CVE-2026-20676 | known affected: 88 recommended: 503 | 2026-07-15T05:35:33+00:00 | Vulnerability · Source |
| CVE-2026-20691 | suse_vex | SUSE CVE CVE-2026-20691 | known affected: 122 recommended: 311 | 2026-07-15T05:35:32+00:00 | Vulnerability · Source |
| CVE-2026-21226 | suse_vex | SUSE CVE CVE-2026-21226 | known affected: 414 recommended: 5345 | 2026-07-15T05:35:27+00:00 | Vulnerability · Source |
| CVE-2026-21428 | suse_vex | SUSE CVE CVE-2026-21428 | known affected: 5 recommended: 8 | 2026-07-15T05:35:25+00:00 | Vulnerability · Source |
| CVE-2026-21444 | suse_vex | SUSE CVE CVE-2026-21444 | known not affected: 67 recommended: 7 | 2026-07-15T05:35:24+00:00 | Vulnerability · Source |
| CVE-2026-21637 | suse_vex | SUSE CVE CVE-2026-21637 | known affected: 163 recommended: 152 | 2026-07-15T05:35:21+00:00 | Vulnerability · Source |
| CVE-2026-21710 | suse_vex | SUSE CVE CVE-2026-21710 | known affected: 142 recommended: 137 | 2026-07-15T05:35:20+00:00 | Vulnerability · Source |
| CVE-2026-21713 | suse_vex | SUSE CVE CVE-2026-21713 | known affected: 142 recommended: 129 | 2026-07-15T05:35:18+00:00 | Vulnerability · Source |
| CVE-2026-21715 | suse_vex | SUSE CVE CVE-2026-21715 | known affected: 22 known not affected: 131 recommended: 129 | 2026-07-15T05:35:17+00:00 | Vulnerability · Source |
| CVE-2026-21716 | suse_vex | SUSE CVE CVE-2026-21716 | known affected: 22 known not affected: 131 recommended: 129 | 2026-07-15T05:35:16+00:00 | Vulnerability · Source |
| CVE-2026-21863 | suse_vex | SUSE CVE CVE-2026-21863 | known affected: 16 recommended: 31 | 2026-07-15T05:35:12+00:00 | Vulnerability · Source |
| CVE-2026-21925 | suse_vex | SUSE CVE CVE-2026-21925 | known affected: 394 known not affected: 88 recommended: 836 | 2026-07-15T05:35:11+00:00 | Vulnerability · Source |
| CVE-2026-21933 | suse_vex | SUSE CVE CVE-2026-21933 | known affected: 394 known not affected: 88 recommended: 836 | 2026-07-15T05:35:08+00:00 | Vulnerability · Source |
| CVE-2026-22693 | suse_vex | SUSE CVE CVE-2026-22693 | known affected: 456 known not affected: 149 recommended: 93 | 2026-07-15T05:34:56+00:00 | Vulnerability · Source |
| CVE-2026-22701 | suse_vex | SUSE CVE CVE-2026-22701 | known affected: 25 recommended: 19 | 2026-07-15T05:34:54+00:00 | Vulnerability · Source |
| CVE-2026-22702 | suse_vex | SUSE CVE CVE-2026-22702 | known affected: 6 known not affected: 37 recommended: 13 | 2026-07-15T05:34:53+00:00 | Vulnerability · Source |
| CVE-2026-22770 | suse_vex | SUSE CVE CVE-2026-22770 | known not affected: 179 recommended: 160 | 2026-07-15T05:34:51+00:00 | Vulnerability · Source |