VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294016 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-5188 | suse_vex | SUSE CVE CVE-2018-5188 | known affected: 21 recommended: 451 | 2026-07-26T00:22:08+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-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-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 |
| CVE-2018-7453 | suse_vex | SUSE CVE CVE-2018-7453 | known not affected: 381 | 2026-07-26T00:20:31+00:00 | Vulnerability · Source |
| CVE-2018-7995 | suse_vex | SUSE CVE CVE-2018-7995 | known not affected: 49 | 2026-07-26T00:20:17+00:00 | Vulnerability · Source |
| CVE-2018-8032 | suse_vex | SUSE CVE CVE-2018-8032 | known affected: 18 recommended: 73 | 2026-07-26T00:20:15+00:00 | Vulnerability · Source |
| CVE-2018-8034 | suse_vex | SUSE CVE CVE-2018-8034 | known affected: 394 known not affected: 101 recommended: 256 | 2026-07-26T00:20:14+00:00 | Vulnerability · Source |
| CVE-2018-8086 | suse_vex | SUSE CVE CVE-2018-8086 | known not affected: 113 | 2026-07-26T00:20:12+00:00 | Vulnerability · Source |
| CVE-2018-8087 | suse_vex | SUSE CVE CVE-2018-8087 | known not affected: 186 recommended: 425 | 2026-07-26T00:20:11+00:00 | Vulnerability · Source |
| CVE-2018-8779 | suse_vex | SUSE CVE CVE-2018-8779 | known affected: 320 known not affected: 22 recommended: 491 | 2026-07-26T00:20:01+00:00 | Vulnerability · Source |
| CVE-2018-8945 | suse_vex | SUSE CVE CVE-2018-8945 | known affected: 454 known not affected: 30 recommended: 509 | 2026-07-26T00:19:56+00:00 | Vulnerability · Source |
| CVE-2018-8976 | suse_vex | SUSE CVE CVE-2018-8976 | known affected: 16 known not affected: 53 recommended: 95 | 2026-07-26T00:19:54+00:00 | Vulnerability · Source |
| CVE-2018-9018 | suse_vex | SUSE CVE CVE-2018-9018 | known affected: 97 recommended: 150 | 2026-07-26T00:19:52+00:00 | Vulnerability · Source |
| CVE-2018-9144 | suse_vex | SUSE CVE CVE-2018-9144 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:51+00:00 | Vulnerability · Source |
| CVE-2018-9145 | suse_vex | SUSE CVE CVE-2018-9145 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:49+00:00 | Vulnerability · Source |
| CVE-2018-9146 | suse_vex | SUSE CVE CVE-2018-9146 | known affected: 4 known not affected: 53 | 2026-07-26T00:19:47+00:00 | Vulnerability · Source |
| CVE-2018-9259 | suse_vex | SUSE CVE CVE-2018-9259 | known affected: 89 known not affected: 115 recommended: 111 | 2026-07-26T00:19:42+00:00 | Vulnerability · Source |
| CVE-2018-9304 | suse_vex | SUSE CVE CVE-2018-9304 | recommended: 8 | 2026-07-26T00:19:20+00:00 | Vulnerability · Source |
| CVE-2018-9415 | suse_vex | SUSE CVE CVE-2018-9415 | known not affected: 113 | 2026-07-26T00:19:18+00:00 | Vulnerability · Source |
| CVE-2018-9422 | suse_vex | SUSE CVE CVE-2018-9422 | known not affected: 71 | 2026-07-26T00:19:16+00:00 | Vulnerability · Source |
| CVE-2018-9465 | suse_vex | SUSE CVE CVE-2018-9465 | known not affected: 71 | 2026-07-26T00:19:14+00:00 | Vulnerability · Source |
| CVE-2018-9518 | suse_vex | SUSE CVE CVE-2018-9518 | known not affected: 71 | 2026-07-26T00:19:10+00:00 | Vulnerability · Source |
| CVE-2018-10074 | suse_vex | SUSE CVE CVE-2018-10074 | known not affected: 14 | 2026-07-26T00:19:01+00:00 | Vulnerability · Source |
| CVE-2018-10115 | suse_vex | SUSE CVE CVE-2018-10115 | known not affected: 32 | 2026-07-26T00:19:00+00:00 | Vulnerability · Source |
| CVE-2018-10126 | suse_vex | SUSE CVE CVE-2018-10126 | known affected: 6 known not affected: 63 | 2026-07-26T00:18:58+00:00 | Vulnerability · Source |
| CVE-2018-10323 | suse_vex | SUSE CVE CVE-2018-10323 | known affected: 320 known not affected: 376 recommended: 1067 | 2026-07-26T00:18:51+00:00 | Vulnerability · Source |
| CVE-2018-10534 | suse_vex | SUSE CVE CVE-2018-10534 | known affected: 453 known not affected: 95 recommended: 345 | 2026-07-26T00:18:46+00:00 | Vulnerability · Source |