VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284477 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-7323 | suse_vex | SUSE CVE CVE-2018-7323 | known affected: 1 known not affected: 115 recommended: 583 | 2026-07-26T00:20:41+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-7329 | suse_vex | SUSE CVE CVE-2018-7329 | known affected: 1 known not affected: 115 recommended: 589 | 2026-07-26T00:20:38+00:00 | Vulnerability · Source |
| CVE-2018-7330 | suse_vex | SUSE CVE CVE-2018-7330 | known affected: 1 known not affected: 115 recommended: 583 | 2026-07-26T00:20:37+00:00 | Vulnerability · Source |
| CVE-2018-7334 | suse_vex | SUSE CVE CVE-2018-7334 | known affected: 1 known not affected: 115 recommended: 589 | 2026-07-26T00:20:36+00:00 | Vulnerability · Source |
| CVE-2018-7337 | suse_vex | SUSE CVE CVE-2018-7337 | known affected: 1 known not affected: 115 recommended: 589 | 2026-07-26T00:20:34+00:00 | Vulnerability · Source |
| CVE-2018-7420 | suse_vex | SUSE CVE CVE-2018-7420 | known affected: 1 known not affected: 115 recommended: 589 | 2026-07-26T00:20:33+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-7455 | suse_vex | SUSE CVE CVE-2018-7455 | known not affected: 381 | 2026-07-26T00:20:30+00:00 | Vulnerability · Source |
| CVE-2018-7485 | suse_vex | SUSE CVE CVE-2018-7485 | known affected: 398 known not affected: 167 recommended: 194 | 2026-07-26T00:20:29+00:00 | Vulnerability · Source |
| CVE-2018-7540 | suse_vex | SUSE CVE CVE-2018-7540 | known affected: 352 known not affected: 110 recommended: 449 | 2026-07-26T00:20:27+00:00 | Vulnerability · Source |
| CVE-2018-7548 | suse_vex | SUSE CVE CVE-2018-7548 | known not affected: 59 | 2026-07-26T00:20:26+00:00 | Vulnerability · Source |
| CVE-2018-7569 | suse_vex | SUSE CVE CVE-2018-7569 | known affected: 452 known not affected: 30 recommended: 509 | 2026-07-26T00:20:24+00:00 | Vulnerability · Source |
| CVE-2018-7570 | suse_vex | SUSE CVE CVE-2018-7570 | known affected: 452 known not affected: 30 recommended: 507 | 2026-07-26T00:20:23+00:00 | Vulnerability · Source |
| CVE-2018-7643 | suse_vex | SUSE CVE CVE-2018-7643 | known affected: 452 known not affected: 30 recommended: 509 | 2026-07-26T00:20:22+00:00 | Vulnerability · Source |
| CVE-2018-7731 | suse_vex | SUSE CVE CVE-2018-7731 | known not affected: 165 recommended: 120 | 2026-07-26T00:20:21+00:00 | Vulnerability · Source |
| CVE-2018-7753 | suse_vex | SUSE CVE CVE-2018-7753 | recommended: 15 | 2026-07-26T00:20:19+00:00 | Vulnerability · Source |
| CVE-2018-7755 | suse_vex | SUSE CVE CVE-2018-7755 | known affected: 391 known not affected: 214 recommended: 336 | 2026-07-26T00:20:18+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-8014 | suse_vex | SUSE CVE CVE-2018-8014 | known affected: 395 known not affected: 164 recommended: 256 | 2026-07-26T00:20:16+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-8088 | suse_vex | SUSE CVE CVE-2018-8088 | known affected: 394 known not affected: 1 recommended: 221 | 2026-07-26T00:20:10+00:00 | Vulnerability · Source |
| CVE-2018-8098 | suse_vex | SUSE CVE CVE-2018-8098 | known not affected: 89 recommended: 139 | 2026-07-26T00:20:08+00:00 | Vulnerability · Source |
| CVE-2018-8107 | suse_vex | SUSE CVE CVE-2018-8107 | known not affected: 381 | 2026-07-26T00:20:07+00:00 | Vulnerability · Source |
| CVE-2018-8518 | suse_vex | SUSE CVE CVE-2018-8518 | recommended: 231 | 2026-07-26T00:20:06+00:00 | Vulnerability · Source |
| CVE-2018-8740 | suse_vex | SUSE CVE CVE-2018-8740 | known affected: 384 known not affected: 243 recommended: 466 | 2026-07-26T00:20:04+00:00 | Vulnerability · Source |
| CVE-2018-8769 | suse_vex | SUSE CVE CVE-2018-8769 | known not affected: 763 | 2026-07-26T00:20:03+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-8822 | suse_vex | SUSE CVE CVE-2018-8822 | known not affected: 223 recommended: 658 | 2026-07-26T00:19:59+00:00 | Vulnerability · Source |
| CVE-2018-8905 | suse_vex | SUSE CVE CVE-2018-8905 | known affected: 441 recommended: 291 | 2026-07-26T00:19:58+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-9154 | suse_vex | SUSE CVE CVE-2018-9154 | known affected: 46 recommended: 153 | 2026-07-26T00:19:44+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-9262 | suse_vex | SUSE CVE CVE-2018-9262 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:40+00:00 | Vulnerability · Source |
| CVE-2018-9263 | suse_vex | SUSE CVE CVE-2018-9263 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:38+00:00 | Vulnerability · Source |
| CVE-2018-9266 | suse_vex | SUSE CVE CVE-2018-9266 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:35+00:00 | Vulnerability · Source |
| CVE-2018-9267 | suse_vex | SUSE CVE CVE-2018-9267 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:33+00:00 | Vulnerability · Source |
| CVE-2018-9268 | suse_vex | SUSE CVE CVE-2018-9268 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:31+00:00 | Vulnerability · Source |
| CVE-2018-9270 | suse_vex | SUSE CVE CVE-2018-9270 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:29+00:00 | Vulnerability · Source |
| CVE-2018-9272 | suse_vex | SUSE CVE CVE-2018-9272 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:27+00:00 | Vulnerability · Source |
| CVE-2018-9273 | suse_vex | SUSE CVE CVE-2018-9273 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-26T00:19:25+00:00 | Vulnerability · Source |
| CVE-2018-9274 | suse_vex | SUSE CVE CVE-2018-9274 | known affected: 89 known not affected: 115 recommended: 549 | 2026-07-26T00:19:22+00:00 | Vulnerability · Source |