VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293915 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9617 | suse_vex | SUSE CVE CVE-2017-9617 | known affected: 86 recommended: 162 | 2026-07-26T23:45:05+00:00 | Vulnerability · Source |
| CVE-2017-10663 | suse_vex | SUSE CVE CVE-2017-10663 | known not affected: 28 | 2026-07-26T23:44:57+00:00 | Vulnerability · Source |
| CVE-2017-12654 | suse_vex | SUSE CVE CVE-2017-12654 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T23:44:52+00:00 | Vulnerability · Source |
| CVE-2017-13087 | suse_vex | SUSE CVE CVE-2017-13087 | known affected: 6 known not affected: 354 recommended: 120 | 2026-07-26T23:44:48+00:00 | Vulnerability · Source |
| CVE-2017-14333 | suse_vex | SUSE CVE CVE-2017-14333 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-26T23:44:42+00:00 | Vulnerability · Source |
| CVE-2017-15591 | suse_vex | SUSE CVE CVE-2017-15591 | known affected: 31 known not affected: 125 recommended: 86 | 2026-07-26T23:44:37+00:00 | Vulnerability · Source |
| CVE-2017-16353 | suse_vex | SUSE CVE CVE-2017-16353 | known affected: 94 recommended: 186 | 2026-07-26T23:44:35+00:00 | Vulnerability · Source |
| CVE-2017-17045 | suse_vex | SUSE CVE CVE-2017-17045 | known affected: 32 known not affected: 42 | 2026-07-26T23:44:33+00:00 | Vulnerability · Source |
| CVE-2017-18027 | suse_vex | SUSE CVE CVE-2017-18027 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T23:44:31+00:00 | Vulnerability · Source |
| CVE-2017-18219 | suse_vex | SUSE CVE CVE-2017-18219 | known not affected: 94 recommended: 50 | 2026-07-26T23:44:29+00:00 | Vulnerability · Source |
| CVE-2018-1656 | suse_vex | SUSE CVE CVE-2018-1656 | known affected: 503 recommended: 415 | 2026-07-26T23:44:21+00:00 | Vulnerability · Source |
| CVE-2018-2814 | suse_vex | SUSE CVE CVE-2018-2814 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-07-26T23:44:19+00:00 | Vulnerability · Source |
| CVE-2018-5093 | suse_vex | SUSE CVE CVE-2018-5093 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T23:44:14+00:00 | Vulnerability · Source |
| CVE-2018-5734 | suse_vex | SUSE CVE CVE-2018-5734 | known not affected: 95 | 2026-07-26T23:44:10+00:00 | Vulnerability · Source |
| CVE-2018-5873 | suse_vex | SUSE CVE CVE-2018-5873 | known not affected: 152 | 2026-07-26T23:44:07+00:00 | Vulnerability · Source |
| CVE-2018-7273 | suse_vex | SUSE CVE CVE-2018-7273 | known not affected: 49 | 2026-07-26T23:44:04+00:00 | Vulnerability · Source |
| CVE-2018-9138 | suse_vex | SUSE CVE CVE-2018-9138 | known not affected: 297 | 2026-07-26T23:43:58+00:00 | Vulnerability · Source |
| CVE-2018-9517 | suse_vex | SUSE CVE CVE-2018-9517 | known affected: 388 known not affected: 365 recommended: 382 | 2026-07-26T23:43:53+00:00 | Vulnerability · Source |
| CVE-2018-12233 | suse_vex | SUSE CVE CVE-2018-12233 | known affected: 30 known not affected: 345 recommended: 505 | 2026-07-26T23:43:49+00:00 | Vulnerability · Source |
| CVE-2018-12928 | suse_vex | SUSE CVE CVE-2018-12928 | known not affected: 563 | 2026-07-26T23:43:45+00:00 | Vulnerability · Source |
| CVE-2018-13095 | suse_vex | SUSE CVE CVE-2018-13095 | known affected: 48 known not affected: 204 recommended: 577 | 2026-07-26T23:43:43+00:00 | Vulnerability · Source |
| CVE-2019-2968 | suse_vex | SUSE CVE CVE-2019-2968 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-26T23:43:20+00:00 | Vulnerability · Source |
| CVE-2019-5736 | suse_vex | SUSE CVE CVE-2019-5736 | known affected: 347 known not affected: 179 recommended: 1109 | 2026-07-26T23:43:13+00:00 | Vulnerability · Source |
| CVE-2019-8597 | suse_vex | SUSE CVE CVE-2019-8597 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-26T23:43:10+00:00 | Vulnerability · Source |
| CVE-2019-9162 | suse_vex | SUSE CVE CVE-2019-9162 | known not affected: 495 | 2026-07-26T23:43:08+00:00 | Vulnerability · Source |
| CVE-2019-9444 | suse_vex | SUSE CVE CVE-2019-9444 | known not affected: 52 | 2026-07-26T23:43:06+00:00 | Vulnerability · Source |
| CVE-2019-9446 | suse_vex | SUSE CVE CVE-2019-9446 | known not affected: 215 | 2026-07-26T23:43:05+00:00 | Vulnerability · Source |
| CVE-2019-12083 | suse_vex | SUSE CVE CVE-2019-12083 | known not affected: 44 recommended: 520 | 2026-07-26T23:42:54+00:00 | Vulnerability · Source |
| CVE-2019-12454 | suse_vex | SUSE CVE CVE-2019-12454 | known not affected: 332 | 2026-07-26T23:42:50+00:00 | Vulnerability · Source |
| CVE-2019-13112 | suse_vex | SUSE CVE CVE-2019-13112 | known affected: 7 known not affected: 83 recommended: 27 | 2026-07-26T23:42:47+00:00 | Vulnerability · Source |
| CVE-2019-17013 | suse_vex | SUSE CVE CVE-2019-17013 | known not affected: 108 recommended: 9 | 2026-07-26T23:42:32+00:00 | Vulnerability · Source |
| CVE-2019-17567 | suse_vex | SUSE CVE CVE-2019-17567 | known affected: 18 known not affected: 218 | 2026-07-26T23:42:30+00:00 | Vulnerability · Source |
| CVE-2019-18424 | suse_vex | SUSE CVE CVE-2019-18424 | known not affected: 169 recommended: 257 | 2026-07-26T23:42:29+00:00 | Vulnerability · Source |
| CVE-2019-18807 | suse_vex | SUSE CVE CVE-2019-18807 | known not affected: 223 | 2026-07-26T23:42:27+00:00 | Vulnerability · Source |
| CVE-2019-19060 | suse_vex | SUSE CVE CVE-2019-19060 | known affected: 428 known not affected: 215 recommended: 1334 | 2026-07-26T23:42:22+00:00 | Vulnerability · Source |
| CVE-2019-19076 | suse_vex | SUSE CVE CVE-2019-19076 | known not affected: 365 | 2026-07-26T23:42:21+00:00 | Vulnerability · Source |
| CVE-2019-19083 | suse_vex | SUSE CVE CVE-2019-19083 | known affected: 371 known not affected: 299 recommended: 1322 | 2026-07-26T23:42:19+00:00 | Vulnerability · Source |
| CVE-2019-19922 | suse_vex | SUSE CVE CVE-2019-19922 | known affected: 320 known not affected: 320 recommended: 801 | 2026-07-26T23:42:12+00:00 | Vulnerability · Source |
| CVE-2020-12108 | suse_vex | SUSE CVE CVE-2020-12108 | known affected: 9 recommended: 32 | 2026-07-26T23:41:44+00:00 | Vulnerability · Source |
| CVE-2020-14314 | suse_vex | SUSE CVE CVE-2020-14314 | known affected: 423 known not affected: 144 recommended: 1552 | 2026-07-26T23:41:39+00:00 | Vulnerability · Source |
| CVE-2020-16290 | suse_vex | SUSE CVE CVE-2020-16290 | known not affected: 172 recommended: 8 | 2026-07-26T23:41:32+00:00 | Vulnerability · Source |
| CVE-2020-25221 | suse_vex | SUSE CVE CVE-2020-25221 | known not affected: 413 | 2026-07-26T23:41:26+00:00 | Vulnerability · Source |
| CVE-2020-29482 | suse_vex | SUSE CVE CVE-2020-29482 | known not affected: 334 | 2026-07-26T23:41:18+00:00 | Vulnerability · Source |
| CVE-2021-29464 | suse_vex | SUSE CVE CVE-2021-29464 | known not affected: 143 recommended: 4 | 2026-07-26T23:40:52+00:00 | Vulnerability · Source |
| CVE-2021-29649 | suse_vex | SUSE CVE CVE-2021-29649 | known not affected: 355 | 2026-07-26T23:40:51+00:00 | Vulnerability · Source |
| CVE-2021-37322 | suse_vex | SUSE CVE CVE-2021-37322 | known not affected: 257 | 2026-07-26T23:40:42+00:00 | Vulnerability · Source |
| CVE-2021-46968 | suse_vex | SUSE CVE CVE-2021-46968 | known affected: 388 known not affected: 248 recommended: 106 | 2026-07-26T23:40:36+00:00 | Vulnerability · Source |
| CVE-2021-46997 | suse_vex | SUSE CVE CVE-2021-46997 | known not affected: 292 | 2026-07-26T23:40:34+00:00 | Vulnerability · Source |
| CVE-2021-47164 | suse_vex | SUSE CVE CVE-2021-47164 | known affected: 388 known not affected: 256 recommended: 91 | 2026-07-26T23:40:29+00:00 | Vulnerability · Source |
| CVE-2022-20118 | suse_vex | SUSE CVE CVE-2022-20118 | known not affected: 390 | 2026-07-26T23:39:43+00:00 | Vulnerability · Source |