VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| 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-6082 | suse_vex | SUSE CVE CVE-2018-6082 | recommended: 10 | 2026-07-26T00:21:14+00:00 | Vulnerability · Source |
| CVE-2018-6307 | suse_vex | SUSE CVE CVE-2018-6307 | known affected: 41 recommended: 129 | 2026-07-26T00:21:07+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-6644 | suse_vex | SUSE CVE CVE-2018-6644 | known not affected: 35 recommended: 40 | 2026-07-26T00:20:56+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-6954 | suse_vex | SUSE CVE CVE-2018-6954 | known affected: 320 recommended: 1258 | 2026-07-26T00:20:50+00:00 | Vulnerability · Source |
| CVE-2018-7170 | suse_vex | SUSE CVE CVE-2018-7170 | known affected: 32 recommended: 114 | 2026-07-26T00:20:49+00:00 | Vulnerability · Source |
| CVE-2018-7182 | suse_vex | SUSE CVE CVE-2018-7182 | known affected: 27 known not affected: 20 recommended: 106 | 2026-07-26T00:20:48+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-7187 | suse_vex | SUSE CVE CVE-2018-7187 | recommended: 519 | 2026-07-26T00:20:45+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-7321 | suse_vex | SUSE CVE CVE-2018-7321 | known affected: 1 known not affected: 115 recommended: 589 | 2026-07-26T00:20:42+00:00 | Vulnerability · Source |
| 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-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-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-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-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-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-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-8107 | suse_vex | SUSE CVE CVE-2018-8107 | known not affected: 381 | 2026-07-26T00:20:07+00:00 | Vulnerability · Source |