VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292260 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-9496 | suse_vex | SUSE CVE CVE-2026-9496 | known affected: 106 known not affected: 145 recommended: 75 | 2026-07-15T05:37:19+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-11525 | suse_vex | SUSE CVE CVE-2026-11525 | known affected: 181 recommended: 98 | 2026-07-15T05:37:02+00:00 | Vulnerability · Source |
| CVE-2026-11527 | suse_vex | SUSE CVE CVE-2026-11527 | known affected: 11 recommended: 22 | 2026-07-15T05:37:01+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-20884 | suse_vex | SUSE CVE CVE-2026-20884 | known not affected: 7 recommended: 36 | 2026-07-15T05:35:31+00:00 | Vulnerability · Source |
| CVE-2026-20889 | suse_vex | SUSE CVE CVE-2026-20889 | known not affected: 7 recommended: 38 | 2026-07-15T05:35:30+00:00 | Vulnerability · Source |
| CVE-2026-20911 | suse_vex | SUSE CVE CVE-2026-20911 | known not affected: 7 recommended: 40 | 2026-07-15T05:35:29+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-22007 | suse_vex | SUSE CVE CVE-2026-22007 | known affected: 417 known not affected: 197 recommended: 808 | 2026-07-15T05:35:05+00:00 | Vulnerability · Source |
| CVE-2026-22008 | suse_vex | SUSE CVE CVE-2026-22008 | known affected: 15 known not affected: 525 recommended: 107 | 2026-07-15T05:35:04+00:00 | Vulnerability · Source |
| CVE-2026-22013 | suse_vex | SUSE CVE CVE-2026-22013 | known affected: 565 known not affected: 49 recommended: 780 | 2026-07-15T05:35:03+00:00 | Vulnerability · Source |
| CVE-2026-22016 | suse_vex | SUSE CVE CVE-2026-22016 | known affected: 565 known not affected: 49 recommended: 801 | 2026-07-15T05:35:02+00:00 | Vulnerability · Source |
| CVE-2026-22018 | suse_vex | SUSE CVE CVE-2026-22018 | known affected: 565 known not affected: 49 recommended: 780 | 2026-07-15T05:35:00+00:00 | Vulnerability · Source |
| CVE-2026-22021 | suse_vex | SUSE CVE CVE-2026-22021 | known affected: 565 known not affected: 49 recommended: 801 | 2026-07-15T05:34:59+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 |
| CVE-2026-22776 | suse_vex | SUSE CVE CVE-2026-22776 | recommended: 8 | 2026-07-15T05:34:49+00:00 | Vulnerability · Source |
| CVE-2026-22791 | suse_vex | SUSE CVE CVE-2026-22791 | known not affected: 85 recommended: 25 | 2026-07-15T05:34:48+00:00 | Vulnerability · Source |
| CVE-2026-22854 | suse_vex | SUSE CVE CVE-2026-22854 | recommended: 182 | 2026-07-15T05:34:39+00:00 | Vulnerability · Source |
| CVE-2026-22857 | suse_vex | SUSE CVE CVE-2026-22857 | recommended: 166 | 2026-07-15T05:34:36+00:00 | Vulnerability · Source |
| CVE-2026-22860 | suse_vex | SUSE CVE CVE-2026-22860 | known affected: 13 known not affected: 79 recommended: 1 | 2026-07-15T05:34:33+00:00 | Vulnerability · Source |