VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-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-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-19876 | suse_vex | SUSE CVE CVE-2018-19876 | known not affected: 149 | 2026-07-25T18:11:13+00:00 | Vulnerability · Source |
| CVE-2018-20185 | suse_vex | SUSE CVE CVE-2018-20185 | known affected: 3 known not affected: 205 recommended: 14 | 2026-07-25T18:10:51+00:00 | Vulnerability · Source |
| CVE-2018-20509 | suse_vex | SUSE CVE CVE-2018-20509 | known not affected: 127 | 2026-07-25T18:10:44+00:00 | Vulnerability · Source |
| CVE-2018-20510 | suse_vex | SUSE CVE CVE-2018-20510 | known not affected: 134 | 2026-07-25T18:10:43+00:00 | Vulnerability · Source |
| CVE-2018-20511 | suse_vex | SUSE CVE CVE-2018-20511 | known not affected: 563 | 2026-07-25T18:10:42+00:00 | Vulnerability · Source |
| CVE-2018-20584 | suse_vex | SUSE CVE CVE-2018-20584 | known not affected: 89 | 2026-07-25T18:10:37+00:00 | Vulnerability · Source |
| CVE-2018-20650 | suse_vex | SUSE CVE CVE-2018-20650 | known affected: 26 known not affected: 324 recommended: 179 | 2026-07-25T18:10:36+00:00 | Vulnerability · Source |
| CVE-2018-20712 | suse_vex | SUSE CVE CVE-2018-20712 | known not affected: 318 | 2026-07-25T18:10:29+00:00 | Vulnerability · Source |
| CVE-2018-20852 | suse_vex | SUSE CVE CVE-2018-20852 | known affected: 459 recommended: 1884 | 2026-07-25T18:10:17+00:00 | Vulnerability · Source |
| CVE-2018-21035 | suse_vex | SUSE CVE CVE-2018-21035 | recommended: 26 | 2026-07-25T18:10:12+00:00 | Vulnerability · Source |
| CVE-2018-21232 | suse_vex | SUSE CVE CVE-2018-21232 | recommended: 29 | 2026-07-25T18:10:11+00:00 | Vulnerability · Source |
| CVE-2018-21247 | suse_vex | SUSE CVE CVE-2018-21247 | known affected: 24 known not affected: 3 recommended: 117 | 2026-07-25T18:10:10+00:00 | Vulnerability · Source |
| CVE-2018-25013 | suse_vex | SUSE CVE CVE-2018-25013 | known affected: 395 known not affected: 55 recommended: 227 | 2026-07-25T18:10:08+00:00 | Vulnerability · Source |
| CVE-2018-25015 | suse_vex | SUSE CVE CVE-2018-25015 | known not affected: 320 | 2026-07-25T18:10:07+00:00 | Vulnerability · Source |
| CVE-2018-25091 | suse_vex | SUSE CVE CVE-2018-25091 | known not affected: 147 recommended: 38 | 2026-07-25T18:10:06+00:00 | Vulnerability · Source |
| CVE-2018-1000028 | suse_vex | SUSE CVE CVE-2018-1000028 | known not affected: 142 recommended: 293 | 2026-07-25T18:10:01+00:00 | Vulnerability · Source |
| CVE-2018-1000032 | suse_vex | SUSE CVE CVE-2018-1000032 | known not affected: 14 | 2026-07-25T18:10:00+00:00 | Vulnerability · Source |
| CVE-2018-1000034 | suse_vex | SUSE CVE CVE-2018-1000034 | known not affected: 14 | 2026-07-25T18:09:58+00:00 | Vulnerability · Source |
| CVE-2018-1000035 | suse_vex | SUSE CVE CVE-2018-1000035 | known affected: 397 known not affected: 30 recommended: 92 | 2026-07-25T18:09:57+00:00 | Vulnerability · Source |
| CVE-2018-1000041 | suse_vex | SUSE CVE CVE-2018-1000041 | recommended: 72 | 2026-07-25T18:09:56+00:00 | Vulnerability · Source |
| CVE-2018-1000116 | suse_vex | SUSE CVE CVE-2018-1000116 | known affected: 2 known not affected: 52 | 2026-07-25T18:09:47+00:00 | Vulnerability · Source |
| CVE-2018-1000802 | suse_vex | SUSE CVE CVE-2018-1000802 | known affected: 438 known not affected: 2 recommended: 1387 | 2026-07-25T18:09:38+00:00 | Vulnerability · Source |
| CVE-2018-1000858 | suse_vex | SUSE CVE CVE-2018-1000858 | known affected: 331 known not affected: 40 recommended: 204 | 2026-07-25T18:09:34+00:00 | Vulnerability · Source |
| CVE-2019-0155 | suse_vex | SUSE CVE CVE-2019-0155 | known affected: 261 known not affected: 303 recommended: 1275 | 2026-07-25T18:09:28+00:00 | Vulnerability · Source |
| CVE-2019-0190 | suse_vex | SUSE CVE CVE-2019-0190 | known not affected: 138 | 2026-07-25T18:09:27+00:00 | Vulnerability · Source |
| CVE-2019-0215 | suse_vex | SUSE CVE CVE-2019-0215 | known not affected: 150 recommended: 11 | 2026-07-25T18:09:23+00:00 | Vulnerability · Source |
| CVE-2019-2011 | suse_vex | SUSE CVE CVE-2019-2011 | known not affected: 109 | 2026-07-25T18:09:04+00:00 | Vulnerability · Source |
| CVE-2019-2054 | suse_vex | SUSE CVE CVE-2019-2054 | known not affected: 413 | 2026-07-25T18:09:02+00:00 | Vulnerability · Source |
| CVE-2019-2214 | suse_vex | SUSE CVE CVE-2019-2214 | known not affected: 208 | 2026-07-25T18:08:59+00:00 | Vulnerability · Source |
| CVE-2019-2426 | suse_vex | SUSE CVE CVE-2019-2426 | known affected: 480 known not affected: 9 recommended: 814 | 2026-07-25T18:08:58+00:00 | Vulnerability · Source |
| CVE-2019-2481 | suse_vex | SUSE CVE CVE-2019-2481 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:56+00:00 | Vulnerability · Source |
| CVE-2019-2513 | suse_vex | SUSE CVE CVE-2019-2513 | known affected: 70 known not affected: 185 | 2026-07-25T18:08:54+00:00 | Vulnerability · Source |
| CVE-2019-2528 | suse_vex | SUSE CVE CVE-2019-2528 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:51+00:00 | Vulnerability · Source |
| CVE-2019-2533 | suse_vex | SUSE CVE CVE-2019-2533 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:50+00:00 | Vulnerability · Source |
| CVE-2019-2821 | suse_vex | SUSE CVE CVE-2019-2821 | known affected: 394 known not affected: 9 recommended: 316 | 2026-07-25T18:08:26+00:00 | Vulnerability · Source |
| CVE-2019-2911 | suse_vex | SUSE CVE CVE-2019-2911 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:24+00:00 | Vulnerability · Source |
| CVE-2019-2920 | suse_vex | SUSE CVE CVE-2019-2920 | known affected: 13 known not affected: 121 | 2026-07-25T18:08:23+00:00 | Vulnerability · Source |
| CVE-2019-2924 | suse_vex | SUSE CVE CVE-2019-2924 | known affected: 13 known not affected: 121 | 2026-07-25T18:08:22+00:00 | Vulnerability · Source |
| CVE-2019-2948 | suse_vex | SUSE CVE CVE-2019-2948 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:19+00:00 | Vulnerability · Source |
| CVE-2019-2960 | suse_vex | SUSE CVE CVE-2019-2960 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:14+00:00 | Vulnerability · Source |
| CVE-2019-2969 | suse_vex | SUSE CVE CVE-2019-2969 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:13+00:00 | Vulnerability · Source |
| CVE-2019-2991 | suse_vex | SUSE CVE CVE-2019-2991 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:10+00:00 | Vulnerability · Source |
| CVE-2019-2992 | suse_vex | SUSE CVE CVE-2019-2992 | known affected: 525 recommended: 1129 | 2026-07-25T18:08:08+00:00 | Vulnerability · Source |
| CVE-2019-2996 | suse_vex | SUSE CVE CVE-2019-2996 | known affected: 131 recommended: 295 | 2026-07-25T18:08:07+00:00 | Vulnerability · Source |
| CVE-2019-3693 | suse_vex | SUSE CVE CVE-2019-3693 | recommended: 31 | 2026-07-25T18:07:59+00:00 | Vulnerability · Source |