VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283095 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2018-5104 | suse_vex | SUSE CVE CVE-2018-5104 | known affected: 2 recommended: 402 | 2026-07-19T18:29:46+00:00 | Vulnerability · Source |
| CVE-2018-5117 | suse_vex | SUSE CVE CVE-2018-5117 | known affected: 2 recommended: 402 | 2026-07-19T18:29:45+00:00 | Vulnerability · Source |
| CVE-2018-5147 | suse_vex | SUSE CVE CVE-2018-5147 | known affected: 27 known not affected: 198 recommended: 304 | 2026-07-19T18:29:43+00:00 | Vulnerability · Source |
| CVE-2018-5150 | suse_vex | SUSE CVE CVE-2018-5150 | known affected: 24 recommended: 447 | 2026-07-19T18:29:42+00:00 | Vulnerability · Source |
| CVE-2018-5163 | suse_vex | SUSE CVE CVE-2018-5163 | known affected: 24 recommended: 74 | 2026-07-19T18:29:40+00:00 | Vulnerability · Source |
| CVE-2018-5164 | suse_vex | SUSE CVE CVE-2018-5164 | known affected: 24 recommended: 74 | 2026-07-19T18:29:39+00:00 | Vulnerability · Source |
| CVE-2018-5165 | suse_vex | SUSE CVE CVE-2018-5165 | known affected: 24 recommended: 74 | 2026-07-19T18:29:38+00:00 | Vulnerability · Source |
| CVE-2018-5166 | suse_vex | SUSE CVE CVE-2018-5166 | known affected: 24 recommended: 74 | 2026-07-19T18:29:37+00:00 | Vulnerability · Source |
| CVE-2018-5170 | suse_vex | SUSE CVE CVE-2018-5170 | known affected: 24 recommended: 87 | 2026-07-19T18:29:36+00:00 | Vulnerability · Source |
| CVE-2018-5175 | suse_vex | SUSE CVE CVE-2018-5175 | known affected: 24 recommended: 74 | 2026-07-19T18:29:34+00:00 | Vulnerability · Source |
| CVE-2018-5177 | suse_vex | SUSE CVE CVE-2018-5177 | known affected: 24 recommended: 74 | 2026-07-19T18:29:33+00:00 | Vulnerability · Source |
| CVE-2018-5178 | suse_vex | SUSE CVE CVE-2018-5178 | known affected: 24 recommended: 435 | 2026-07-19T18:29:32+00:00 | Vulnerability · Source |
| CVE-2018-5183 | suse_vex | SUSE CVE CVE-2018-5183 | known affected: 24 recommended: 435 | 2026-07-19T18:29:31+00:00 | Vulnerability · Source |
| CVE-2018-5188 | suse_vex | SUSE CVE CVE-2018-5188 | known affected: 21 recommended: 445 | 2026-07-19T18:29:30+00:00 | Vulnerability · Source |
| CVE-2018-5727 | suse_vex | SUSE CVE CVE-2018-5727 | known affected: 2 known not affected: 11 recommended: 189 | 2026-07-19T18:29:28+00:00 | Vulnerability · Source |
| CVE-2018-5736 | suse_vex | SUSE CVE CVE-2018-5736 | known not affected: 451 recommended: 306 | 2026-07-19T18:29:27+00:00 | Vulnerability · Source |
| CVE-2018-5815 | suse_vex | SUSE CVE CVE-2018-5815 | known not affected: 18 recommended: 98 | 2026-07-19T18:29:26+00:00 | Vulnerability · Source |
| CVE-2018-5819 | suse_vex | SUSE CVE CVE-2018-5819 | recommended: 134 | 2026-07-19T18:29:25+00:00 | Vulnerability · Source |
| CVE-2018-6551 | suse_vex | SUSE CVE CVE-2018-6551 | known affected: 50 known not affected: 230 recommended: 1150 | 2026-07-19T18:29:23+00:00 | Vulnerability · Source |
| CVE-2018-6767 | suse_vex | SUSE CVE CVE-2018-6767 | known affected: 394 known not affected: 24 recommended: 227 | 2026-07-19T18:29:22+00:00 | Vulnerability · Source |
| CVE-2018-6872 | suse_vex | SUSE CVE CVE-2018-6872 | known affected: 441 known not affected: 61 recommended: 504 | 2026-07-19T18:29:20+00:00 | Vulnerability · Source |
| CVE-2018-6913 | suse_vex | SUSE CVE CVE-2018-6913 | known affected: 322 recommended: 416 | 2026-07-19T18:29:19+00:00 | Vulnerability · Source |
| CVE-2018-6942 | suse_vex | SUSE CVE CVE-2018-6942 | known affected: 322 known not affected: 65 recommended: 379 | 2026-07-19T18:29:18+00:00 | Vulnerability · Source |