VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283038 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2018-7253 | suse_vex | SUSE CVE CVE-2018-7253 | known affected: 394 known not affected: 54 recommended: 227 | 2026-07-19T18:29:16+00:00 | Vulnerability · Source |
| CVE-2018-7254 | suse_vex | SUSE CVE CVE-2018-7254 | known affected: 394 known not affected: 85 recommended: 227 | 2026-07-19T18:29:15+00:00 | Vulnerability · Source |
| CVE-2018-7321 | suse_vex | SUSE CVE CVE-2018-7321 | known affected: 1 known not affected: 115 recommended: 571 | 2026-07-19T18:29:14+00:00 | Vulnerability · Source |
| CVE-2018-7322 | suse_vex | SUSE CVE CVE-2018-7322 | known affected: 1 known not affected: 115 recommended: 565 | 2026-07-19T18:29:12+00:00 | Vulnerability · Source |
| CVE-2018-7324 | suse_vex | SUSE CVE CVE-2018-7324 | known affected: 1 known not affected: 115 recommended: 565 | 2026-07-19T18:29:11+00:00 | Vulnerability · Source |
| CVE-2018-7332 | suse_vex | SUSE CVE CVE-2018-7332 | known affected: 1 known not affected: 115 recommended: 565 | 2026-07-19T18:29:10+00:00 | Vulnerability · Source |
| CVE-2018-7336 | suse_vex | SUSE CVE CVE-2018-7336 | known affected: 1 known not affected: 115 recommended: 571 | 2026-07-19T18:29:09+00:00 | Vulnerability · Source |
| CVE-2018-7409 | suse_vex | SUSE CVE CVE-2018-7409 | known affected: 396 known not affected: 167 recommended: 190 | 2026-07-19T18:29:08+00:00 | Vulnerability · Source |
| CVE-2018-7419 | suse_vex | SUSE CVE CVE-2018-7419 | known affected: 1 known not affected: 115 recommended: 571 | 2026-07-19T18:29:06+00:00 | Vulnerability · Source |
| CVE-2018-7420 | suse_vex | SUSE CVE CVE-2018-7420 | known affected: 1 known not affected: 115 recommended: 571 | 2026-07-19T18:29:05+00:00 | Vulnerability · Source |
| CVE-2018-7536 | suse_vex | SUSE CVE CVE-2018-7536 | recommended: 23 | 2026-07-19T18:29:04+00:00 | Vulnerability · Source |
| CVE-2018-7537 | suse_vex | SUSE CVE CVE-2018-7537 | recommended: 23 | 2026-07-19T18:29:03+00:00 | Vulnerability · Source |
| CVE-2018-7550 | suse_vex | SUSE CVE CVE-2018-7550 | known affected: 57 known not affected: 376 recommended: 1774 | 2026-07-19T18:29:01+00:00 | Vulnerability · Source |
| CVE-2018-7730 | suse_vex | SUSE CVE CVE-2018-7730 | known affected: 3 known not affected: 60 recommended: 152 | 2026-07-19T18:29:00+00:00 | Vulnerability · Source |
| CVE-2018-7999 | suse_vex | SUSE CVE CVE-2018-7999 | known affected: 394 known not affected: 78 recommended: 224 | 2026-07-19T18:28:59+00:00 | Vulnerability · Source |
| CVE-2018-8099 | suse_vex | SUSE CVE CVE-2018-8099 | known not affected: 71 recommended: 149 | 2026-07-19T18:28:58+00:00 | Vulnerability · Source |
| CVE-2018-8787 | suse_vex | SUSE CVE CVE-2018-8787 | recommended: 219 | 2026-07-19T18:28:56+00:00 | Vulnerability · Source |
| CVE-2018-8789 | suse_vex | SUSE CVE CVE-2018-8789 | recommended: 215 | 2026-07-19T18:28:55+00:00 | Vulnerability · Source |
| CVE-2018-9055 | suse_vex | SUSE CVE CVE-2018-9055 | known affected: 39 known not affected: 61 recommended: 163 | 2026-07-19T18:28:54+00:00 | Vulnerability · Source |
| CVE-2018-9256 | suse_vex | SUSE CVE CVE-2018-9256 | known affected: 72 known not affected: 115 recommended: 543 | 2026-07-19T18:28:52+00:00 | Vulnerability · Source |
| CVE-2018-9264 | suse_vex | SUSE CVE CVE-2018-9264 | known affected: 72 known not affected: 115 recommended: 543 | 2026-07-19T18:28:51+00:00 | Vulnerability · Source |