VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-13050 | suse_vex | SUSE CVE CVE-2017-13050 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T16:58:50+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-14033 | suse_vex | SUSE CVE CVE-2017-14033 | known affected: 1 known not affected: 55 recommended: 98 | 2026-07-26T16:58:46+00:00 | Vulnerability · Source |
| CVE-2017-14129 | suse_vex | SUSE CVE CVE-2017-14129 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-26T16:58:45+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-14318 | suse_vex | SUSE CVE CVE-2017-14318 | known affected: 31 known not affected: 125 recommended: 111 | 2026-07-26T16:58:42+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-15041 | suse_vex | SUSE CVE CVE-2017-15041 | known not affected: 160 recommended: 61 | 2026-07-26T16:58:34+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-18269 | suse_vex | SUSE CVE CVE-2017-18269 | known affected: 438 known not affected: 145 recommended: 1255 | 2026-07-26T16:58:21+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-2603 | suse_vex | SUSE CVE CVE-2018-2603 | known affected: 467 known not affected: 263 recommended: 730 | 2026-07-26T16:58:14+00:00 | Vulnerability · Source |
| CVE-2018-2777 | suse_vex | SUSE CVE CVE-2018-2777 | known affected: 1 known not affected: 192 recommended: 431 | 2026-07-26T16:58:12+00:00 | Vulnerability · Source |
| CVE-2018-2941 | suse_vex | SUSE CVE CVE-2018-2941 | known not affected: 62 | 2026-07-26T16:58:10+00:00 | Vulnerability · Source |
| CVE-2018-2964 | suse_vex | SUSE CVE CVE-2018-2964 | known not affected: 215 recommended: 286 | 2026-07-26T16:58:09+00:00 | Vulnerability · Source |
| CVE-2018-4300 | suse_vex | SUSE CVE CVE-2018-4300 | known not affected: 400 | 2026-07-26T16:58:06+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-5345 | suse_vex | SUSE CVE CVE-2018-5345 | known not affected: 96 recommended: 306 | 2026-07-26T16:57:58+00:00 | Vulnerability · Source |
| CVE-2018-5685 | suse_vex | SUSE CVE CVE-2018-5685 | known affected: 94 recommended: 186 | 2026-07-26T16:57:56+00:00 | Vulnerability · Source |
| CVE-2018-6073 | suse_vex | SUSE CVE CVE-2018-6073 | recommended: 10 | 2026-07-26T16:57:53+00:00 | Vulnerability · Source |
| CVE-2018-7225 | suse_vex | SUSE CVE CVE-2018-7225 | known affected: 45 known not affected: 32 recommended: 93 | 2026-07-26T16:57:49+00:00 | Vulnerability · Source |
| CVE-2018-7418 | suse_vex | SUSE CVE CVE-2018-7418 | known affected: 1 known not affected: 115 recommended: 592 | 2026-07-26T16:57:46+00:00 | Vulnerability · Source |
| CVE-2018-8101 | suse_vex | SUSE CVE CVE-2018-8101 | known not affected: 381 | 2026-07-26T16:57:44+00:00 | Vulnerability · Source |
| CVE-2018-10195 | suse_vex | SUSE CVE CVE-2018-10195 | known affected: 17 known not affected: 24 recommended: 70 | 2026-07-26T16:57:40+00:00 | Vulnerability · Source |
| CVE-2018-10861 | suse_vex | SUSE CVE CVE-2018-10861 | known not affected: 137 recommended: 1273 | 2026-07-26T16:57:37+00:00 | Vulnerability · Source |
| CVE-2018-10881 | suse_vex | SUSE CVE CVE-2018-10881 | known affected: 48 known not affected: 257 recommended: 442 | 2026-07-26T16:57:36+00:00 | Vulnerability · Source |
| CVE-2018-11357 | suse_vex | SUSE CVE CVE-2018-11357 | known affected: 87 recommended: 1022 | 2026-07-26T16:57:31+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-14646 | suse_vex | SUSE CVE CVE-2018-14646 | known not affected: 137 recommended: 13 | 2026-07-26T16:57:24+00:00 | Vulnerability · Source |
| CVE-2018-14662 | suse_vex | SUSE CVE CVE-2018-14662 | known not affected: 49 recommended: 327 | 2026-07-26T16:57:23+00:00 | Vulnerability · Source |
| CVE-2018-15688 | suse_vex | SUSE CVE CVE-2018-15688 | known affected: 320 known not affected: 69 recommended: 1509 | 2026-07-26T16:57:19+00:00 | Vulnerability · Source |
| CVE-2018-15854 | suse_vex | SUSE CVE CVE-2018-15854 | known affected: 565 known not affected: 65 recommended: 391 | 2026-07-26T16:57:18+00:00 | Vulnerability · Source |
| CVE-2018-15910 | suse_vex | SUSE CVE CVE-2018-15910 | known affected: 16 recommended: 424 | 2026-07-26T16:57:16+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-17456 | suse_vex | SUSE CVE CVE-2018-17456 | known affected: 119 known not affected: 2 recommended: 1076 | 2026-07-26T16:57:11+00:00 | Vulnerability · Source |
| CVE-2018-17540 | suse_vex | SUSE CVE CVE-2018-17540 | known affected: 26 known not affected: 135 recommended: 448 | 2026-07-26T16:57:10+00:00 | Vulnerability · Source |
| CVE-2018-17972 | suse_vex | SUSE CVE CVE-2018-17972 | known affected: 44 known not affected: 229 recommended: 287 | 2026-07-26T16:57:06+00:00 | Vulnerability · Source |
| CVE-2018-18020 | suse_vex | SUSE CVE CVE-2018-18020 | known affected: 19 known not affected: 190 | 2026-07-26T16:57:05+00:00 | Vulnerability · Source |
| CVE-2018-18457 | suse_vex | SUSE CVE CVE-2018-18457 | known not affected: 381 | 2026-07-26T16:57:03+00:00 | Vulnerability · Source |
| CVE-2018-18585 | suse_vex | SUSE CVE CVE-2018-18585 | known affected: 48 recommended: 157 | 2026-07-26T16:57:01+00:00 | Vulnerability · Source |