VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294121 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-18511 | suse_vex | SUSE CVE CVE-2018-18511 | known not affected: 70 recommended: 104 | 2026-07-28T00:03:20+00:00 | Vulnerability · Source |
| CVE-2018-19406 | suse_vex | SUSE CVE CVE-2018-19406 | known not affected: 132 | 2026-07-28T00:03:16+00:00 | Vulnerability · Source |
| CVE-2018-20839 | suse_vex | SUSE CVE CVE-2018-20839 | known affected: 11 known not affected: 186 | 2026-07-28T00:03:07+00:00 | Vulnerability · Source |
| CVE-2018-25018 | suse_vex | SUSE CVE CVE-2018-25018 | known not affected: 21 | 2026-07-28T00:03:04+00:00 | Vulnerability · Source |
| CVE-2018-1000077 | suse_vex | SUSE CVE CVE-2018-1000077 | known affected: 323 known not affected: 68 recommended: 478 | 2026-07-28T00:02:59+00:00 | Vulnerability · Source |
| CVE-2019-2529 | suse_vex | SUSE CVE CVE-2019-2529 | known affected: 53 known not affected: 173 recommended: 134 | 2026-07-28T00:02:48+00:00 | Vulnerability · Source |
| CVE-2019-2816 | suse_vex | SUSE CVE CVE-2019-2816 | known affected: 402 known not affected: 6 recommended: 1106 | 2026-07-28T00:02:43+00:00 | Vulnerability · Source |
| CVE-2019-2922 | suse_vex | SUSE CVE CVE-2019-2922 | known affected: 7 known not affected: 98 | 2026-07-28T00:02:40+00:00 | Vulnerability · Source |
| CVE-2019-2945 | suse_vex | SUSE CVE CVE-2019-2945 | known affected: 482 recommended: 1067 | 2026-07-28T00:02:37+00:00 | Vulnerability · Source |
| CVE-2019-2950 | suse_vex | SUSE CVE CVE-2019-2950 | known affected: 7 known not affected: 98 recommended: 10 | 2026-07-28T00:02:36+00:00 | Vulnerability · Source |
| CVE-2019-3009 | suse_vex | SUSE CVE CVE-2019-3009 | known affected: 7 known not affected: 98 recommended: 10 | 2026-07-28T00:02:34+00:00 | Vulnerability · Source |
| CVE-2019-3835 | suse_vex | SUSE CVE CVE-2019-3835 | known affected: 33 recommended: 269 | 2026-07-28T00:02:31+00:00 | Vulnerability · Source |
| CVE-2019-3901 | suse_vex | SUSE CVE CVE-2019-3901 | known not affected: 232 recommended: 13 | 2026-07-28T00:02:26+00:00 | Vulnerability · Source |
| CVE-2019-6488 | suse_vex | SUSE CVE CVE-2019-6488 | known not affected: 245 | 2026-07-28T00:02:18+00:00 | Vulnerability · Source |
| CVE-2019-6501 | suse_vex | SUSE CVE CVE-2019-6501 | known not affected: 301 | 2026-07-28T00:02:17+00:00 | Vulnerability · Source |
| CVE-2019-7282 | suse_vex | SUSE CVE CVE-2019-7282 | known affected: 4 | 2026-07-28T00:02:15+00:00 | Vulnerability · Source |
| CVE-2019-8622 | suse_vex | SUSE CVE CVE-2019-8622 | known affected: 112 known not affected: 82 recommended: 288 | 2026-07-28T00:02:07+00:00 | Vulnerability · Source |
| CVE-2019-8816 | suse_vex | SUSE CVE CVE-2019-8816 | known not affected: 10 recommended: 1075 | 2026-07-28T00:02:00+00:00 | Vulnerability · Source |
| CVE-2019-9641 | suse_vex | SUSE CVE CVE-2019-9641 | known not affected: 1681 recommended: 3868 | 2026-07-28T00:01:49+00:00 | Vulnerability · Source |
| CVE-2019-10143 | suse_vex | SUSE CVE CVE-2019-10143 | known affected: 23 known not affected: 112 recommended: 36 | 2026-07-28T00:01:42+00:00 | Vulnerability · Source |
| CVE-2019-11010 | suse_vex | SUSE CVE CVE-2019-11010 | known affected: 10 known not affected: 350 recommended: 16 | 2026-07-28T00:01:35+00:00 | Vulnerability · Source |
| CVE-2019-11683 | suse_vex | SUSE CVE CVE-2019-11683 | known not affected: 406 | 2026-07-28T00:01:27+00:00 | Vulnerability · Source |
| CVE-2019-11734 | suse_vex | SUSE CVE CVE-2019-11734 | known not affected: 79 recommended: 9 | 2026-07-28T00:01:23+00:00 | Vulnerability · Source |
| CVE-2019-12381 | suse_vex | SUSE CVE CVE-2019-12381 | known not affected: 167 | 2026-07-28T00:01:16+00:00 | Vulnerability · Source |
| CVE-2019-12418 | suse_vex | SUSE CVE CVE-2019-12418 | known affected: 513 known not affected: 112 recommended: 382 | 2026-07-28T00:01:15+00:00 | Vulnerability · Source |
| CVE-2019-14203 | suse_vex | SUSE CVE CVE-2019-14203 | known affected: 16 recommended: 40 | 2026-07-28T00:01:06+00:00 | Vulnerability · Source |
| CVE-2019-14369 | suse_vex | SUSE CVE CVE-2019-14369 | known not affected: 79 | 2026-07-28T00:01:04+00:00 | Vulnerability · Source |
| CVE-2019-14814 | suse_vex | SUSE CVE CVE-2019-14814 | known affected: 410 known not affected: 74 recommended: 1601 | 2026-07-28T00:01:00+00:00 | Vulnerability · Source |
| CVE-2019-15213 | suse_vex | SUSE CVE CVE-2019-15213 | known affected: 100 known not affected: 61 recommended: 673 | 2026-07-28T00:00:50+00:00 | Vulnerability · Source |
| CVE-2019-15223 | suse_vex | SUSE CVE CVE-2019-15223 | known not affected: 174 recommended: 20 | 2026-07-28T00:00:49+00:00 | Vulnerability · Source |
| CVE-2019-15922 | suse_vex | SUSE CVE CVE-2019-15922 | known not affected: 326 | 2026-07-28T00:00:45+00:00 | Vulnerability · Source |
| CVE-2019-17042 | suse_vex | SUSE CVE CVE-2019-17042 | known affected: 473 known not affected: 237 recommended: 325 | 2026-07-28T00:00:34+00:00 | Vulnerability · Source |
| CVE-2019-17346 | suse_vex | SUSE CVE CVE-2019-17346 | known affected: 18 known not affected: 154 recommended: 175 | 2026-07-28T00:00:32+00:00 | Vulnerability · Source |
| CVE-2019-18422 | suse_vex | SUSE CVE CVE-2019-18422 | known not affected: 23 recommended: 167 | 2026-07-28T00:00:26+00:00 | Vulnerability · Source |
| CVE-2019-19037 | suse_vex | SUSE CVE CVE-2019-19037 | known affected: 310 known not affected: 297 recommended: 781 | 2026-07-28T00:00:23+00:00 | Vulnerability · Source |
| CVE-2019-19073 | suse_vex | SUSE CVE CVE-2019-19073 | known affected: 416 known not affected: 53 recommended: 1501 | 2026-07-28T00:00:20+00:00 | Vulnerability · Source |
| CVE-2019-19081 | suse_vex | SUSE CVE CVE-2019-19081 | known affected: 330 known not affected: 266 recommended: 1130 | 2026-07-28T00:00:16+00:00 | Vulnerability · Source |
| CVE-2019-19318 | suse_vex | SUSE CVE CVE-2019-19318 | known affected: 78 known not affected: 67 recommended: 473 | 2026-07-28T00:00:14+00:00 | Vulnerability · Source |
| CVE-2019-19555 | suse_vex | SUSE CVE CVE-2019-19555 | known affected: 3 recommended: 43 | 2026-07-28T00:00:13+00:00 | Vulnerability · Source |
| CVE-2019-19578 | suse_vex | SUSE CVE CVE-2019-19578 | recommended: 234 | 2026-07-28T00:00:11+00:00 | Vulnerability · Source |
| CVE-2020-0423 | suse_vex | SUSE CVE CVE-2020-0423 | known not affected: 273 | 2026-07-27T23:59:52+00:00 | Vulnerability · Source |
| CVE-2020-15704 | suse_vex | SUSE CVE CVE-2020-15704 | known not affected: 71 | 2026-07-27T23:58:43+00:00 | Vulnerability · Source |
| CVE-2020-16126 | suse_vex | SUSE CVE CVE-2020-16126 | known not affected: 212 | 2026-07-27T23:58:34+00:00 | Vulnerability · Source |
| CVE-2020-21675 | suse_vex | SUSE CVE CVE-2020-21675 | known not affected: 25 | 2026-07-27T23:58:21+00:00 | Vulnerability · Source |
| CVE-2020-21682 | suse_vex | SUSE CVE CVE-2020-21682 | recommended: 43 | 2026-07-27T23:58:19+00:00 | Vulnerability · Source |
| CVE-2020-24659 | suse_vex | SUSE CVE CVE-2020-24659 | known affected: 308 known not affected: 60 recommended: 487 | 2026-07-27T23:58:17+00:00 | Vulnerability · Source |
| CVE-2020-25602 | suse_vex | SUSE CVE CVE-2020-25602 | known affected: 308 known not affected: 101 recommended: 375 | 2026-07-27T23:58:11+00:00 | Vulnerability · Source |
| CVE-2020-27769 | suse_vex | SUSE CVE CVE-2020-27769 | recommended: 753 | 2026-07-27T23:57:56+00:00 | Vulnerability · Source |
| CVE-2020-29479 | suse_vex | SUSE CVE CVE-2020-29479 | known not affected: 229 | 2026-07-27T23:57:44+00:00 | Vulnerability · Source |
| CVE-2020-35501 | suse_vex | SUSE CVE CVE-2020-35501 | known not affected: 292 | 2026-07-27T23:57:38+00:00 | Vulnerability · Source |