VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
305256 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2019-16746 | suse_vex | SUSE CVE CVE-2019-16746 | known affected: 197 known not affected: 201 recommended: 850 | 2026-10-03T16:54:21+00:00 | Vulnerability · Source |
| CVE-2019-19062 | suse_vex | SUSE CVE CVE-2019-19062 | known affected: 469 known not affected: 69 recommended: 1499 | 2026-10-03T16:54:17+00:00 | Vulnerability · Source |
| CVE-2019-20810 | suse_vex | SUSE CVE CVE-2019-20810 | known affected: 441 known not affected: 27 recommended: 1506 | 2026-10-03T16:54:13+00:00 | Vulnerability · Source |
| CVE-2020-8428 | suse_vex | SUSE CVE CVE-2020-8428 | known affected: 390 known not affected: 243 recommended: 1253 | 2026-10-03T16:54:07+00:00 | Vulnerability · Source |
| CVE-2020-10720 | suse_vex | SUSE CVE CVE-2020-10720 | known affected: 97 known not affected: 97 recommended: 644 | 2026-10-03T16:54:03+00:00 | Vulnerability · Source |
| CVE-2020-12655 | suse_vex | SUSE CVE CVE-2020-12655 | known affected: 393 known not affected: 117 recommended: 1339 | 2026-10-03T16:53:59+00:00 | Vulnerability · Source |
| CVE-2020-12656 | suse_vex | SUSE CVE CVE-2020-12656 | known affected: 447 known not affected: 137 recommended: 1566 | 2026-10-03T16:53:55+00:00 | Vulnerability · Source |
| CVE-2020-12657 | suse_vex | SUSE CVE CVE-2020-12657 | known affected: 393 known not affected: 226 recommended: 1236 | 2026-10-03T16:53:52+00:00 | Vulnerability · Source |
| CVE-2020-12659 | suse_vex | SUSE CVE CVE-2020-12659 | known affected: 382 known not affected: 323 recommended: 1110 | 2026-10-03T16:53:50+00:00 | Vulnerability · Source |
| CVE-2020-15437 | suse_vex | SUSE CVE CVE-2020-15437 | known affected: 292 known not affected: 112 recommended: 1607 | 2026-10-03T16:53:45+00:00 | Vulnerability · Source |
| CVE-2020-24586 | suse_vex | SUSE CVE CVE-2020-24586 | known affected: 318 known not affected: 122 recommended: 1546 | 2026-10-03T16:53:41+00:00 | Vulnerability · Source |
| CVE-2020-25669 | suse_vex | SUSE CVE CVE-2020-25669 | known affected: 292 known not affected: 108 recommended: 1587 | 2026-10-03T16:53:37+00:00 | Vulnerability · Source |
| CVE-2020-25670 | suse_vex | SUSE CVE CVE-2020-25670 | known affected: 300 known not affected: 98 recommended: 1502 | 2026-10-03T16:53:35+00:00 | Vulnerability · Source |
| CVE-2020-26141 | suse_vex | SUSE CVE CVE-2020-26141 | known affected: 318 known not affected: 168 recommended: 1493 | 2026-10-03T16:53:32+00:00 | Vulnerability · Source |
| CVE-2020-26159 | suse_vex | SUSE CVE CVE-2020-26159 | known affected: 243 recommended: 272 | 2026-10-03T16:53:30+00:00 | Vulnerability · Source |
| CVE-2020-29661 | suse_vex | SUSE CVE CVE-2020-29661 | known affected: 473 known not affected: 10 recommended: 1869 | 2026-10-03T16:53:25+00:00 | Vulnerability · Source |
| CVE-2020-36312 | suse_vex | SUSE CVE CVE-2020-36312 | known affected: 300 known not affected: 133 recommended: 1464 | 2026-10-03T16:53:22+00:00 | Vulnerability · Source |