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-2026-86805 | suse_vex | SUSE CVE CVE-2026-86805 | known affected: 381 recommended: 231 | 2026-10-15T23:57:47+00:00 | Vulnerability · Source |
| CVE-2026-86818 | suse_vex | SUSE CVE CVE-2026-86818 | known affected: 9 known not affected: 147 | 2026-10-15T23:57:46+00:00 | Vulnerability · Source |
| CVE-2026-87910 | suse_vex | SUSE CVE CVE-2026-87910 | known affected: 394 known not affected: 79 | 2026-10-15T23:57:29+00:00 | Vulnerability · Source |
| CVE-2026-88806 | suse_vex | SUSE CVE CVE-2026-88806 | known affected: 515 recommended: 147 | 2026-10-15T23:57:26+00:00 | Vulnerability · Source |
| CVE-2026-89092 | suse_vex | SUSE CVE CVE-2026-89092 | known affected: 412 recommended: 171 | 2026-10-15T23:57:19+00:00 | Vulnerability · Source |
| CVE-2026-89407 | suse_vex | SUSE CVE CVE-2026-89407 | known affected: 22 recommended: 96 | 2026-10-15T23:57:04+00:00 | Vulnerability · Source |
| CVE-2026-89425 | suse_vex | SUSE CVE CVE-2026-89425 | known affected: 17 recommended: 96 | 2026-10-15T23:57:02+00:00 | Vulnerability · Source |
| CVE-2026-90253 | suse_vex | SUSE CVE CVE-2026-90253 | known affected: 30 known not affected: 317 | 2026-10-15T23:53:57+00:00 | Vulnerability · Source |
| CVE-2026-90288 | suse_vex | SUSE CVE CVE-2026-90288 | known not affected: 347 | 2026-10-15T23:53:43+00:00 | Vulnerability · Source |
| CVE-2026-90297 | suse_vex | SUSE CVE CVE-2026-90297 | known affected: 263 known not affected: 84 | 2026-10-15T23:53:34+00:00 | Vulnerability · Source |
| CVE-2026-90325 | suse_vex | SUSE CVE CVE-2026-90325 | known not affected: 347 | 2026-10-15T23:53:26+00:00 | Vulnerability · Source |
| CVE-2026-90326 | suse_vex | SUSE CVE CVE-2026-90326 | known not affected: 347 | 2026-10-15T23:53:24+00:00 | Vulnerability · Source |
| CVE-2026-90349 | suse_vex | SUSE CVE CVE-2026-90349 | known not affected: 347 | 2026-10-15T23:53:21+00:00 | Vulnerability · Source |
| CVE-2026-90350 | suse_vex | SUSE CVE CVE-2026-90350 | known not affected: 347 | 2026-10-15T23:53:18+00:00 | Vulnerability · Source |
| CVE-2026-90352 | suse_vex | SUSE CVE CVE-2026-90352 | known affected: 30 known not affected: 317 | 2026-10-15T23:53:16+00:00 | Vulnerability · Source |
| CVE-2026-90357 | suse_vex | SUSE CVE CVE-2026-90357 | known affected: 84 known not affected: 263 | 2026-10-15T23:53:14+00:00 | Vulnerability · Source |
| CVE-2026-90439 | suse_vex | SUSE CVE CVE-2026-90439 | known affected: 66 recommended: 2 | 2026-10-15T23:52:57+00:00 | Vulnerability · Source |
| CVE-2026-90616 | suse_vex | SUSE CVE CVE-2026-90616 | known affected: 216 recommended: 6 | 2026-10-15T23:52:55+00:00 | Vulnerability · Source |
| CVE-2026-91776 | suse_vex | SUSE CVE CVE-2026-91776 | known affected: 28 recommended: 77 | 2026-10-15T23:52:41+00:00 | Vulnerability · Source |
| CVE-2026-91777 | suse_vex | SUSE CVE CVE-2026-91777 | known affected: 28 recommended: 77 | 2026-10-15T23:52:39+00:00 | Vulnerability · Source |
| CVE-2026-92005 | suse_vex | SUSE CVE CVE-2026-92005 | known affected: 71 recommended: 99 | 2026-10-15T23:52:32+00:00 | Vulnerability · Source |
| CVE-2026-92006 | suse_vex | SUSE CVE CVE-2026-92006 | known affected: 71 recommended: 99 | 2026-10-15T23:52:30+00:00 | Vulnerability · Source |
| CVE-2026-92007 | suse_vex | SUSE CVE CVE-2026-92007 | known affected: 71 recommended: 99 | 2026-10-15T23:52:28+00:00 | Vulnerability · Source |
| CVE-2026-92008 | suse_vex | SUSE CVE CVE-2026-92008 | known affected: 71 recommended: 99 | 2026-10-15T23:52:25+00:00 | Vulnerability · Source |
| CVE-2026-92009 | suse_vex | SUSE CVE CVE-2026-92009 | known affected: 71 recommended: 99 | 2026-10-15T23:52:23+00:00 | Vulnerability · Source |
| CVE-2026-92010 | suse_vex | SUSE CVE CVE-2026-92010 | known affected: 71 recommended: 99 | 2026-10-15T23:52:21+00:00 | Vulnerability · Source |
| CVE-2026-92011 | suse_vex | SUSE CVE CVE-2026-92011 | known affected: 71 recommended: 99 | 2026-10-15T23:52:19+00:00 | Vulnerability · Source |
| CVE-2026-92012 | suse_vex | SUSE CVE CVE-2026-92012 | known affected: 71 recommended: 99 | 2026-10-15T23:52:16+00:00 | Vulnerability · Source |
| CVE-2026-92013 | suse_vex | SUSE CVE CVE-2026-92013 | known affected: 71 recommended: 99 | 2026-10-15T23:52:14+00:00 | Vulnerability · Source |
| CVE-2026-92014 | suse_vex | SUSE CVE CVE-2026-92014 | known affected: 71 recommended: 11 | 2026-10-15T23:52:12+00:00 | Vulnerability · Source |
| CVE-2026-92015 | suse_vex | SUSE CVE CVE-2026-92015 | known affected: 71 recommended: 99 | 2026-10-15T23:52:09+00:00 | Vulnerability · Source |
| CVE-2026-92016 | suse_vex | SUSE CVE CVE-2026-92016 | known affected: 71 recommended: 99 | 2026-10-15T23:52:06+00:00 | Vulnerability · Source |
| CVE-2026-92017 | suse_vex | SUSE CVE CVE-2026-92017 | known affected: 71 recommended: 99 | 2026-10-15T23:52:03+00:00 | Vulnerability · Source |
| CVE-2026-92018 | suse_vex | SUSE CVE CVE-2026-92018 | known affected: 71 recommended: 99 | 2026-10-15T23:52:00+00:00 | Vulnerability · Source |
| CVE-2026-92019 | suse_vex | SUSE CVE CVE-2026-92019 | known affected: 71 recommended: 99 | 2026-10-15T23:51:59+00:00 | Vulnerability · Source |
| CVE-2026-92020 | suse_vex | SUSE CVE CVE-2026-92020 | known affected: 71 recommended: 99 | 2026-10-15T23:51:57+00:00 | Vulnerability · Source |
| CVE-2026-92021 | suse_vex | SUSE CVE CVE-2026-92021 | known affected: 71 recommended: 11 | 2026-10-15T23:51:55+00:00 | Vulnerability · Source |
| CVE-2026-92022 | suse_vex | SUSE CVE CVE-2026-92022 | known affected: 71 recommended: 99 | 2026-10-15T23:51:53+00:00 | Vulnerability · Source |
| CVE-2026-92023 | suse_vex | SUSE CVE CVE-2026-92023 | known affected: 71 recommended: 99 | 2026-10-15T23:51:51+00:00 | Vulnerability · Source |
| CVE-2026-92024 | suse_vex | SUSE CVE CVE-2026-92024 | known affected: 71 recommended: 99 | 2026-10-15T23:51:50+00:00 | Vulnerability · Source |
| CVE-2026-92025 | suse_vex | SUSE CVE CVE-2026-92025 | known affected: 71 recommended: 99 | 2026-10-15T23:51:48+00:00 | Vulnerability · Source |
| CVE-2026-92026 | suse_vex | SUSE CVE CVE-2026-92026 | known affected: 71 recommended: 99 | 2026-10-15T23:51:46+00:00 | Vulnerability · Source |
| CVE-2026-92027 | suse_vex | SUSE CVE CVE-2026-92027 | known affected: 71 recommended: 99 | 2026-10-15T23:51:44+00:00 | Vulnerability · Source |
| CVE-2026-92028 | suse_vex | SUSE CVE CVE-2026-92028 | known affected: 71 recommended: 99 | 2026-10-15T23:51:42+00:00 | Vulnerability · Source |
| CVE-2026-92029 | suse_vex | SUSE CVE CVE-2026-92029 | known affected: 71 recommended: 99 | 2026-10-15T23:51:40+00:00 | Vulnerability · Source |
| CVE-2026-92030 | suse_vex | SUSE CVE CVE-2026-92030 | known affected: 71 recommended: 99 | 2026-10-15T23:51:37+00:00 | Vulnerability · Source |
| CVE-2026-92031 | suse_vex | SUSE CVE CVE-2026-92031 | known affected: 71 recommended: 99 | 2026-10-15T23:51:35+00:00 | Vulnerability · Source |
| CVE-2026-92032 | suse_vex | SUSE CVE CVE-2026-92032 | known affected: 71 recommended: 99 | 2026-10-15T23:51:33+00:00 | Vulnerability · Source |
| CVE-2026-92238 | suse_vex | SUSE CVE CVE-2026-92238 | known affected: 71 recommended: 7 | 2026-10-15T23:51:31+00:00 | Vulnerability · Source |
| CVE-2026-92239 | suse_vex | SUSE CVE CVE-2026-92239 | known affected: 71 recommended: 7 | 2026-10-15T23:51:29+00:00 | Vulnerability · Source |