VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291942 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-17546 | suse_vex | SUSE CVE CVE-2019-17546 | known affected: 401 recommended: 277 | 2026-07-28T00:00:28+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-18804 | suse_vex | SUSE CVE CVE-2019-18804 | known affected: 20 known not affected: 27 recommended: 161 | 2026-07-28T00:00:25+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-19044 | suse_vex | SUSE CVE CVE-2019-19044 | known not affected: 297 recommended: 707 | 2026-07-28T00:00:22+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-19077 | suse_vex | SUSE CVE CVE-2019-19077 | known affected: 395 known not affected: 187 recommended: 1326 | 2026-07-28T00:00:18+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-2019-19579 | suse_vex | SUSE CVE CVE-2019-19579 | known affected: 68 known not affected: 163 recommended: 211 | 2026-07-28T00:00:10+00:00 | Vulnerability · Source |
| CVE-2019-19923 | suse_vex | SUSE CVE CVE-2019-19923 | known affected: 364 known not affected: 254 recommended: 441 | 2026-07-28T00:00:06+00:00 | Vulnerability · Source |
| CVE-2019-19977 | suse_vex | SUSE CVE CVE-2019-19977 | known affected: 3 recommended: 127 | 2026-07-28T00:00:05+00:00 | Vulnerability · Source |
| CVE-2019-20079 | suse_vex | SUSE CVE CVE-2019-20079 | known affected: 4 known not affected: 100 | 2026-07-28T00:00:03+00:00 | Vulnerability · Source |
| CVE-2019-20421 | suse_vex | SUSE CVE CVE-2019-20421 | known not affected: 8 recommended: 20 | 2026-07-28T00:00:02+00:00 | Vulnerability · Source |
| CVE-2019-20788 | suse_vex | SUSE CVE CVE-2019-20788 | known affected: 43 recommended: 114 | 2026-07-28T00:00:00+00:00 | Vulnerability · Source |
| CVE-2019-20839 | suse_vex | SUSE CVE CVE-2019-20839 | known affected: 22 known not affected: 3 recommended: 107 | 2026-07-27T23:59:59+00:00 | Vulnerability · Source |
| CVE-2019-1010006 | suse_vex | SUSE CVE CVE-2019-1010006 | known not affected: 172 recommended: 1138 | 2026-07-27T23:59:57+00:00 | Vulnerability · Source |
| CVE-2020-0182 | suse_vex | SUSE CVE CVE-2020-0182 | known not affected: 137 recommended: 5 | 2026-07-27T23:59:55+00:00 | Vulnerability · Source |
| CVE-2020-0305 | suse_vex | SUSE CVE CVE-2020-0305 | known affected: 422 known not affected: 9 recommended: 1612 | 2026-07-27T23:59:53+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-0548 | suse_vex | SUSE CVE CVE-2020-0548 | known affected: 14 known not affected: 35 recommended: 184 | 2026-07-27T23:59:50+00:00 | Vulnerability · Source |
| CVE-2020-2593 | suse_vex | SUSE CVE CVE-2020-2593 | known affected: 503 recommended: 1161 | 2026-07-27T23:59:47+00:00 | Vulnerability · Source |
| CVE-2020-2604 | suse_vex | SUSE CVE CVE-2020-2604 | known affected: 503 recommended: 1161 | 2026-07-27T23:59:45+00:00 | Vulnerability · Source |
| CVE-2020-2659 | suse_vex | SUSE CVE CVE-2020-2659 | known affected: 121 recommended: 845 | 2026-07-27T23:59:44+00:00 | Vulnerability · Source |
| CVE-2020-2756 | suse_vex | SUSE CVE CVE-2020-2756 | known affected: 412 recommended: 1120 | 2026-07-27T23:59:42+00:00 | Vulnerability · Source |
| CVE-2020-2767 | suse_vex | SUSE CVE CVE-2020-2767 | known affected: 422 recommended: 293 | 2026-07-27T23:59:40+00:00 | Vulnerability · Source |
| CVE-2020-2781 | suse_vex | SUSE CVE CVE-2020-2781 | known affected: 422 recommended: 1120 | 2026-07-27T23:59:39+00:00 | Vulnerability · Source |
| CVE-2020-3862 | suse_vex | SUSE CVE CVE-2020-3862 | known affected: 46 known not affected: 256 recommended: 1075 | 2026-07-27T23:59:34+00:00 | Vulnerability · Source |
| CVE-2020-8449 | suse_vex | SUSE CVE CVE-2020-8449 | known affected: 395 recommended: 68 | 2026-07-27T23:59:23+00:00 | Vulnerability · Source |
| CVE-2020-9383 | suse_vex | SUSE CVE CVE-2020-9383 | known affected: 427 known not affected: 200 recommended: 1443 | 2026-07-27T23:59:19+00:00 | Vulnerability · Source |
| CVE-2020-11741 | suse_vex | SUSE CVE CVE-2020-11741 | known affected: 63 known not affected: 80 recommended: 416 | 2026-07-27T23:59:10+00:00 | Vulnerability · Source |
| CVE-2020-11884 | suse_vex | SUSE CVE CVE-2020-11884 | known affected: 300 known not affected: 326 recommended: 801 | 2026-07-27T23:59:07+00:00 | Vulnerability · Source |
| CVE-2020-14562 | suse_vex | SUSE CVE CVE-2020-14562 | known affected: 515 recommended: 304 | 2026-07-27T23:58:58+00:00 | Vulnerability · Source |
| CVE-2020-14578 | suse_vex | SUSE CVE CVE-2020-14578 | known affected: 133 recommended: 870 | 2026-07-27T23:58:56+00:00 | Vulnerability · Source |
| CVE-2020-14776 | suse_vex | SUSE CVE CVE-2020-14776 | known not affected: 90 recommended: 624 | 2026-07-27T23:58:55+00:00 | Vulnerability · Source |
| CVE-2020-15358 | suse_vex | SUSE CVE CVE-2020-15358 | known affected: 367 known not affected: 268 recommended: 424 | 2026-07-27T23:58:53+00:00 | Vulnerability · Source |
| CVE-2020-15653 | suse_vex | SUSE CVE CVE-2020-15653 | known affected: 22 recommended: 443 | 2026-07-27T23:58:51+00:00 | Vulnerability · Source |
| CVE-2020-15674 | suse_vex | SUSE CVE CVE-2020-15674 | known affected: 3 known not affected: 148 recommended: 9 | 2026-07-27T23:58:44+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-15707 | suse_vex | SUSE CVE CVE-2020-15707 | known affected: 406 recommended: 833 | 2026-07-27T23:58:41+00:00 | Vulnerability · Source |
| CVE-2020-15801 | suse_vex | SUSE CVE CVE-2020-15801 | known not affected: 641 recommended: 246 | 2026-07-27T23:58:39+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-16590 | suse_vex | SUSE CVE CVE-2020-16590 | known affected: 395 known not affected: 83 recommended: 524 | 2026-07-27T23:58:31+00:00 | Vulnerability · Source |
| CVE-2020-19187 | suse_vex | SUSE CVE CVE-2020-19187 | known not affected: 525 | 2026-07-27T23:58:25+00:00 | Vulnerability · Source |
| CVE-2020-19188 | suse_vex | SUSE CVE CVE-2020-19188 | known not affected: 525 | 2026-07-27T23:58:22+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 |