VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284520 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-10906 | suse_vex | SUSE CVE CVE-2018-10906 | known affected: 351 recommended: 461 | 2026-07-26T00:17:58+00:00 | Vulnerability · Source |
| CVE-2018-10916 | suse_vex | SUSE CVE CVE-2018-10916 | known affected: 13 known not affected: 19 recommended: 73 | 2026-07-26T00:17:56+00:00 | Vulnerability · Source |
| CVE-2018-10936 | suse_vex | SUSE CVE CVE-2018-10936 | known affected: 394 recommended: 37 | 2026-07-26T00:17:54+00:00 | Vulnerability · Source |
| CVE-2018-11233 | suse_vex | SUSE CVE CVE-2018-11233 | known affected: 112 known not affected: 27 recommended: 917 | 2026-07-26T00:17:51+00:00 | Vulnerability · Source |
| CVE-2018-11236 | suse_vex | SUSE CVE CVE-2018-11236 | known affected: 439 known not affected: 109 recommended: 1376 | 2026-07-26T00:17:48+00:00 | Vulnerability · Source |
| CVE-2018-11354 | suse_vex | SUSE CVE CVE-2018-11354 | known affected: 87 recommended: 860 | 2026-07-26T00:17:46+00:00 | Vulnerability · Source |
| CVE-2018-11360 | suse_vex | SUSE CVE CVE-2018-11360 | known affected: 87 recommended: 1022 | 2026-07-26T00:17:44+00:00 | Vulnerability · Source |
| CVE-2018-11361 | suse_vex | SUSE CVE CVE-2018-11361 | known affected: 87 recommended: 860 | 2026-07-26T00:17:41+00:00 | Vulnerability · Source |
| CVE-2018-11412 | suse_vex | SUSE CVE CVE-2018-11412 | known not affected: 396 | 2026-07-26T00:17:39+00:00 | Vulnerability · Source |
| CVE-2018-11490 | suse_vex | SUSE CVE CVE-2018-11490 | known affected: 429 known not affected: 16 recommended: 136 | 2026-07-26T00:17:36+00:00 | Vulnerability · Source |
| CVE-2018-11531 | suse_vex | SUSE CVE CVE-2018-11531 | known not affected: 22 recommended: 107 | 2026-07-26T00:17:34+00:00 | Vulnerability · Source |
| CVE-2018-11574 | suse_vex | SUSE CVE CVE-2018-11574 | known not affected: 27 | 2026-07-26T00:17:32+00:00 | Vulnerability · Source |
| CVE-2018-11625 | suse_vex | SUSE CVE CVE-2018-11625 | known not affected: 128 recommended: 567 | 2026-07-26T00:17:29+00:00 | Vulnerability · Source |
| CVE-2018-11645 | suse_vex | SUSE CVE CVE-2018-11645 | known affected: 1 known not affected: 176 recommended: 6 | 2026-07-26T00:17:28+00:00 | Vulnerability · Source |
| CVE-2018-11656 | suse_vex | SUSE CVE CVE-2018-11656 | known not affected: 364 recommended: 100 | 2026-07-26T00:17:26+00:00 | Vulnerability · Source |
| CVE-2018-11780 | suse_vex | SUSE CVE CVE-2018-11780 | known affected: 1 known not affected: 121 recommended: 190 | 2026-07-26T00:17:24+00:00 | Vulnerability · Source |
| CVE-2018-12085 | suse_vex | SUSE CVE CVE-2018-12085 | known affected: 54 known not affected: 178 recommended: 316 | 2026-07-26T00:17:22+00:00 | Vulnerability · Source |
| CVE-2018-12086 | suse_vex | SUSE CVE CVE-2018-12086 | known not affected: 266 recommended: 988 | 2026-07-26T00:17:20+00:00 | Vulnerability · Source |
| CVE-2018-12178 | suse_vex | SUSE CVE CVE-2018-12178 | known affected: 50 known not affected: 9 recommended: 239 | 2026-07-26T00:17:19+00:00 | Vulnerability · Source |
| CVE-2018-12179 | suse_vex | SUSE CVE CVE-2018-12179 | known not affected: 47 | 2026-07-26T00:17:17+00:00 | Vulnerability · Source |
| CVE-2018-12183 | suse_vex | SUSE CVE CVE-2018-12183 | known not affected: 47 | 2026-07-26T00:17:16+00:00 | Vulnerability · Source |
| CVE-2018-12207 | suse_vex | SUSE CVE CVE-2018-12207 | known affected: 633 known not affected: 238 recommended: 2940 | 2026-07-26T00:17:14+00:00 | Vulnerability · Source |
| CVE-2018-12264 | suse_vex | SUSE CVE CVE-2018-12264 | known not affected: 36 recommended: 159 | 2026-07-26T00:17:12+00:00 | Vulnerability · Source |
| CVE-2018-12293 | suse_vex | SUSE CVE CVE-2018-12293 | known affected: 162 known not affected: 82 | 2026-07-26T00:17:10+00:00 | Vulnerability · Source |
| CVE-2018-12294 | suse_vex | SUSE CVE CVE-2018-12294 | known affected: 162 known not affected: 82 | 2026-07-26T00:17:09+00:00 | Vulnerability · Source |
| CVE-2018-12327 | suse_vex | SUSE CVE CVE-2018-12327 | known affected: 36 recommended: 119 | 2026-07-26T00:17:07+00:00 | Vulnerability · Source |
| CVE-2018-12365 | suse_vex | SUSE CVE CVE-2018-12365 | known affected: 21 recommended: 451 | 2026-07-26T00:17:04+00:00 | Vulnerability · Source |
| CVE-2018-12368 | suse_vex | SUSE CVE CVE-2018-12368 | known affected: 21 recommended: 322 | 2026-07-26T00:17:02+00:00 | Vulnerability · Source |
| CVE-2018-12381 | suse_vex | SUSE CVE CVE-2018-12381 | known not affected: 200 recommended: 721 | 2026-07-26T00:17:00+00:00 | Vulnerability · Source |
| CVE-2018-12385 | suse_vex | SUSE CVE CVE-2018-12385 | known affected: 1 recommended: 819 | 2026-07-26T00:16:58+00:00 | Vulnerability · Source |
| CVE-2018-12393 | suse_vex | SUSE CVE CVE-2018-12393 | known affected: 1 recommended: 416 | 2026-07-26T00:16:56+00:00 | Vulnerability · Source |
| CVE-2018-12397 | suse_vex | SUSE CVE CVE-2018-12397 | known affected: 1 recommended: 325 | 2026-07-26T00:16:55+00:00 | Vulnerability · Source |
| CVE-2018-12437 | suse_vex | SUSE CVE CVE-2018-12437 | known not affected: 55 recommended: 4 | 2026-07-26T00:16:53+00:00 | Vulnerability · Source |
| CVE-2018-12471 | suse_vex | SUSE CVE CVE-2018-12471 | recommended: 82 | 2026-07-26T00:16:52+00:00 | Vulnerability · Source |
| CVE-2018-12472 | suse_vex | SUSE CVE CVE-2018-12472 | recommended: 82 | 2026-07-26T00:16:50+00:00 | Vulnerability · Source |
| CVE-2018-12599 | suse_vex | SUSE CVE CVE-2018-12599 | known not affected: 35 recommended: 739 | 2026-07-26T00:16:49+00:00 | Vulnerability · Source |
| CVE-2018-12882 | suse_vex | SUSE CVE CVE-2018-12882 | known affected: 550 known not affected: 1549 recommended: 3595 | 2026-07-26T00:16:46+00:00 | Vulnerability · Source |
| CVE-2018-12886 | suse_vex | SUSE CVE CVE-2018-12886 | known not affected: 1106 | 2026-07-26T00:16:44+00:00 | Vulnerability · Source |
| CVE-2018-12891 | suse_vex | SUSE CVE CVE-2018-12891 | known affected: 352 known not affected: 42 recommended: 534 | 2026-07-26T00:16:42+00:00 | Vulnerability · Source |
| CVE-2018-12930 | suse_vex | SUSE CVE CVE-2018-12930 | known not affected: 563 | 2026-07-26T00:16:40+00:00 | Vulnerability · Source |
| CVE-2018-12938 | suse_vex | SUSE CVE CVE-2018-12938 | known affected: 61 | 2026-07-26T00:16:38+00:00 | Vulnerability · Source |
| CVE-2018-13065 | suse_vex | SUSE CVE CVE-2018-13065 | known not affected: 25 | 2026-07-26T00:16:36+00:00 | Vulnerability · Source |
| CVE-2018-13440 | suse_vex | SUSE CVE CVE-2018-13440 | known affected: 1 known not affected: 4 recommended: 179 | 2026-07-26T00:16:34+00:00 | Vulnerability · Source |
| CVE-2018-13785 | suse_vex | SUSE CVE CVE-2018-13785 | known affected: 320 known not affected: 161 recommended: 1173 | 2026-07-26T00:16:32+00:00 | Vulnerability · Source |
| CVE-2018-13796 | suse_vex | SUSE CVE CVE-2018-13796 | known affected: 16 recommended: 28 | 2026-07-26T00:16:30+00:00 | Vulnerability · Source |
| CVE-2018-14338 | suse_vex | SUSE CVE CVE-2018-14338 | known not affected: 61 recommended: 8 | 2026-07-26T00:16:27+00:00 | Vulnerability · Source |
| CVE-2018-14339 | suse_vex | SUSE CVE CVE-2018-14339 | known affected: 118 recommended: 1022 | 2026-07-26T00:16:25+00:00 | Vulnerability · Source |
| CVE-2018-14342 | suse_vex | SUSE CVE CVE-2018-14342 | known affected: 118 recommended: 1022 | 2026-07-26T00:16:23+00:00 | Vulnerability · Source |
| CVE-2018-14350 | suse_vex | SUSE CVE CVE-2018-14350 | known affected: 29 recommended: 200 | 2026-07-26T00:16:21+00:00 | Vulnerability · Source |
| CVE-2018-14469 | suse_vex | SUSE CVE CVE-2018-14469 | known affected: 333 recommended: 145 | 2026-07-26T00:16:19+00:00 | Vulnerability · Source |