VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-15680 | suse_vex | SUSE CVE CVE-2020-15680 | known affected: 56 recommended: 9 | 2026-07-23T02:45:24+00:00 | Vulnerability · Source |
| CVE-2020-15810 | suse_vex | SUSE CVE CVE-2020-15810 | known affected: 394 known not affected: 24 recommended: 84 | 2026-07-23T02:45:22+00:00 | Vulnerability · Source |
| CVE-2020-15852 | suse_vex | SUSE CVE CVE-2020-15852 | known not affected: 541 | 2026-07-23T02:45:21+00:00 | Vulnerability · Source |
| CVE-2020-15861 | suse_vex | SUSE CVE CVE-2020-15861 | known not affected: 203 | 2026-07-23T02:45:19+00:00 | Vulnerability · Source |
| CVE-2020-15889 | suse_vex | SUSE CVE CVE-2020-15889 | known not affected: 492 | 2026-07-23T02:45:18+00:00 | Vulnerability · Source |
| CVE-2020-16309 | suse_vex | SUSE CVE CVE-2020-16309 | known not affected: 172 recommended: 8 | 2026-07-23T02:45:15+00:00 | Vulnerability · Source |
| CVE-2020-16587 | suse_vex | SUSE CVE CVE-2020-16587 | known affected: 21 recommended: 202 | 2026-07-23T02:45:14+00:00 | Vulnerability · Source |
| CVE-2020-17538 | suse_vex | SUSE CVE CVE-2020-17538 | known not affected: 172 recommended: 8 | 2026-07-23T02:45:12+00:00 | Vulnerability · Source |
| CVE-2020-18768 | suse_vex | SUSE CVE CVE-2020-18768 | known affected: 516 recommended: 99 | 2026-07-23T02:45:11+00:00 | Vulnerability · Source |
| CVE-2020-18839 | suse_vex | SUSE CVE CVE-2020-18839 | known not affected: 526 | 2026-07-23T02:45:09+00:00 | Vulnerability · Source |
| CVE-2020-19909 | suse_vex | SUSE CVE CVE-2020-19909 | recommended: 6 | 2026-07-23T02:45:08+00:00 | Vulnerability · Source |
| CVE-2020-22218 | suse_vex | SUSE CVE CVE-2020-22218 | known affected: 442 known not affected: 215 recommended: 132 | 2026-07-23T02:45:06+00:00 | Vulnerability · Source |
| CVE-2020-22219 | suse_vex | SUSE CVE CVE-2020-22219 | known affected: 80 known not affected: 68 recommended: 121 | 2026-07-23T02:45:05+00:00 | Vulnerability · Source |
| CVE-2020-23804 | suse_vex | SUSE CVE CVE-2020-23804 | known affected: 78 known not affected: 133 recommended: 181 | 2026-07-23T02:45:03+00:00 | Vulnerability · Source |
| CVE-2020-24394 | suse_vex | SUSE CVE CVE-2020-24394 | known affected: 105 known not affected: 325 recommended: 574 | 2026-07-23T02:45:02+00:00 | Vulnerability · Source |
| CVE-2020-24741 | suse_vex | SUSE CVE CVE-2020-24741 | known affected: 394 known not affected: 1012 recommended: 474 | 2026-07-23T02:45:00+00:00 | Vulnerability · Source |
| CVE-2020-25285 | suse_vex | SUSE CVE CVE-2020-25285 | known affected: 416 known not affected: 122 recommended: 1597 | 2026-07-23T02:44:55+00:00 | Vulnerability · Source |
| CVE-2020-25604 | suse_vex | SUSE CVE CVE-2020-25604 | known affected: 320 known not affected: 81 recommended: 532 | 2026-07-23T02:44:53+00:00 | Vulnerability · Source |
| CVE-2020-25613 | suse_vex | SUSE CVE CVE-2020-25613 | known affected: 300 known not affected: 6 recommended: 498 | 2026-07-23T02:44:52+00:00 | Vulnerability · Source |
| CVE-2020-25625 | suse_vex | SUSE CVE CVE-2020-25625 | known affected: 388 known not affected: 587 recommended: 850 | 2026-07-23T02:44:51+00:00 | Vulnerability · Source |
| CVE-2020-25682 | suse_vex | SUSE CVE CVE-2020-25682 | recommended: 109 | 2026-07-23T02:44:49+00:00 | Vulnerability · Source |
| CVE-2020-26139 | suse_vex | SUSE CVE CVE-2020-26139 | known affected: 318 known not affected: 126 recommended: 1569 | 2026-07-23T02:44:43+00:00 | Vulnerability · Source |
| CVE-2020-26140 | suse_vex | SUSE CVE CVE-2020-26140 | known affected: 22 known not affected: 165 recommended: 20 | 2026-07-23T02:44:41+00:00 | Vulnerability · Source |
| CVE-2020-26144 | suse_vex | SUSE CVE CVE-2020-26144 | known affected: 22 known not affected: 165 recommended: 20 | 2026-07-23T02:44:38+00:00 | Vulnerability · Source |
| CVE-2020-26967 | suse_vex | SUSE CVE CVE-2020-26967 | known affected: 59 recommended: 9 | 2026-07-23T02:44:33+00:00 | Vulnerability · Source |
| CVE-2020-26969 | suse_vex | SUSE CVE CVE-2020-26969 | known affected: 59 recommended: 9 | 2026-07-23T02:44:31+00:00 | Vulnerability · Source |
| CVE-2020-27661 | suse_vex | SUSE CVE CVE-2020-27661 | known not affected: 1102 | 2026-07-23T02:44:29+00:00 | Vulnerability · Source |
| CVE-2020-27673 | suse_vex | SUSE CVE CVE-2020-27673 | known affected: 410 known not affected: 23 recommended: 1551 | 2026-07-23T02:44:27+00:00 | Vulnerability · Source |
| CVE-2020-27750 | suse_vex | SUSE CVE CVE-2020-27750 | known not affected: 4 recommended: 778 | 2026-07-23T02:44:26+00:00 | Vulnerability · Source |
| CVE-2020-27753 | suse_vex | SUSE CVE CVE-2020-27753 | recommended: 769 | 2026-07-23T02:44:24+00:00 | Vulnerability · Source |
| CVE-2020-27765 | suse_vex | SUSE CVE CVE-2020-27765 | recommended: 785 | 2026-07-23T02:44:23+00:00 | Vulnerability · Source |
| CVE-2020-28097 | suse_vex | SUSE CVE CVE-2020-28097 | known affected: 419 known not affected: 56 recommended: 483 | 2026-07-23T02:44:18+00:00 | Vulnerability · Source |
| CVE-2020-29040 | suse_vex | SUSE CVE CVE-2020-29040 | known affected: 320 known not affected: 57 recommended: 236 | 2026-07-23T02:44:16+00:00 | Vulnerability · Source |
| CVE-2020-29373 | suse_vex | SUSE CVE CVE-2020-29373 | known affected: 322 known not affected: 283 recommended: 1065 | 2026-07-23T02:44:14+00:00 | Vulnerability · Source |
| CVE-2020-29480 | suse_vex | SUSE CVE CVE-2020-29480 | known affected: 399 known not affected: 75 recommended: 559 | 2026-07-23T02:44:13+00:00 | Vulnerability · Source |
| CVE-2020-29487 | suse_vex | SUSE CVE CVE-2020-29487 | known not affected: 334 | 2026-07-23T02:44:11+00:00 | Vulnerability · Source |
| CVE-2020-29567 | suse_vex | SUSE CVE CVE-2020-29567 | known affected: 320 known not affected: 217 recommended: 229 | 2026-07-23T02:44:10+00:00 | Vulnerability · Source |
| CVE-2020-35342 | suse_vex | SUSE CVE CVE-2020-35342 | known affected: 1 known not affected: 233 | 2026-07-23T02:44:08+00:00 | Vulnerability · Source |
| CVE-2020-35508 | suse_vex | SUSE CVE CVE-2020-35508 | known not affected: 409 recommended: 20 | 2026-07-23T02:44:07+00:00 | Vulnerability · Source |
| CVE-2020-36778 | suse_vex | SUSE CVE CVE-2020-36778 | known not affected: 267 | 2026-07-23T02:44:05+00:00 | Vulnerability · Source |
| CVE-2021-0183 | suse_vex | SUSE CVE CVE-2021-0183 | known not affected: 71 recommended: 130 | 2026-07-23T02:44:00+00:00 | Vulnerability · Source |
| CVE-2021-0342 | suse_vex | SUSE CVE CVE-2021-0342 | known affected: 353 known not affected: 333 recommended: 1203 | 2026-07-23T02:43:58+00:00 | Vulnerability · Source |
| CVE-2021-0605 | suse_vex | SUSE CVE CVE-2021-0605 | known affected: 299 known not affected: 88 recommended: 1533 | 2026-07-23T02:43:56+00:00 | Vulnerability · Source |
| CVE-2021-0929 | suse_vex | SUSE CVE CVE-2021-0929 | known not affected: 365 | 2026-07-23T02:43:54+00:00 | Vulnerability · Source |
| CVE-2021-1405 | suse_vex | SUSE CVE CVE-2021-1405 | recommended: 282 | 2026-07-23T02:43:52+00:00 | Vulnerability · Source |
| CVE-2021-1825 | suse_vex | SUSE CVE CVE-2021-1825 | known affected: 1 known not affected: 117 recommended: 937 | 2026-07-23T02:43:51+00:00 | Vulnerability · Source |
| CVE-2021-2154 | suse_vex | SUSE CVE CVE-2021-2154 | known affected: 31 known not affected: 42 recommended: 457 | 2026-07-23T02:43:50+00:00 | Vulnerability · Source |
| CVE-2021-3475 | suse_vex | SUSE CVE CVE-2021-3475 | recommended: 172 | 2026-07-23T02:43:43+00:00 | Vulnerability · Source |
| CVE-2021-3490 | suse_vex | SUSE CVE CVE-2021-3490 | known affected: 322 known not affected: 324 recommended: 763 | 2026-07-23T02:43:42+00:00 | Vulnerability · Source |
| CVE-2021-3501 | suse_vex | SUSE CVE CVE-2021-3501 | known not affected: 320 recommended: 20 | 2026-07-23T02:43:40+00:00 | Vulnerability · Source |