VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
304370 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-89713 | suse_vex | SUSE CVE CVE-2026-89713 | known affected: 349 known not affected: 4 recommended: 4 | 2026-10-03T00:17:00+00:00 | Vulnerability · Source |
| CVE-2026-89747 | suse_vex | SUSE CVE CVE-2026-89747 | known affected: 29 known not affected: 324 recommended: 4 | 2026-10-03T00:16:58+00:00 | Vulnerability · Source |
| CVE-2026-89780 | suse_vex | SUSE CVE CVE-2026-89780 | known affected: 254 known not affected: 93 recommended: 4 | 2026-10-03T00:16:56+00:00 | Vulnerability · Source |
| CVE-2026-89798 | suse_vex | SUSE CVE CVE-2026-89798 | known affected: 41 known not affected: 306 recommended: 4 | 2026-10-03T00:16:53+00:00 | Vulnerability · Source |
| CVE-2026-89913 | suse_vex | SUSE CVE CVE-2026-89913 | known affected: 343 known not affected: 4 recommended: 4 | 2026-10-03T00:16:50+00:00 | Vulnerability · Source |
| CVE-2026-89970 | suse_vex | SUSE CVE CVE-2026-89970 | known affected: 204 known not affected: 143 recommended: 4 | 2026-10-03T00:16:47+00:00 | Vulnerability · Source |
| CVE-2026-90104 | suse_vex | SUSE CVE CVE-2026-90104 | known affected: 347 recommended: 4 | 2026-10-03T00:16:44+00:00 | Vulnerability · Source |
| CVE-2026-90151 | suse_vex | SUSE CVE CVE-2026-90151 | known affected: 347 recommended: 4 | 2026-10-03T00:16:41+00:00 | Vulnerability · Source |
| CVE-2026-90240 | suse_vex | SUSE CVE CVE-2026-90240 | known affected: 61 known not affected: 286 recommended: 4 | 2026-10-03T00:16:39+00:00 | Vulnerability · Source |
| CVE-2026-90241 | suse_vex | SUSE CVE CVE-2026-90241 | known affected: 61 known not affected: 286 recommended: 4 | 2026-10-03T00:16:36+00:00 | Vulnerability · Source |
| CVE-2026-90243 | suse_vex | SUSE CVE CVE-2026-90243 | known affected: 45 known not affected: 286 recommended: 4 | 2026-10-03T00:16:35+00:00 | Vulnerability · Source |
| CVE-2026-90259 | suse_vex | SUSE CVE CVE-2026-90259 | known affected: 343 known not affected: 4 recommended: 4 | 2026-10-03T00:16:32+00:00 | Vulnerability · Source |
| CVE-2026-90308 | suse_vex | SUSE CVE CVE-2026-90308 | known affected: 108 known not affected: 239 recommended: 4 | 2026-10-03T00:16:30+00:00 | Vulnerability · Source |
| CVE-2026-90309 | suse_vex | SUSE CVE CVE-2026-90309 | known affected: 108 known not affected: 239 recommended: 4 | 2026-10-03T00:16:28+00:00 | Vulnerability · Source |
| CVE-2026-91765 | suse_vex | SUSE CVE CVE-2026-91765 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:23+00:00 | Vulnerability · Source |
| CVE-2026-91766 | suse_vex | SUSE CVE CVE-2026-91766 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:21+00:00 | Vulnerability · Source |
| CVE-2026-91767 | suse_vex | SUSE CVE CVE-2026-91767 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:18+00:00 | Vulnerability · Source |
| CVE-2026-91768 | suse_vex | SUSE CVE CVE-2026-91768 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:15+00:00 | Vulnerability · Source |
| CVE-2026-91769 | suse_vex | SUSE CVE CVE-2026-91769 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:13+00:00 | Vulnerability · Source |
| CVE-2026-91776 | suse_vex | SUSE CVE CVE-2026-91776 | known affected: 21 recommended: 77 | 2026-10-03T00:16:11+00:00 | Vulnerability · Source |
| CVE-2026-91777 | suse_vex | SUSE CVE CVE-2026-91777 | known affected: 21 recommended: 77 | 2026-10-03T00:16:09+00:00 | Vulnerability · Source |
| CVE-2026-92842 | suse_vex | SUSE CVE CVE-2026-92842 | known affected: 2235 recommended: 47 | 2026-10-03T00:16:05+00:00 | Vulnerability · Source |
| CVE-2026-92925 | suse_vex | SUSE CVE CVE-2026-92925 | known affected: 30 known not affected: 19 recommended: 17 | 2026-10-03T00:16:03+00:00 | Vulnerability · Source |
| CVE-2026-93107 | suse_vex | SUSE CVE CVE-2026-93107 | known affected: 108 known not affected: 239 recommended: 4 | 2026-10-03T00:16:00+00:00 | Vulnerability · Source |
| CVE-2026-93108 | suse_vex | SUSE CVE CVE-2026-93108 | known affected: 335 known not affected: 12 recommended: 4 | 2026-10-03T00:15:57+00:00 | Vulnerability · Source |
| CVE-2026-93109 | suse_vex | SUSE CVE CVE-2026-93109 | known affected: 242 known not affected: 105 recommended: 4 | 2026-10-03T00:15:55+00:00 | Vulnerability · Source |
| CVE-2026-93110 | suse_vex | SUSE CVE CVE-2026-93110 | known affected: 242 known not affected: 105 recommended: 4 | 2026-10-03T00:15:53+00:00 | Vulnerability · Source |
| CVE-2026-93599 | suse_vex | SUSE CVE CVE-2026-93599 | known affected: 161 known not affected: 956 recommended: 7 | 2026-10-03T00:15:49+00:00 | Vulnerability · Source |
| CVE-2026-93600 | suse_vex | SUSE CVE CVE-2026-93600 | known affected: 161 known not affected: 956 recommended: 3 | 2026-10-03T00:15:46+00:00 | Vulnerability · Source |
| CVE-2026-93601 | suse_vex | SUSE CVE CVE-2026-93601 | known affected: 161 known not affected: 956 recommended: 3 | 2026-10-03T00:15:43+00:00 | Vulnerability · Source |
| CVE-2026-93602 | suse_vex | SUSE CVE CVE-2026-93602 | known affected: 161 known not affected: 956 recommended: 3 | 2026-10-03T00:15:41+00:00 | Vulnerability · Source |
| CVE-2026-93682 | suse_vex | SUSE CVE CVE-2026-93682 | known affected: 2235 recommended: 47 | 2026-10-03T00:15:39+00:00 | Vulnerability · Source |
| CVE-2026-94653 | suse_vex | SUSE CVE CVE-2026-94653 | No product status | 2026-10-03T00:15:34+00:00 | Vulnerability · Source |
| CVE-2026-94654 | suse_vex | SUSE CVE CVE-2026-94654 | No product status | 2026-10-03T00:15:32+00:00 | Vulnerability · Source |
| CVE-2026-94655 | suse_vex | SUSE CVE CVE-2026-94655 | No product status | 2026-10-03T00:15:30+00:00 | Vulnerability · Source |
| CVE-2026-94656 | suse_vex | SUSE CVE CVE-2026-94656 | No product status | 2026-10-03T00:15:28+00:00 | Vulnerability · Source |
| CVE-2026-94657 | suse_vex | SUSE CVE CVE-2026-94657 | No product status | 2026-10-03T00:15:26+00:00 | Vulnerability · Source |
| CVE-2026-94658 | suse_vex | SUSE CVE CVE-2026-94658 | No product status | 2026-10-03T00:15:23+00:00 | Vulnerability · Source |
| CVE-2026-96277 | suse_vex | SUSE CVE CVE-2026-96277 | No product status | 2026-10-03T00:14:32+00:00 | Vulnerability · Source |
| CVE-2026-96286 | suse_vex | SUSE CVE CVE-2026-96286 | No product status | 2026-10-03T00:14:29+00:00 | Vulnerability · Source |
| CVE-2026-96287 | suse_vex | SUSE CVE CVE-2026-96287 | No product status | 2026-10-03T00:14:26+00:00 | Vulnerability · Source |
| CVE-2026-96288 | suse_vex | SUSE CVE CVE-2026-96288 | No product status | 2026-10-03T00:14:24+00:00 | Vulnerability · Source |
| CVE-2026-96289 | suse_vex | SUSE CVE CVE-2026-96289 | No product status | 2026-10-03T00:14:21+00:00 | Vulnerability · Source |
| CVE-2026-96292 | suse_vex | SUSE CVE CVE-2026-96292 | No product status | 2026-10-03T00:14:18+00:00 | Vulnerability · Source |
| CVE-2026-100760 | suse_vex | SUSE CVE CVE-2026-100760 | known affected: 176 recommended: 9 | 2026-10-03T00:14:13+00:00 | Vulnerability · Source |
| CVE-2026-100774 | suse_vex | SUSE CVE CVE-2026-100774 | known affected: 176 recommended: 9 | 2026-10-03T00:14:08+00:00 | Vulnerability · Source |
| CVE-2026-100785 | suse_vex | SUSE CVE CVE-2026-100785 | known affected: 176 recommended: 9 | 2026-10-03T00:14:03+00:00 | Vulnerability · Source |
| CVE-2026-100817 | suse_vex | SUSE CVE CVE-2026-100817 | known affected: 164 | 2026-10-03T00:13:53+00:00 | Vulnerability · Source |
| CVE-2026-100822 | suse_vex | SUSE CVE CVE-2026-100822 | known affected: 176 recommended: 9 | 2026-10-03T00:13:50+00:00 | Vulnerability · Source |
| CVE-2026-100829 | suse_vex | SUSE CVE CVE-2026-100829 | known affected: 176 recommended: 9 | 2026-10-03T00:13:46+00:00 | Vulnerability · Source |