VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292089 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-16889 | suse_vex | SUSE CVE CVE-2018-16889 | known not affected: 349 recommended: 1158 | 2026-07-25T18:12:48+00:00 | Vulnerability · Source |
| CVE-2018-17095 | suse_vex | SUSE CVE CVE-2018-17095 | known affected: 44 known not affected: 15 recommended: 201 | 2026-07-25T18:12:46+00:00 | Vulnerability · Source |
| CVE-2018-17199 | suse_vex | SUSE CVE CVE-2018-17199 | known affected: 111 known not affected: 40 recommended: 190 | 2026-07-25T18:12:45+00:00 | Vulnerability · Source |
| CVE-2018-17294 | suse_vex | SUSE CVE CVE-2018-17294 | known affected: 52 known not affected: 128 recommended: 105 | 2026-07-25T18:12:42+00:00 | Vulnerability · Source |
| CVE-2018-17358 | suse_vex | SUSE CVE CVE-2018-17358 | known affected: 447 known not affected: 40 recommended: 485 | 2026-07-25T18:12:40+00:00 | Vulnerability · Source |
| CVE-2018-17360 | suse_vex | SUSE CVE CVE-2018-17360 | known affected: 394 recommended: 485 | 2026-07-25T18:12:37+00:00 | Vulnerability · Source |
| CVE-2018-17407 | suse_vex | SUSE CVE CVE-2018-17407 | known affected: 30 known not affected: 72 recommended: 13119 | 2026-07-25T18:12:33+00:00 | Vulnerability · Source |
| CVE-2018-17967 | suse_vex | SUSE CVE CVE-2018-17967 | known not affected: 176 recommended: 17 | 2026-07-25T18:12:31+00:00 | Vulnerability · Source |
| CVE-2018-18025 | suse_vex | SUSE CVE CVE-2018-18025 | known not affected: 176 | 2026-07-25T18:12:30+00:00 | Vulnerability · Source |
| CVE-2018-18065 | suse_vex | SUSE CVE CVE-2018-18065 | known affected: 394 known not affected: 127 recommended: 476 | 2026-07-25T18:12:28+00:00 | Vulnerability · Source |
| CVE-2018-18227 | suse_vex | SUSE CVE CVE-2018-18227 | known not affected: 266 recommended: 988 | 2026-07-25T18:12:27+00:00 | Vulnerability · Source |
| CVE-2018-18281 | suse_vex | SUSE CVE CVE-2018-18281 | known affected: 74 known not affected: 57 recommended: 781 | 2026-07-25T18:12:25+00:00 | Vulnerability · Source |
| CVE-2018-18284 | suse_vex | SUSE CVE CVE-2018-18284 | known affected: 17 known not affected: 87 recommended: 403 | 2026-07-25T18:12:24+00:00 | Vulnerability · Source |
| CVE-2018-18314 | suse_vex | SUSE CVE CVE-2018-18314 | known affected: 340 known not affected: 166 recommended: 357 | 2026-07-25T18:12:20+00:00 | Vulnerability · Source |
| CVE-2018-18386 | suse_vex | SUSE CVE CVE-2018-18386 | known affected: 86 known not affected: 163 recommended: 830 | 2026-07-25T18:12:17+00:00 | Vulnerability · Source |
| CVE-2018-18454 | suse_vex | SUSE CVE CVE-2018-18454 | recommended: 41 | 2026-07-25T18:12:15+00:00 | Vulnerability · Source |
| CVE-2018-18483 | suse_vex | SUSE CVE CVE-2018-18483 | known affected: 447 recommended: 485 | 2026-07-25T18:12:14+00:00 | Vulnerability · Source |
| CVE-2018-18492 | suse_vex | SUSE CVE CVE-2018-18492 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:12+00:00 | Vulnerability · Source |
| CVE-2018-18493 | suse_vex | SUSE CVE CVE-2018-18493 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:10+00:00 | Vulnerability · Source |
| CVE-2018-18494 | suse_vex | SUSE CVE CVE-2018-18494 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:09+00:00 | Vulnerability · Source |
| CVE-2018-18498 | suse_vex | SUSE CVE CVE-2018-18498 | known affected: 20 known not affected: 168 recommended: 1231 | 2026-07-25T18:12:07+00:00 | Vulnerability · Source |
| CVE-2018-18505 | suse_vex | SUSE CVE CVE-2018-18505 | known not affected: 154 recommended: 1193 | 2026-07-25T18:12:03+00:00 | Vulnerability · Source |
| CVE-2018-18584 | suse_vex | SUSE CVE CVE-2018-18584 | known affected: 48 recommended: 157 | 2026-07-25T18:11:59+00:00 | Vulnerability · Source |
| CVE-2018-18586 | suse_vex | SUSE CVE CVE-2018-18586 | known affected: 50 known not affected: 63 recommended: 95 | 2026-07-25T18:11:58+00:00 | Vulnerability · Source |
| CVE-2018-18690 | suse_vex | SUSE CVE CVE-2018-18690 | known affected: 15 known not affected: 191 recommended: 239 | 2026-07-25T18:11:56+00:00 | Vulnerability · Source |
| CVE-2018-18883 | suse_vex | SUSE CVE CVE-2018-18883 | known affected: 375 known not affected: 90 recommended: 431 | 2026-07-25T18:11:55+00:00 | Vulnerability · Source |
| CVE-2018-19058 | suse_vex | SUSE CVE CVE-2018-19058 | known affected: 26 known not affected: 324 recommended: 170 | 2026-07-25T18:11:53+00:00 | Vulnerability · Source |
| CVE-2018-19059 | suse_vex | SUSE CVE CVE-2018-19059 | known affected: 26 known not affected: 324 recommended: 170 | 2026-07-25T18:11:52+00:00 | Vulnerability · Source |
| CVE-2018-19139 | suse_vex | SUSE CVE CVE-2018-19139 | known affected: 44 known not affected: 19 recommended: 154 | 2026-07-25T18:11:48+00:00 | Vulnerability · Source |
| CVE-2018-19184 | suse_vex | SUSE CVE CVE-2018-19184 | recommended: 3 | 2026-07-25T18:11:45+00:00 | Vulnerability · Source |
| CVE-2018-19362 | suse_vex | SUSE CVE CVE-2018-19362 | recommended: 45 | 2026-07-25T18:11:42+00:00 | Vulnerability · Source |
| CVE-2018-19416 | suse_vex | SUSE CVE CVE-2018-19416 | known affected: 405 known not affected: 8 recommended: 137 | 2026-07-25T18:11:41+00:00 | Vulnerability · Source |
| CVE-2018-19432 | suse_vex | SUSE CVE CVE-2018-19432 | known affected: 410 recommended: 178 | 2026-07-25T18:11:39+00:00 | Vulnerability · Source |
| CVE-2018-19477 | suse_vex | SUSE CVE CVE-2018-19477 | known affected: 17 known not affected: 87 recommended: 403 | 2026-07-25T18:11:38+00:00 | Vulnerability · Source |
| CVE-2018-19478 | suse_vex | SUSE CVE CVE-2018-19478 | known affected: 6 known not affected: 199 | 2026-07-25T18:11:37+00:00 | Vulnerability · Source |
| CVE-2018-19492 | suse_vex | SUSE CVE CVE-2018-19492 | known affected: 118 known not affected: 2 recommended: 91 | 2026-07-25T18:11:35+00:00 | Vulnerability · Source |
| CVE-2018-19626 | suse_vex | SUSE CVE CVE-2018-19626 | known affected: 111 known not affected: 37 recommended: 922 | 2026-07-25T18:11:29+00:00 | Vulnerability · Source |
| CVE-2018-19628 | suse_vex | SUSE CVE CVE-2018-19628 | known not affected: 170 recommended: 677 | 2026-07-25T18:11:26+00:00 | Vulnerability · Source |
| CVE-2018-19639 | suse_vex | SUSE CVE CVE-2018-19639 | known affected: 320 recommended: 185 | 2026-07-25T18:11:23+00:00 | Vulnerability · Source |
| CVE-2018-19662 | suse_vex | SUSE CVE CVE-2018-19662 | known not affected: 84 recommended: 7 | 2026-07-25T18:11:22+00:00 | Vulnerability · Source |
| CVE-2018-19788 | suse_vex | SUSE CVE CVE-2018-19788 | known affected: 415 known not affected: 52 recommended: 400 | 2026-07-25T18:11:17+00:00 | Vulnerability · Source |
| CVE-2018-19854 | suse_vex | SUSE CVE CVE-2018-19854 | known affected: 57 known not affected: 351 recommended: 437 | 2026-07-25T18:11:16+00:00 | Vulnerability · Source |
| CVE-2018-19876 | suse_vex | SUSE CVE CVE-2018-19876 | known not affected: 149 | 2026-07-25T18:11:13+00:00 | Vulnerability · Source |
| CVE-2018-19961 | suse_vex | SUSE CVE CVE-2018-19961 | known affected: 388 known not affected: 32 recommended: 539 | 2026-07-25T18:11:09+00:00 | Vulnerability · Source |
| CVE-2018-19965 | suse_vex | SUSE CVE CVE-2018-19965 | known affected: 388 known not affected: 84 recommended: 531 | 2026-07-25T18:11:07+00:00 | Vulnerability · Source |
| CVE-2018-20097 | suse_vex | SUSE CVE CVE-2018-20097 | known affected: 38 known not affected: 3 recommended: 114 | 2026-07-25T18:11:01+00:00 | Vulnerability · Source |
| CVE-2018-20106 | suse_vex | SUSE CVE CVE-2018-20106 | known affected: 3 known not affected: 47 | 2026-07-25T18:10:59+00:00 | Vulnerability · Source |
| CVE-2018-20125 | suse_vex | SUSE CVE CVE-2018-20125 | known affected: 394 known not affected: 544 recommended: 1486 | 2026-07-25T18:10:56+00:00 | Vulnerability · Source |
| CVE-2018-20126 | suse_vex | SUSE CVE CVE-2018-20126 | known affected: 486 known not affected: 450 recommended: 1725 | 2026-07-25T18:10:55+00:00 | Vulnerability · Source |
| CVE-2018-20169 | suse_vex | SUSE CVE CVE-2018-20169 | known affected: 66 known not affected: 194 recommended: 806 | 2026-07-25T18:10:53+00:00 | Vulnerability · Source |