VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294132 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-10169 | suse_vex | SUSE CVE CVE-2016-10169 | known affected: 30 recommended: 57 | 2026-07-26T17:00:13+00:00 | Vulnerability · Source |
| CVE-2017-5563 | suse_vex | SUSE CVE CVE-2017-5563 | known not affected: 47 | 2026-07-26T16:59:54+00:00 | Vulnerability · Source |
| CVE-2017-6210 | suse_vex | SUSE CVE CVE-2017-6210 | recommended: 29 | 2026-07-26T16:59:48+00:00 | Vulnerability · Source |
| CVE-2017-7511 | suse_vex | SUSE CVE CVE-2017-7511 | known affected: 60 known not affected: 39 recommended: 583 | 2026-07-26T16:59:35+00:00 | Vulnerability · Source |
| CVE-2017-7547 | suse_vex | SUSE CVE CVE-2017-7547 | known not affected: 45 recommended: 264 | 2026-07-26T16:59:33+00:00 | Vulnerability · Source |
| CVE-2017-7718 | suse_vex | SUSE CVE CVE-2017-7718 | known affected: 26 known not affected: 280 recommended: 268 | 2026-07-26T16:59:30+00:00 | Vulnerability · Source |
| CVE-2017-8069 | suse_vex | SUSE CVE CVE-2017-8069 | known not affected: 34 | 2026-07-26T16:59:23+00:00 | Vulnerability · Source |
| CVE-2017-9408 | suse_vex | SUSE CVE CVE-2017-9408 | known affected: 60 known not affected: 39 recommended: 151 | 2026-07-26T16:59:13+00:00 | Vulnerability · Source |
| CVE-2017-10911 | suse_vex | SUSE CVE CVE-2017-10911 | known affected: 28 known not affected: 1412 recommended: 292 | 2026-07-26T16:59:10+00:00 | Vulnerability · Source |
| CVE-2017-10928 | suse_vex | SUSE CVE CVE-2017-10928 | known affected: 7 known not affected: 14 recommended: 136 | 2026-07-26T16:59:09+00:00 | Vulnerability · Source |
| CVE-2017-11531 | suse_vex | SUSE CVE CVE-2017-11531 | known affected: 94 known not affected: 70 recommended: 136 | 2026-07-26T16:59:05+00:00 | Vulnerability · Source |
| CVE-2017-11643 | suse_vex | SUSE CVE CVE-2017-11643 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T16:59:03+00:00 | Vulnerability · Source |
| CVE-2017-11752 | suse_vex | SUSE CVE CVE-2017-11752 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T16:59:02+00:00 | Vulnerability · Source |
| CVE-2017-12380 | suse_vex | SUSE CVE CVE-2017-12380 | known affected: 1 known not affected: 78 recommended: 280 | 2026-07-26T16:58:57+00:00 | Vulnerability · Source |
| CVE-2017-12427 | suse_vex | SUSE CVE CVE-2017-12427 | known affected: 95 recommended: 186 | 2026-07-26T16:58:56+00:00 | Vulnerability · Source |
| CVE-2017-12641 | suse_vex | SUSE CVE CVE-2017-12641 | known affected: 94 recommended: 186 | 2026-07-26T16:58:54+00:00 | Vulnerability · Source |
| CVE-2017-12935 | suse_vex | SUSE CVE CVE-2017-12935 | known affected: 94 known not affected: 91 recommended: 186 | 2026-07-26T16:58:52+00:00 | Vulnerability · Source |
| CVE-2017-13061 | suse_vex | SUSE CVE CVE-2017-13061 | known affected: 95 recommended: 186 | 2026-07-26T16:58:48+00:00 | Vulnerability · Source |
| CVE-2017-14164 | suse_vex | SUSE CVE CVE-2017-14164 | known not affected: 65 recommended: 200 | 2026-07-26T16:58:43+00:00 | Vulnerability · Source |
| CVE-2017-14520 | suse_vex | SUSE CVE CVE-2017-14520 | known affected: 60 known not affected: 39 recommended: 111 | 2026-07-26T16:58:40+00:00 | Vulnerability · Source |
| CVE-2017-14684 | suse_vex | SUSE CVE CVE-2017-14684 | known affected: 10 known not affected: 144 | 2026-07-26T16:58:37+00:00 | Vulnerability · Source |
| CVE-2017-16879 | suse_vex | SUSE CVE CVE-2017-16879 | known not affected: 667 recommended: 50 | 2026-07-26T16:58:31+00:00 | Vulnerability · Source |
| CVE-2017-17857 | suse_vex | SUSE CVE CVE-2017-17857 | known not affected: 182 recommended: 299 | 2026-07-26T16:58:27+00:00 | Vulnerability · Source |
| CVE-2017-18043 | suse_vex | SUSE CVE CVE-2017-18043 | known affected: 69 known not affected: 11 recommended: 218 | 2026-07-26T16:58:26+00:00 | Vulnerability · Source |
| CVE-2017-18251 | suse_vex | SUSE CVE CVE-2017-18251 | known affected: 98 recommended: 184 | 2026-07-26T16:58:23+00:00 | Vulnerability · Source |
| CVE-2017-20230 | suse_vex | SUSE CVE CVE-2017-20230 | known affected: 402 known not affected: 138 recommended: 16 | 2026-07-26T16:58:19+00:00 | Vulnerability · Source |
| CVE-2018-1283 | suse_vex | SUSE CVE CVE-2018-1283 | known affected: 92 known not affected: 39 recommended: 127 | 2026-07-26T16:58:16+00:00 | Vulnerability · Source |
| CVE-2018-5092 | suse_vex | SUSE CVE CVE-2018-5092 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T16:58:01+00:00 | Vulnerability · Source |
| CVE-2018-5118 | suse_vex | SUSE CVE CVE-2018-5118 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T16:57:59+00:00 | Vulnerability · Source |
| CVE-2018-12699 | suse_vex | SUSE CVE CVE-2018-12699 | known not affected: 229 recommended: 2 | 2026-07-26T16:57:28+00:00 | Vulnerability · Source |
| CVE-2018-17189 | suse_vex | SUSE CVE CVE-2018-17189 | known affected: 111 known not affected: 53 recommended: 164 | 2026-07-26T16:57:13+00:00 | Vulnerability · Source |
| CVE-2018-1000205 | suse_vex | SUSE CVE CVE-2018-1000205 | known not affected: 14 | 2026-07-26T16:56:42+00:00 | Vulnerability · Source |
| CVE-2019-5544 | suse_vex | SUSE CVE CVE-2019-5544 | known not affected: 158 recommended: 12 | 2026-07-26T16:56:31+00:00 | Vulnerability · Source |
| CVE-2019-8584 | suse_vex | SUSE CVE CVE-2019-8584 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-26T16:56:20+00:00 | Vulnerability · Source |
| CVE-2019-8586 | suse_vex | SUSE CVE CVE-2019-8586 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-26T16:56:18+00:00 | Vulnerability · Source |
| CVE-2019-9193 | suse_vex | SUSE CVE CVE-2019-9193 | known affected: 2 known not affected: 54 | 2026-07-26T16:56:12+00:00 | Vulnerability · Source |
| CVE-2019-9806 | suse_vex | SUSE CVE CVE-2019-9806 | known affected: 20 known not affected: 76 recommended: 9 | 2026-07-26T16:56:07+00:00 | Vulnerability · Source |
| CVE-2019-12524 | suse_vex | SUSE CVE CVE-2019-12524 | known not affected: 20 recommended: 27 | 2026-07-26T16:55:53+00:00 | Vulnerability · Source |
| CVE-2019-13113 | suse_vex | SUSE CVE CVE-2019-13113 | known affected: 2 known not affected: 110 recommended: 24 | 2026-07-26T16:55:48+00:00 | Vulnerability · Source |
| CVE-2019-13233 | suse_vex | SUSE CVE CVE-2019-13233 | known not affected: 341 recommended: 456 | 2026-07-26T16:55:46+00:00 | Vulnerability · Source |
| CVE-2019-13454 | suse_vex | SUSE CVE CVE-2019-13454 | known affected: 142 recommended: 712 | 2026-07-26T16:55:43+00:00 | Vulnerability · Source |
| CVE-2019-14196 | suse_vex | SUSE CVE CVE-2019-14196 | known affected: 19 recommended: 46 | 2026-07-26T16:55:40+00:00 | Vulnerability · Source |
| CVE-2019-14607 | suse_vex | SUSE CVE CVE-2019-14607 | known not affected: 28 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-14444 | suse_vex | SUSE CVE CVE-2019-14444 | known affected: 428 recommended: 553 | 2026-07-26T16:55:34+00:00 | Vulnerability · Source |
| CVE-2019-15791 | suse_vex | SUSE CVE CVE-2019-15791 | known not affected: 208 | 2026-07-26T16:55:31+00:00 | Vulnerability · Source |
| CVE-2019-17040 | suse_vex | SUSE CVE CVE-2019-17040 | known affected: 22 known not affected: 241 | 2026-07-26T16:55:27+00:00 | Vulnerability · Source |
| CVE-2019-17347 | suse_vex | SUSE CVE CVE-2019-17347 | known affected: 18 known not affected: 166 recommended: 207 | 2026-07-26T16:55:26+00:00 | Vulnerability · Source |
| CVE-2019-17582 | suse_vex | SUSE CVE CVE-2019-17582 | known not affected: 131 | 2026-07-26T16:55:23+00:00 | Vulnerability · Source |
| CVE-2019-19242 | suse_vex | SUSE CVE CVE-2019-19242 | known not affected: 358 | 2026-07-26T16:55:19+00:00 | Vulnerability · Source |
| CVE-2019-19815 | suse_vex | SUSE CVE CVE-2019-19815 | known not affected: 257 | 2026-07-26T16:55:17+00:00 | Vulnerability · Source |