VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294016 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-18211 | suse_vex | SUSE CVE CVE-2017-18211 | known affected: 94 known not affected: 50 recommended: 136 | 2026-07-26T00:27:58+00:00 | Vulnerability · Source |
| CVE-2017-18218 | suse_vex | SUSE CVE CVE-2017-18218 | known not affected: 212 | 2026-07-26T00:27:57+00:00 | Vulnerability · Source |
| CVE-2017-18234 | suse_vex | SUSE CVE CVE-2017-18234 | known affected: 5 recommended: 34 | 2026-07-26T00:27:49+00:00 | Vulnerability · Source |
| CVE-2017-18236 | suse_vex | SUSE CVE CVE-2017-18236 | known affected: 4 known not affected: 14 recommended: 26 | 2026-07-26T00:27:47+00:00 | Vulnerability · Source |
| CVE-2017-18250 | suse_vex | SUSE CVE CVE-2017-18250 | known affected: 97 known not affected: 50 recommended: 100 | 2026-07-26T00:27:40+00:00 | Vulnerability · Source |
| CVE-2017-18253 | suse_vex | SUSE CVE CVE-2017-18253 | known affected: 10 known not affected: 190 | 2026-07-26T00:27:38+00:00 | Vulnerability · Source |
| CVE-2017-18261 | suse_vex | SUSE CVE CVE-2017-18261 | known not affected: 291 | 2026-07-26T00:27:32+00:00 | Vulnerability · Source |
| CVE-2017-18360 | suse_vex | SUSE CVE CVE-2017-18360 | known not affected: 355 recommended: 74 | 2026-07-26T00:27:22+00:00 | Vulnerability · Source |
| CVE-2017-18550 | suse_vex | SUSE CVE CVE-2017-18550 | known not affected: 210 | 2026-07-26T00:27:20+00:00 | Vulnerability · Source |
| CVE-2017-1000199 | suse_vex | SUSE CVE CVE-2017-1000199 | known affected: 2 recommended: 8 | 2026-07-26T00:27:06+00:00 | Vulnerability · Source |
| CVE-2017-1000201 | suse_vex | SUSE CVE CVE-2017-1000201 | known not affected: 9 | 2026-07-26T00:27:04+00:00 | Vulnerability · Source |
| CVE-2017-1000252 | suse_vex | SUSE CVE CVE-2017-1000252 | known affected: 3 known not affected: 149 recommended: 419 | 2026-07-26T00:27:00+00:00 | Vulnerability · Source |
| CVE-2017-1000376 | suse_vex | SUSE CVE CVE-2017-1000376 | known not affected: 65 recommended: 89 | 2026-07-26T00:26:48+00:00 | Vulnerability · Source |
| CVE-2017-1000422 | suse_vex | SUSE CVE CVE-2017-1000422 | recommended: 75 | 2026-07-26T00:26:37+00:00 | Vulnerability · Source |
| CVE-2017-1000445 | suse_vex | SUSE CVE CVE-2017-1000445 | known affected: 94 known not affected: 1 recommended: 172 | 2026-07-26T00:26:35+00:00 | Vulnerability · Source |
| CVE-2017-1000476 | suse_vex | SUSE CVE CVE-2017-1000476 | known affected: 94 recommended: 206 | 2026-07-26T00:26:33+00:00 | Vulnerability · Source |
| CVE-2018-0494 | suse_vex | SUSE CVE CVE-2018-0494 | known affected: 336 known not affected: 24 recommended: 162 | 2026-07-26T00:26:28+00:00 | Vulnerability · Source |
| CVE-2018-0733 | suse_vex | SUSE CVE CVE-2018-0733 | known not affected: 68 | 2026-07-26T00:26:21+00:00 | Vulnerability · Source |
| CVE-2018-1058 | suse_vex | SUSE CVE CVE-2018-1058 | known affected: 56 known not affected: 185 recommended: 437 | 2026-07-26T00:26:13+00:00 | Vulnerability · Source |
| CVE-2018-1083 | suse_vex | SUSE CVE CVE-2018-1083 | known affected: 412 known not affected: 45 recommended: 81 | 2026-07-26T00:26:05+00:00 | Vulnerability · Source |
| CVE-2018-1094 | suse_vex | SUSE CVE CVE-2018-1094 | known affected: 7 known not affected: 232 recommended: 493 | 2026-07-26T00:26:01+00:00 | Vulnerability · Source |
| CVE-2018-1095 | suse_vex | SUSE CVE CVE-2018-1095 | known not affected: 393 | 2026-07-26T00:25:59+00:00 | Vulnerability · Source |
| CVE-2018-1106 | suse_vex | SUSE CVE CVE-2018-1106 | known affected: 10 known not affected: 57 recommended: 554 | 2026-07-26T00:25:57+00:00 | Vulnerability · Source |
| CVE-2018-1115 | suse_vex | SUSE CVE CVE-2018-1115 | known affected: 54 known not affected: 255 recommended: 395 | 2026-07-26T00:25:55+00:00 | Vulnerability · Source |
| CVE-2018-1304 | suse_vex | SUSE CVE CVE-2018-1304 | known affected: 46 known not affected: 1 recommended: 177 | 2026-07-26T00:25:42+00:00 | Vulnerability · Source |
| CVE-2018-1312 | suse_vex | SUSE CVE CVE-2018-1312 | known affected: 92 recommended: 168 | 2026-07-26T00:25:39+00:00 | Vulnerability · Source |
| CVE-2018-2678 | suse_vex | SUSE CVE CVE-2018-2678 | known affected: 73 known not affected: 263 recommended: 730 | 2026-07-26T00:25:08+00:00 | Vulnerability · Source |
| CVE-2018-2794 | suse_vex | SUSE CVE CVE-2018-2794 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-07-26T00:24:49+00:00 | Vulnerability · Source |
| CVE-2018-2796 | suse_vex | SUSE CVE CVE-2018-2796 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-07-26T00:24:47+00:00 | Vulnerability · Source |
| CVE-2018-2798 | suse_vex | SUSE CVE CVE-2018-2798 | known affected: 527 known not affected: 179 recommended: 1098 | 2026-07-26T00:24:45+00:00 | Vulnerability · Source |
| CVE-2018-2940 | suse_vex | SUSE CVE CVE-2018-2940 | known affected: 527 known not affected: 214 recommended: 1194 | 2026-07-26T00:24:39+00:00 | Vulnerability · Source |
| CVE-2018-2942 | suse_vex | SUSE CVE CVE-2018-2942 | known not affected: 42 | 2026-07-26T00:24:37+00:00 | Vulnerability · Source |
| CVE-2018-3136 | suse_vex | SUSE CVE CVE-2018-3136 | known affected: 411 known not affected: 103 recommended: 1133 | 2026-07-26T00:24:30+00:00 | Vulnerability · Source |
| CVE-2018-3139 | suse_vex | SUSE CVE CVE-2018-3139 | known affected: 411 known not affected: 103 recommended: 1133 | 2026-07-26T00:24:29+00:00 | Vulnerability · Source |
| CVE-2018-3150 | suse_vex | SUSE CVE CVE-2018-3150 | known affected: 394 known not affected: 81 recommended: 292 | 2026-07-26T00:24:25+00:00 | Vulnerability · Source |
| CVE-2018-3968 | suse_vex | SUSE CVE CVE-2018-3968 | known not affected: 20 | 2026-07-26T00:24:10+00:00 | Vulnerability · Source |
| CVE-2018-4121 | suse_vex | SUSE CVE CVE-2018-4121 | known affected: 116 recommended: 515 | 2026-07-26T00:24:03+00:00 | Vulnerability · Source |
| CVE-2018-4271 | suse_vex | SUSE CVE CVE-2018-4271 | known affected: 108 known not affected: 82 recommended: 127 | 2026-07-26T00:23:43+00:00 | Vulnerability · Source |
| CVE-2018-5100 | suse_vex | SUSE CVE CVE-2018-5100 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:23:10+00:00 | Vulnerability · Source |
| CVE-2018-5101 | suse_vex | SUSE CVE CVE-2018-5101 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:23:08+00:00 | Vulnerability · Source |
| CVE-2018-5107 | suse_vex | SUSE CVE CVE-2018-5107 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:23:04+00:00 | Vulnerability · Source |
| CVE-2018-5108 | suse_vex | SUSE CVE CVE-2018-5108 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:23:01+00:00 | Vulnerability · Source |
| CVE-2018-5109 | suse_vex | SUSE CVE CVE-2018-5109 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:59+00:00 | Vulnerability · Source |
| CVE-2018-5112 | suse_vex | SUSE CVE CVE-2018-5112 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:57+00:00 | Vulnerability · Source |
| CVE-2018-5113 | suse_vex | SUSE CVE CVE-2018-5113 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:56+00:00 | Vulnerability · Source |
| CVE-2018-5116 | suse_vex | SUSE CVE CVE-2018-5116 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:54+00:00 | Vulnerability · Source |
| CVE-2018-5119 | suse_vex | SUSE CVE CVE-2018-5119 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:52+00:00 | Vulnerability · Source |
| CVE-2018-5124 | suse_vex | SUSE CVE CVE-2018-5124 | known not affected: 51 | 2026-07-26T00:22:50+00:00 | Vulnerability · Source |
| CVE-2018-5134 | suse_vex | SUSE CVE CVE-2018-5134 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-26T00:22:47+00:00 | Vulnerability · Source |
| CVE-2018-5136 | suse_vex | SUSE CVE CVE-2018-5136 | known affected: 1 known not affected: 54 recommended: 12 | 2026-07-26T00:22:45+00:00 | Vulnerability · Source |