VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-87876 | suse_vex | SUSE CVE CVE-2026-87876 | known affected: 395 | 2026-10-16T23:48:36+00:00 | Vulnerability · Source |
| CVE-2026-88038 | suse_vex | SUSE CVE CVE-2026-88038 | known affected: 262 known not affected: 64 | 2026-10-16T23:48:34+00:00 | Vulnerability · Source |
| CVE-2026-89156 | suse_vex | SUSE CVE CVE-2026-89156 | known affected: 394 known not affected: 391 recommended: 137 | 2026-10-16T23:48:31+00:00 | Vulnerability · Source |
| CVE-2026-89157 | suse_vex | SUSE CVE CVE-2026-89157 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-16T23:48:29+00:00 | Vulnerability · Source |
| CVE-2026-89158 | suse_vex | SUSE CVE CVE-2026-89158 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-16T23:48:27+00:00 | Vulnerability · Source |
| CVE-2026-89160 | suse_vex | SUSE CVE CVE-2026-89160 | known affected: 466 known not affected: 319 recommended: 137 | 2026-10-16T23:48:25+00:00 | Vulnerability · Source |
| CVE-2026-89622 | suse_vex | SUSE CVE CVE-2026-89622 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-16T23:47:21+00:00 | Vulnerability · Source |
| CVE-2026-90711 | suse_vex | SUSE CVE CVE-2026-90711 | known affected: 202 known not affected: 236 | 2026-10-16T23:45:11+00:00 | Vulnerability · Source |
| CVE-2026-90771 | suse_vex | SUSE CVE CVE-2026-90771 | known affected: 11 known not affected: 326 | 2026-10-16T23:45:09+00:00 | Vulnerability · Source |
| CVE-2026-90776 | suse_vex | SUSE CVE CVE-2026-90776 | known affected: 131 known not affected: 301 | 2026-10-16T23:45:08+00:00 | Vulnerability · Source |
| CVE-2026-90949 | suse_vex | SUSE CVE CVE-2026-90949 | known not affected: 26 recommended: 9 | 2026-10-16T23:45:06+00:00 | Vulnerability · Source |
| CVE-2026-91142 | suse_vex | SUSE CVE CVE-2026-91142 | known affected: 98 | 2026-10-16T23:45:02+00:00 | Vulnerability · Source |
| CVE-2026-91147 | suse_vex | SUSE CVE CVE-2026-91147 | known affected: 84 known not affected: 14 | 2026-10-16T23:45:00+00:00 | Vulnerability · Source |
| CVE-2026-91149 | suse_vex | SUSE CVE CVE-2026-91149 | known affected: 98 | 2026-10-16T23:44:59+00:00 | Vulnerability · Source |
| CVE-2026-92476 | suse_vex | SUSE CVE CVE-2026-92476 | known affected: 130 known not affected: 217 recommended: 4 | 2026-10-16T23:44:45+00:00 | Vulnerability · Source |
| CVE-2026-92595 | suse_vex | SUSE CVE CVE-2026-92595 | known affected: 131 known not affected: 301 | 2026-10-16T23:44:21+00:00 | Vulnerability · Source |
| CVE-2026-92596 | suse_vex | SUSE CVE CVE-2026-92596 | known affected: 131 known not affected: 301 | 2026-10-16T23:44:20+00:00 | Vulnerability · Source |
| CVE-2026-92597 | suse_vex | SUSE CVE CVE-2026-92597 | known affected: 131 known not affected: 301 | 2026-10-16T23:44:18+00:00 | Vulnerability · Source |
| CVE-2026-92598 | suse_vex | SUSE CVE CVE-2026-92598 | known affected: 131 known not affected: 301 | 2026-10-16T23:44:17+00:00 | Vulnerability · Source |
| CVE-2026-92599 | suse_vex | SUSE CVE CVE-2026-92599 | known not affected: 337 | 2026-10-16T23:44:15+00:00 | Vulnerability · Source |
| CVE-2026-92745 | suse_vex | SUSE CVE CVE-2026-92745 | known affected: 6 known not affected: 5 | 2026-10-16T23:44:14+00:00 | Vulnerability · Source |
| CVE-2026-92747 | suse_vex | SUSE CVE CVE-2026-92747 | known affected: 6 known not affected: 5 | 2026-10-16T23:44:12+00:00 | Vulnerability · Source |
| CVE-2026-92768 | suse_vex | SUSE CVE CVE-2026-92768 | known affected: 6 known not affected: 5 | 2026-10-16T23:44:11+00:00 | Vulnerability · Source |
| CVE-2026-92821 | suse_vex | SUSE CVE CVE-2026-92821 | known affected: 938 | 2026-10-16T23:44:09+00:00 | Vulnerability · Source |
| CVE-2026-93435 | suse_vex | SUSE CVE CVE-2026-93435 | known affected: 229 known not affected: 301 | 2026-10-16T23:43:41+00:00 | Vulnerability · Source |
| CVE-2026-93590 | suse_vex | SUSE CVE CVE-2026-93590 | known affected: 81 known not affected: 302 recommended: 15 | 2026-10-16T23:43:31+00:00 | Vulnerability · Source |
| CVE-2026-93690 | suse_vex | SUSE CVE CVE-2026-93690 | known affected: 262 known not affected: 328 | 2026-10-16T23:43:29+00:00 | Vulnerability · Source |
| CVE-2026-93748 | suse_vex | SUSE CVE CVE-2026-93748 | known affected: 111 known not affected: 419 | 2026-10-16T23:43:27+00:00 | Vulnerability · Source |
| CVE-2026-93750 | suse_vex | SUSE CVE CVE-2026-93750 | known affected: 111 known not affected: 419 | 2026-10-16T23:43:26+00:00 | Vulnerability · Source |
| CVE-2026-93751 | suse_vex | SUSE CVE CVE-2026-93751 | known affected: 262 known not affected: 328 | 2026-10-16T23:43:24+00:00 | Vulnerability · Source |
| CVE-2026-93753 | suse_vex | SUSE CVE CVE-2026-93753 | known affected: 45 known not affected: 402 | 2026-10-16T23:43:22+00:00 | Vulnerability · Source |
| CVE-2026-97057 | suse_vex | SUSE CVE CVE-2026-97057 | known affected: 133 known not affected: 397 | 2026-10-16T23:42:59+00:00 | Vulnerability · Source |
| CVE-2026-97621 | suse_vex | SUSE CVE CVE-2026-97621 | known not affected: 347 | 2026-10-16T23:42:48+00:00 | Vulnerability · Source |
| CVE-2026-101894 | suse_vex | SUSE CVE CVE-2026-101894 | known affected: 294 known not affected: 231 | 2026-10-16T23:42:27+00:00 | Vulnerability · Source |
| CVE-2026-101898 | suse_vex | SUSE CVE CVE-2026-101898 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:25+00:00 | Vulnerability · Source |
| CVE-2026-101900 | suse_vex | SUSE CVE CVE-2026-101900 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:23+00:00 | Vulnerability · Source |
| CVE-2026-101901 | suse_vex | SUSE CVE CVE-2026-101901 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:21+00:00 | Vulnerability · Source |
| CVE-2026-101902 | suse_vex | SUSE CVE CVE-2026-101902 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:19+00:00 | Vulnerability · Source |
| CVE-2026-101903 | suse_vex | SUSE CVE CVE-2026-101903 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:17+00:00 | Vulnerability · Source |
| CVE-2026-101904 | suse_vex | SUSE CVE CVE-2026-101904 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:16+00:00 | Vulnerability · Source |
| CVE-2026-101905 | suse_vex | SUSE CVE CVE-2026-101905 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:14+00:00 | Vulnerability · Source |
| CVE-2026-101906 | suse_vex | SUSE CVE CVE-2026-101906 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:12+00:00 | Vulnerability · Source |
| CVE-2026-101907 | suse_vex | SUSE CVE CVE-2026-101907 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:10+00:00 | Vulnerability · Source |
| CVE-2026-101908 | suse_vex | SUSE CVE CVE-2026-101908 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:08+00:00 | Vulnerability · Source |
| CVE-2026-101909 | suse_vex | SUSE CVE CVE-2026-101909 | known affected: 111 known not affected: 339 | 2026-10-16T23:42:06+00:00 | Vulnerability · Source |
| CVE-2026-101910 | suse_vex | SUSE CVE CVE-2026-101910 | known affected: 101 known not affected: 226 | 2026-10-16T23:42:04+00:00 | Vulnerability · Source |
| CVE-2026-101911 | suse_vex | SUSE CVE CVE-2026-101911 | known affected: 162 known not affected: 165 | 2026-10-16T23:42:02+00:00 | Vulnerability · Source |
| CVE-2026-101912 | suse_vex | SUSE CVE CVE-2026-101912 | known affected: 162 known not affected: 165 | 2026-10-16T23:42:00+00:00 | Vulnerability · Source |
| CVE-2026-101913 | suse_vex | SUSE CVE CVE-2026-101913 | known affected: 162 known not affected: 165 | 2026-10-16T23:41:59+00:00 | Vulnerability · Source |
| CVE-2026-102414 | suse_vex | SUSE CVE CVE-2026-102414 | known affected: 206 known not affected: 327 | 2026-10-16T23:41:56+00:00 | Vulnerability · Source |