VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283041 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-17521 | suse_vex | SUSE CVE CVE-2017-17521 | known not affected: 33 recommended: 20 | 2026-07-19T18:30:56+00:00 | Vulnerability · Source |
| CVE-2017-18248 | suse_vex | SUSE CVE CVE-2017-18248 | known affected: 360 known not affected: 259 recommended: 808 | 2026-07-19T18:30:54+00:00 | Vulnerability · Source |
| CVE-2017-18269 | suse_vex | SUSE CVE CVE-2017-18269 | known affected: 426 known not affected: 122 recommended: 1219 | 2026-07-19T18:30:52+00:00 | Vulnerability · Source |
| CVE-2017-18922 | suse_vex | SUSE CVE CVE-2017-18922 | known affected: 22 known not affected: 3 recommended: 113 | 2026-07-19T18:30:51+00:00 | Vulnerability · Source |
| CVE-2017-1000100 | suse_vex | SUSE CVE CVE-2017-1000100 | known affected: 333 known not affected: 61 recommended: 449 | 2026-07-19T18:30:49+00:00 | Vulnerability · Source |
| CVE-2017-1000116 | suse_vex | SUSE CVE CVE-2017-1000116 | known not affected: 24 recommended: 58 | 2026-07-19T18:30:48+00:00 | Vulnerability · Source |
| CVE-2017-1000121 | suse_vex | SUSE CVE CVE-2017-1000121 | known affected: 4 known not affected: 212 recommended: 825 | 2026-07-19T18:30:47+00:00 | Vulnerability · Source |
| CVE-2017-1000128 | suse_vex | SUSE CVE CVE-2017-1000128 | known affected: 2 known not affected: 88 recommended: 114 | 2026-07-19T18:30:46+00:00 | Vulnerability · Source |
| CVE-2017-1000366 | suse_vex | SUSE CVE CVE-2017-1000366 | known affected: 370 known not affected: 230 recommended: 1322 | 2026-07-19T18:30:44+00:00 | Vulnerability · Source |
| CVE-2017-1000382 | suse_vex | SUSE CVE CVE-2017-1000382 | known affected: 323 known not affected: 224 recommended: 371 | 2026-07-19T18:30:43+00:00 | Vulnerability · Source |
| CVE-2017-1000408 | suse_vex | SUSE CVE CVE-2017-1000408 | known affected: 369 known not affected: 266 recommended: 1158 | 2026-07-19T18:30:41+00:00 | Vulnerability · Source |
| CVE-2018-0361 | suse_vex | SUSE CVE CVE-2018-0361 | known affected: 1 recommended: 292 | 2026-07-19T18:30:40+00:00 | Vulnerability · Source |
| CVE-2018-0494 | suse_vex | SUSE CVE CVE-2018-0494 | known affected: 334 known not affected: 24 recommended: 160 | 2026-07-19T18:30:39+00:00 | Vulnerability · Source |
| CVE-2018-0500 | suse_vex | SUSE CVE CVE-2018-0500 | known affected: 320 known not affected: 104 recommended: 371 | 2026-07-19T18:30:37+00:00 | Vulnerability · Source |
| CVE-2018-0739 | suse_vex | SUSE CVE CVE-2018-0739 | known affected: 349 known not affected: 427 recommended: 914 | 2026-07-19T18:30:36+00:00 | Vulnerability · Source |
| CVE-2018-0886 | suse_vex | SUSE CVE CVE-2018-0886 | recommended: 221 | 2026-07-19T18:30:35+00:00 | Vulnerability · Source |
| CVE-2018-1106 | suse_vex | SUSE CVE CVE-2018-1106 | known affected: 5 known not affected: 57 recommended: 549 | 2026-07-19T18:30:33+00:00 | Vulnerability · Source |
| CVE-2018-1139 | suse_vex | SUSE CVE CVE-2018-1139 | known affected: 320 known not affected: 854 recommended: 3087 | 2026-07-19T18:30:31+00:00 | Vulnerability · Source |
| CVE-2018-2665 | suse_vex | SUSE CVE CVE-2018-2665 | known affected: 1 known not affected: 123 recommended: 597 | 2026-07-19T18:30:29+00:00 | Vulnerability · Source |
| CVE-2018-2759 | suse_vex | SUSE CVE CVE-2018-2759 | known affected: 1 known not affected: 173 recommended: 414 | 2026-07-19T18:30:28+00:00 | Vulnerability · Source |
| CVE-2018-2813 | suse_vex | SUSE CVE CVE-2018-2813 | known affected: 1 known not affected: 173 recommended: 606 | 2026-07-19T18:30:27+00:00 | Vulnerability · Source |
| CVE-2018-3058 | suse_vex | SUSE CVE CVE-2018-3058 | known affected: 60 known not affected: 32 recommended: 594 | 2026-07-19T18:30:25+00:00 | Vulnerability · Source |
| CVE-2018-3156 | suse_vex | SUSE CVE CVE-2018-3156 | known affected: 91 known not affected: 46 recommended: 562 | 2026-07-19T18:30:24+00:00 | Vulnerability · Source |
| CVE-2018-3173 | suse_vex | SUSE CVE CVE-2018-3173 | known affected: 84 known not affected: 46 recommended: 430 | 2026-07-19T18:30:23+00:00 | Vulnerability · Source |
| CVE-2018-3174 | suse_vex | SUSE CVE CVE-2018-3174 | known affected: 93 known not affected: 27 recommended: 601 | 2026-07-19T18:30:21+00:00 | Vulnerability · Source |
| CVE-2018-3200 | suse_vex | SUSE CVE CVE-2018-3200 | known affected: 84 known not affected: 46 recommended: 440 | 2026-07-19T18:30:20+00:00 | Vulnerability · Source |
| CVE-2018-3630 | suse_vex | SUSE CVE CVE-2018-3630 | known affected: 43 recommended: 231 | 2026-07-19T18:30:19+00:00 | Vulnerability · Source |
| CVE-2018-4096 | suse_vex | SUSE CVE CVE-2018-4096 | known affected: 135 known not affected: 87 recommended: 893 | 2026-07-19T18:30:17+00:00 | Vulnerability · Source |
| CVE-2018-4101 | suse_vex | SUSE CVE CVE-2018-4101 | known affected: 92 known not affected: 169 recommended: 905 | 2026-07-19T18:30:16+00:00 | Vulnerability · Source |
| CVE-2018-4127 | suse_vex | SUSE CVE CVE-2018-4127 | known affected: 92 known not affected: 169 recommended: 905 | 2026-07-19T18:30:14+00:00 | Vulnerability · Source |
| CVE-2018-4191 | suse_vex | SUSE CVE CVE-2018-4191 | known affected: 84 known not affected: 82 recommended: 956 | 2026-07-19T18:30:12+00:00 | Vulnerability · Source |
| CVE-2018-4197 | suse_vex | SUSE CVE CVE-2018-4197 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:30:11+00:00 | Vulnerability · Source |
| CVE-2018-4204 | suse_vex | SUSE CVE CVE-2018-4204 | known affected: 93 known not affected: 63 recommended: 1283 | 2026-07-19T18:30:09+00:00 | Vulnerability · Source |
| CVE-2018-4209 | suse_vex | SUSE CVE CVE-2018-4209 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:30:08+00:00 | Vulnerability · Source |
| CVE-2018-4210 | suse_vex | SUSE CVE CVE-2018-4210 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:30:07+00:00 | Vulnerability · Source |
| CVE-2018-4218 | suse_vex | SUSE CVE CVE-2018-4218 | known affected: 138 known not affected: 82 recommended: 902 | 2026-07-19T18:30:06+00:00 | Vulnerability · Source |
| CVE-2018-4262 | suse_vex | SUSE CVE CVE-2018-4262 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:04+00:00 | Vulnerability · Source |
| CVE-2018-4266 | suse_vex | SUSE CVE CVE-2018-4266 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:03+00:00 | Vulnerability · Source |
| CVE-2018-4278 | suse_vex | SUSE CVE CVE-2018-4278 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:01+00:00 | Vulnerability · Source |
| CVE-2018-4306 | suse_vex | SUSE CVE CVE-2018-4306 | known affected: 84 known not affected: 82 recommended: 956 | 2026-07-19T18:30:00+00:00 | Vulnerability · Source |
| CVE-2018-4312 | suse_vex | SUSE CVE CVE-2018-4312 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:29:59+00:00 | Vulnerability · Source |
| CVE-2018-4316 | suse_vex | SUSE CVE CVE-2018-4316 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:29:57+00:00 | Vulnerability · Source |
| CVE-2018-4319 | suse_vex | SUSE CVE CVE-2018-4319 | known affected: 84 known not affected: 82 recommended: 956 | 2026-07-19T18:29:56+00:00 | Vulnerability · Source |
| CVE-2018-4358 | suse_vex | SUSE CVE CVE-2018-4358 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:29:55+00:00 | Vulnerability · Source |
| CVE-2018-4359 | suse_vex | SUSE CVE CVE-2018-4359 | known affected: 84 known not affected: 82 recommended: 956 | 2026-07-19T18:29:53+00:00 | Vulnerability · Source |
| CVE-2018-4361 | suse_vex | SUSE CVE CVE-2018-4361 | known affected: 84 known not affected: 82 recommended: 944 | 2026-07-19T18:29:52+00:00 | Vulnerability · Source |
| CVE-2018-4376 | suse_vex | SUSE CVE CVE-2018-4376 | known affected: 84 recommended: 944 | 2026-07-19T18:29:51+00:00 | Vulnerability · Source |
| CVE-2018-4386 | suse_vex | SUSE CVE CVE-2018-4386 | known affected: 84 recommended: 944 | 2026-07-19T18:29:49+00:00 | Vulnerability · Source |
| CVE-2018-4442 | suse_vex | SUSE CVE CVE-2018-4442 | known affected: 84 recommended: 965 | 2026-07-19T18:29:48+00:00 | Vulnerability · Source |
| CVE-2018-5091 | suse_vex | SUSE CVE CVE-2018-5091 | known affected: 2 recommended: 317 | 2026-07-19T18:29:47+00:00 | Vulnerability · Source |