VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2018-5137 | suse_vex | SUSE CVE CVE-2018-5137 | known affected: 1 known not affected: 54 recommended: 12 | 2026-07-26T00:22:43+00:00 | Vulnerability · Source |
| CVE-2018-5138 | suse_vex | SUSE CVE CVE-2018-5138 | known affected: 1 known not affected: 54 recommended: 12 | 2026-07-26T00:22:40+00:00 | Vulnerability · Source |
| CVE-2018-5165 | suse_vex | SUSE CVE CVE-2018-5165 | known affected: 26 recommended: 83 | 2026-07-26T00:22:30+00:00 | Vulnerability · Source |
| CVE-2018-5169 | suse_vex | SUSE CVE CVE-2018-5169 | known affected: 26 recommended: 83 | 2026-07-26T00:22:26+00:00 | Vulnerability · Source |
| CVE-2018-5172 | suse_vex | SUSE CVE CVE-2018-5172 | known affected: 26 recommended: 83 | 2026-07-26T00:22:23+00:00 | Vulnerability · Source |
| CVE-2018-5173 | suse_vex | SUSE CVE CVE-2018-5173 | known affected: 26 recommended: 83 | 2026-07-26T00:22:21+00:00 | Vulnerability · Source |
| CVE-2018-5185 | suse_vex | SUSE CVE CVE-2018-5185 | known affected: 26 recommended: 87 | 2026-07-26T00:22:10+00:00 | Vulnerability · Source |
| CVE-2018-5381 | suse_vex | SUSE CVE CVE-2018-5381 | known affected: 1 known not affected: 125 recommended: 357 | 2026-07-26T00:21:55+00:00 | Vulnerability · Source |
| CVE-2018-5710 | suse_vex | SUSE CVE CVE-2018-5710 | known not affected: 88 | 2026-07-26T00:21:49+00:00 | Vulnerability · Source |
| CVE-2018-6057 | suse_vex | SUSE CVE CVE-2018-6057 | recommended: 10 | 2026-07-26T00:21:28+00:00 | Vulnerability · Source |
| CVE-2018-6067 | suse_vex | SUSE CVE CVE-2018-6067 | recommended: 10 | 2026-07-26T00:21:24+00:00 | Vulnerability · Source |
| CVE-2018-6071 | suse_vex | SUSE CVE CVE-2018-6071 | recommended: 10 | 2026-07-26T00:21:21+00:00 | Vulnerability · Source |
| CVE-2018-6072 | suse_vex | SUSE CVE CVE-2018-6072 | recommended: 10 | 2026-07-26T00:21:20+00:00 | Vulnerability · Source |
| CVE-2018-6074 | suse_vex | SUSE CVE CVE-2018-6074 | recommended: 10 | 2026-07-26T00:21:19+00:00 | Vulnerability · Source |
| CVE-2018-6075 | suse_vex | SUSE CVE CVE-2018-6075 | recommended: 10 | 2026-07-26T00:21:17+00:00 | Vulnerability · Source |
| CVE-2018-6077 | suse_vex | SUSE CVE CVE-2018-6077 | recommended: 10 | 2026-07-26T00:21:16+00:00 | Vulnerability · Source |
| CVE-2018-6078 | suse_vex | SUSE CVE CVE-2018-6078 | recommended: 10 | 2026-07-26T00:21:15+00:00 | Vulnerability · Source |
| CVE-2018-6405 | suse_vex | SUSE CVE CVE-2018-6405 | known affected: 95 recommended: 186 | 2026-07-26T00:21:04+00:00 | Vulnerability · Source |
| CVE-2018-6412 | suse_vex | SUSE CVE CVE-2018-6412 | known not affected: 14 | 2026-07-26T00:21:03+00:00 | Vulnerability · Source |
| CVE-2018-6797 | suse_vex | SUSE CVE CVE-2018-6797 | recommended: 86 | 2026-07-26T00:20:55+00:00 | Vulnerability · Source |
| CVE-2018-6829 | suse_vex | SUSE CVE CVE-2018-6829 | known not affected: 153 | 2026-07-26T00:20:53+00:00 | Vulnerability · Source |
| CVE-2018-7183 | suse_vex | SUSE CVE CVE-2018-7183 | known affected: 27 known not affected: 20 recommended: 100 | 2026-07-26T00:20:46+00:00 | Vulnerability · Source |
| CVE-2018-7226 | suse_vex | SUSE CVE CVE-2018-7226 | known not affected: 50 | 2026-07-26T00:20:44+00:00 | Vulnerability · Source |
| CVE-2018-7324 | suse_vex | SUSE CVE CVE-2018-7324 | known affected: 1 known not affected: 115 recommended: 583 | 2026-07-26T00:20:40+00:00 | Vulnerability · Source |