VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-4358 | suse_vex | SUSE CVE CVE-2018-4358 | known affected: 108 known not affected: 82 recommended: 959 | 2026-07-26T00:23:29+00:00 | Vulnerability · Source |
| CVE-2018-4359 | suse_vex | SUSE CVE CVE-2018-4359 | known affected: 108 known not affected: 82 recommended: 971 | 2026-07-26T00:23:27+00:00 | Vulnerability · Source |
| CVE-2018-4372 | suse_vex | SUSE CVE CVE-2018-4372 | known affected: 108 recommended: 971 | 2026-07-26T00:23:25+00:00 | Vulnerability · Source |
| CVE-2018-4375 | suse_vex | SUSE CVE CVE-2018-4375 | known affected: 108 recommended: 971 | 2026-07-26T00:23:23+00:00 | Vulnerability · Source |
| CVE-2018-4376 | suse_vex | SUSE CVE CVE-2018-4376 | known affected: 108 recommended: 959 | 2026-07-26T00:23:21+00:00 | Vulnerability · Source |
| CVE-2018-4378 | suse_vex | SUSE CVE CVE-2018-4378 | known affected: 108 recommended: 959 | 2026-07-26T00:23:18+00:00 | Vulnerability · Source |
| CVE-2018-4868 | suse_vex | SUSE CVE CVE-2018-4868 | known affected: 4 known not affected: 53 recommended: 8 | 2026-07-26T00:23:14+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-5104 | suse_vex | SUSE CVE CVE-2018-5104 | known affected: 2 recommended: 408 | 2026-07-26T00:23:06+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-5148 | suse_vex | SUSE CVE CVE-2018-5148 | known affected: 1 recommended: 311 | 2026-07-26T00:22:38+00:00 | Vulnerability · Source |
| CVE-2018-5155 | suse_vex | SUSE CVE CVE-2018-5155 | known affected: 26 recommended: 459 | 2026-07-26T00:22:36+00:00 | Vulnerability · Source |
| CVE-2018-5164 | suse_vex | SUSE CVE CVE-2018-5164 | known affected: 26 recommended: 83 | 2026-07-26T00:22:32+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-5174 | suse_vex | SUSE CVE CVE-2018-5174 | known affected: 26 recommended: 214 | 2026-07-26T00:22:19+00:00 | Vulnerability · Source |
| CVE-2018-5176 | suse_vex | SUSE CVE CVE-2018-5176 | known affected: 26 recommended: 83 | 2026-07-26T00:22:17+00:00 | Vulnerability · Source |
| CVE-2018-5184 | suse_vex | SUSE CVE CVE-2018-5184 | known affected: 26 recommended: 87 | 2026-07-26T00:22:12+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-5188 | suse_vex | SUSE CVE CVE-2018-5188 | known affected: 21 recommended: 451 | 2026-07-26T00:22:08+00:00 | Vulnerability · Source |
| CVE-2018-5334 | suse_vex | SUSE CVE CVE-2018-5334 | known affected: 86 known not affected: 115 recommended: 589 | 2026-07-26T00:22:03+00:00 | Vulnerability · Source |
| CVE-2018-5360 | suse_vex | SUSE CVE CVE-2018-5360 | known not affected: 62 | 2026-07-26T00:21:59+00:00 | Vulnerability · Source |
| CVE-2018-5379 | suse_vex | SUSE CVE CVE-2018-5379 | known affected: 1 known not affected: 125 recommended: 363 | 2026-07-26T00:21:57+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-5741 | suse_vex | SUSE CVE CVE-2018-5741 | known affected: 18 known not affected: 255 recommended: 600 | 2026-07-26T00:21:44+00:00 | Vulnerability · Source |
| CVE-2018-5744 | suse_vex | SUSE CVE CVE-2018-5744 | known affected: 27 known not affected: 388 recommended: 306 | 2026-07-26T00:21:40+00:00 | Vulnerability · Source |
| CVE-2018-5750 | suse_vex | SUSE CVE CVE-2018-5750 | known affected: 14 known not affected: 57 recommended: 12 | 2026-07-26T00:21:38+00:00 | Vulnerability · Source |
| CVE-2018-5848 | suse_vex | SUSE CVE CVE-2018-5848 | known affected: 85 known not affected: 192 recommended: 606 | 2026-07-26T00:21:30+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-6065 | suse_vex | SUSE CVE CVE-2018-6065 | recommended: 10 | 2026-07-26T00:21:27+00:00 | Vulnerability · Source |
| CVE-2018-6066 | suse_vex | SUSE CVE CVE-2018-6066 | recommended: 10 | 2026-07-26T00:21:25+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-6070 | suse_vex | SUSE CVE CVE-2018-6070 | recommended: 10 | 2026-07-26T00:21:23+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 |