VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305220 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-84639 | suse_vex | SUSE CVE CVE-2026-84639 | known affected: 80 recommended: 22 | 2026-10-03T23:56:16+00:00 | Vulnerability · Source |
| CVE-2026-84640 | suse_vex | SUSE CVE CVE-2026-84640 | known affected: 80 recommended: 22 | 2026-10-03T23:56:15+00:00 | Vulnerability · Source |
| CVE-2026-84641 | suse_vex | SUSE CVE CVE-2026-84641 | known affected: 80 recommended: 22 | 2026-10-03T23:56:13+00:00 | Vulnerability · Source |
| CVE-2026-89479 | suse_vex | SUSE CVE CVE-2026-89479 | known affected: 353 recommended: 4 | 2026-10-03T23:56:10+00:00 | Vulnerability · Source |
| CVE-2026-89569 | suse_vex | SUSE CVE CVE-2026-89569 | known affected: 265 known not affected: 88 recommended: 4 | 2026-10-03T23:56:05+00:00 | Vulnerability · Source |
| CVE-2026-89603 | suse_vex | SUSE CVE CVE-2026-89603 | known affected: 210 known not affected: 143 recommended: 4 | 2026-10-03T23:56:03+00:00 | Vulnerability · Source |
| CVE-2026-89631 | suse_vex | SUSE CVE CVE-2026-89631 | known affected: 353 recommended: 4 | 2026-10-03T23:56:01+00:00 | Vulnerability · Source |
| CVE-2026-89636 | suse_vex | SUSE CVE CVE-2026-89636 | known affected: 347 known not affected: 6 recommended: 4 | 2026-10-03T23:56:00+00:00 | Vulnerability · Source |
| CVE-2026-89638 | suse_vex | SUSE CVE CVE-2026-89638 | known affected: 353 recommended: 4 | 2026-10-03T23:55:58+00:00 | Vulnerability · Source |
| CVE-2026-89777 | suse_vex | SUSE CVE CVE-2026-89777 | known affected: 254 known not affected: 93 recommended: 4 | 2026-10-03T23:55:56+00:00 | Vulnerability · Source |
| CVE-2026-89984 | suse_vex | SUSE CVE CVE-2026-89984 | known affected: 204 known not affected: 143 recommended: 4 | 2026-10-03T23:55:52+00:00 | Vulnerability · Source |
| CVE-2026-92005 | suse_vex | SUSE CVE CVE-2026-92005 | known affected: 71 recommended: 99 | 2026-10-03T23:55:48+00:00 | Vulnerability · Source |
| CVE-2026-92006 | suse_vex | SUSE CVE CVE-2026-92006 | known affected: 71 recommended: 99 | 2026-10-03T23:55:46+00:00 | Vulnerability · Source |
| CVE-2026-92007 | suse_vex | SUSE CVE CVE-2026-92007 | known affected: 71 recommended: 99 | 2026-10-03T23:55:45+00:00 | Vulnerability · Source |
| CVE-2026-92008 | suse_vex | SUSE CVE CVE-2026-92008 | known affected: 71 recommended: 99 | 2026-10-03T23:55:43+00:00 | Vulnerability · Source |
| CVE-2026-92009 | suse_vex | SUSE CVE CVE-2026-92009 | known affected: 71 recommended: 99 | 2026-10-03T23:55:41+00:00 | Vulnerability · Source |
| CVE-2026-92010 | suse_vex | SUSE CVE CVE-2026-92010 | known affected: 71 recommended: 99 | 2026-10-03T23:55:38+00:00 | Vulnerability · Source |
| CVE-2026-92011 | suse_vex | SUSE CVE CVE-2026-92011 | known affected: 71 recommended: 99 | 2026-10-03T23:55:37+00:00 | Vulnerability · Source |
| CVE-2026-92012 | suse_vex | SUSE CVE CVE-2026-92012 | known affected: 71 recommended: 99 | 2026-10-03T23:55:35+00:00 | Vulnerability · Source |
| CVE-2026-92013 | suse_vex | SUSE CVE CVE-2026-92013 | known affected: 71 recommended: 99 | 2026-10-03T23:55:33+00:00 | Vulnerability · Source |
| CVE-2026-92014 | suse_vex | SUSE CVE CVE-2026-92014 | known affected: 71 recommended: 11 | 2026-10-03T23:55:32+00:00 | Vulnerability · Source |
| CVE-2026-92015 | suse_vex | SUSE CVE CVE-2026-92015 | known affected: 71 recommended: 99 | 2026-10-03T23:55:30+00:00 | Vulnerability · Source |
| CVE-2026-92016 | suse_vex | SUSE CVE CVE-2026-92016 | known affected: 71 recommended: 99 | 2026-10-03T23:55:28+00:00 | Vulnerability · Source |
| CVE-2026-92017 | suse_vex | SUSE CVE CVE-2026-92017 | known affected: 71 recommended: 99 | 2026-10-03T23:55:26+00:00 | Vulnerability · Source |
| CVE-2026-92018 | suse_vex | SUSE CVE CVE-2026-92018 | known affected: 71 recommended: 99 | 2026-10-03T23:55:24+00:00 | Vulnerability · Source |
| CVE-2026-92019 | suse_vex | SUSE CVE CVE-2026-92019 | known affected: 71 recommended: 99 | 2026-10-03T23:55:23+00:00 | Vulnerability · Source |
| CVE-2026-92020 | suse_vex | SUSE CVE CVE-2026-92020 | known affected: 71 recommended: 99 | 2026-10-03T23:55:21+00:00 | Vulnerability · Source |
| CVE-2026-92021 | suse_vex | SUSE CVE CVE-2026-92021 | known affected: 71 recommended: 11 | 2026-10-03T23:55:18+00:00 | Vulnerability · Source |
| CVE-2026-92022 | suse_vex | SUSE CVE CVE-2026-92022 | known affected: 71 recommended: 99 | 2026-10-03T23:55:17+00:00 | Vulnerability · Source |
| CVE-2026-92023 | suse_vex | SUSE CVE CVE-2026-92023 | known affected: 71 recommended: 99 | 2026-10-03T23:55:15+00:00 | Vulnerability · Source |
| CVE-2026-92024 | suse_vex | SUSE CVE CVE-2026-92024 | known affected: 71 recommended: 99 | 2026-10-03T23:55:13+00:00 | Vulnerability · Source |
| CVE-2026-92025 | suse_vex | SUSE CVE CVE-2026-92025 | known affected: 71 recommended: 99 | 2026-10-03T23:55:12+00:00 | Vulnerability · Source |
| CVE-2026-92026 | suse_vex | SUSE CVE CVE-2026-92026 | known affected: 71 recommended: 99 | 2026-10-03T23:55:10+00:00 | Vulnerability · Source |
| CVE-2026-92027 | suse_vex | SUSE CVE CVE-2026-92027 | known affected: 71 recommended: 99 | 2026-10-03T23:55:08+00:00 | Vulnerability · Source |
| CVE-2026-92028 | suse_vex | SUSE CVE CVE-2026-92028 | known affected: 71 recommended: 99 | 2026-10-03T23:55:07+00:00 | Vulnerability · Source |
| CVE-2026-92029 | suse_vex | SUSE CVE CVE-2026-92029 | known affected: 71 recommended: 99 | 2026-10-03T23:55:05+00:00 | Vulnerability · Source |
| CVE-2026-92030 | suse_vex | SUSE CVE CVE-2026-92030 | known affected: 71 recommended: 99 | 2026-10-03T23:55:04+00:00 | Vulnerability · Source |
| CVE-2026-92031 | suse_vex | SUSE CVE CVE-2026-92031 | known affected: 71 recommended: 99 | 2026-10-03T23:55:02+00:00 | Vulnerability · Source |
| CVE-2026-92032 | suse_vex | SUSE CVE CVE-2026-92032 | known affected: 71 recommended: 99 | 2026-10-03T23:55:00+00:00 | Vulnerability · Source |
| CVE-2026-92238 | suse_vex | SUSE CVE CVE-2026-92238 | known affected: 71 recommended: 7 | 2026-10-03T23:54:58+00:00 | Vulnerability · Source |
| CVE-2026-92239 | suse_vex | SUSE CVE CVE-2026-92239 | known affected: 71 recommended: 7 | 2026-10-03T23:54:57+00:00 | Vulnerability · Source |
| CVE-2026-92240 | suse_vex | SUSE CVE CVE-2026-92240 | known affected: 71 recommended: 7 | 2026-10-03T23:54:55+00:00 | Vulnerability · Source |
| CVE-2017-7380 | suse_vex | SUSE CVE CVE-2017-7380 | known affected: 6 recommended: 28 | 2026-10-03T16:55:21+00:00 | Vulnerability · Source |
| CVE-2018-10767 | suse_vex | SUSE CVE CVE-2018-10767 | known affected: 306 recommended: 848 | 2026-10-03T16:55:01+00:00 | Vulnerability · Source |
| CVE-2018-12983 | suse_vex | SUSE CVE CVE-2018-12983 | recommended: 32 | 2026-10-03T16:54:57+00:00 | Vulnerability · Source |
| CVE-2018-20669 | suse_vex | SUSE CVE CVE-2018-20669 | known affected: 369 known not affected: 309 recommended: 1348 | 2026-10-03T16:54:47+00:00 | Vulnerability · Source |
| CVE-2019-9456 | suse_vex | SUSE CVE CVE-2019-9456 | known affected: 3 known not affected: 6 recommended: 942 | 2026-10-03T16:54:39+00:00 | Vulnerability · Source |
| CVE-2019-14835 | suse_vex | SUSE CVE CVE-2019-14835 | known affected: 257 known not affected: 2 recommended: 1178 | 2026-10-03T16:54:30+00:00 | Vulnerability · Source |
| CVE-2019-15916 | suse_vex | SUSE CVE CVE-2019-15916 | known affected: 117 known not affected: 267 recommended: 656 | 2026-10-03T16:54:26+00:00 | Vulnerability · Source |
| CVE-2019-16231 | suse_vex | SUSE CVE CVE-2019-16231 | known affected: 469 known not affected: 97 recommended: 1526 | 2026-10-03T16:54:24+00:00 | Vulnerability · Source |