VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283448 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-24994 | suse_vex | SUSE CVE CVE-2020-24994 | known affected: 6 recommended: 93 | 2026-07-25T17:49:27+00:00 | Vulnerability · Source |
| CVE-2020-25220 | suse_vex | SUSE CVE CVE-2020-25220 | known not affected: 250 | 2026-07-25T17:49:25+00:00 | Vulnerability · Source |
| CVE-2020-25412 | suse_vex | SUSE CVE CVE-2020-25412 | known not affected: 59 recommended: 23 | 2026-07-25T17:49:24+00:00 | Vulnerability · Source |
| CVE-2020-25596 | suse_vex | SUSE CVE CVE-2020-25596 | known affected: 431 known not affected: 3 recommended: 532 | 2026-07-25T17:49:22+00:00 | Vulnerability · Source |
| CVE-2020-25599 | suse_vex | SUSE CVE CVE-2020-25599 | known affected: 430 known not affected: 3 recommended: 509 | 2026-07-25T17:49:21+00:00 | Vulnerability · Source |
| CVE-2020-25632 | suse_vex | SUSE CVE CVE-2020-25632 | known affected: 293 recommended: 869 | 2026-07-25T17:49:19+00:00 | Vulnerability · Source |
| CVE-2020-25639 | suse_vex | SUSE CVE CVE-2020-25639 | known affected: 293 known not affected: 141 recommended: 1211 | 2026-07-25T17:49:18+00:00 | Vulnerability · Source |
| CVE-2020-25647 | suse_vex | SUSE CVE CVE-2020-25647 | known affected: 293 recommended: 869 | 2026-07-25T17:49:16+00:00 | Vulnerability · Source |
| CVE-2020-25648 | suse_vex | SUSE CVE CVE-2020-25648 | known affected: 326 recommended: 1592 | 2026-07-25T17:49:14+00:00 | Vulnerability · Source |
| CVE-2020-25652 | suse_vex | SUSE CVE CVE-2020-25652 | known affected: 13 recommended: 66 | 2026-07-25T17:49:13+00:00 | Vulnerability · Source |
| CVE-2020-25656 | suse_vex | SUSE CVE CVE-2020-25656 | known affected: 455 known not affected: 4 recommended: 1627 | 2026-07-25T17:49:11+00:00 | Vulnerability · Source |
| CVE-2020-25660 | suse_vex | SUSE CVE CVE-2020-25660 | known affected: 85 known not affected: 602 recommended: 1071 | 2026-07-25T17:49:10+00:00 | Vulnerability · Source |
| CVE-2020-25663 | suse_vex | SUSE CVE CVE-2020-25663 | known not affected: 338 | 2026-07-25T17:49:08+00:00 | Vulnerability · Source |
| CVE-2020-25664 | suse_vex | SUSE CVE CVE-2020-25664 | recommended: 769 | 2026-07-25T17:49:07+00:00 | Vulnerability · Source |
| CVE-2020-25665 | suse_vex | SUSE CVE CVE-2020-25665 | recommended: 766 | 2026-07-25T17:49:06+00:00 | Vulnerability · Source |
| CVE-2020-25666 | suse_vex | SUSE CVE CVE-2020-25666 | recommended: 785 | 2026-07-25T17:49:05+00:00 | Vulnerability · Source |
| CVE-2020-25673 | suse_vex | SUSE CVE CVE-2020-25673 | known affected: 300 known not affected: 88 recommended: 1531 | 2026-07-25T17:49:03+00:00 | Vulnerability · Source |
| CVE-2020-25675 | suse_vex | SUSE CVE CVE-2020-25675 | known not affected: 4 recommended: 762 | 2026-07-25T17:49:02+00:00 | Vulnerability · Source |
| CVE-2020-25676 | suse_vex | SUSE CVE CVE-2020-25676 | known not affected: 4 recommended: 762 | 2026-07-25T17:49:00+00:00 | Vulnerability · Source |
| CVE-2020-25681 | suse_vex | SUSE CVE CVE-2020-25681 | recommended: 111 | 2026-07-25T17:48:59+00:00 | Vulnerability · Source |
| CVE-2020-25696 | suse_vex | SUSE CVE CVE-2020-25696 | known affected: 394 known not affected: 898 recommended: 2080 | 2026-07-25T17:48:57+00:00 | Vulnerability · Source |
| CVE-2020-25707 | suse_vex | SUSE CVE CVE-2020-25707 | known affected: 1 recommended: 1887 | 2026-07-25T17:48:55+00:00 | Vulnerability · Source |
| CVE-2020-25708 | suse_vex | SUSE CVE CVE-2020-25708 | known affected: 40 recommended: 121 | 2026-07-25T17:48:54+00:00 | Vulnerability · Source |
| CVE-2020-25709 | suse_vex | SUSE CVE CVE-2020-25709 | known affected: 364 recommended: 597 | 2026-07-25T17:48:53+00:00 | Vulnerability · Source |
| CVE-2020-25710 | suse_vex | SUSE CVE CVE-2020-25710 | known affected: 72 recommended: 495 | 2026-07-25T17:48:51+00:00 | Vulnerability · Source |
| CVE-2020-25741 | suse_vex | SUSE CVE CVE-2020-25741 | known affected: 42 | 2026-07-25T17:48:50+00:00 | Vulnerability · Source |
| CVE-2020-25863 | suse_vex | SUSE CVE CVE-2020-25863 | known affected: 31 known not affected: 158 recommended: 342 | 2026-07-25T17:48:48+00:00 | Vulnerability · Source |
| CVE-2020-26088 | suse_vex | SUSE CVE CVE-2020-26088 | known affected: 455 known not affected: 25 recommended: 1519 | 2026-07-25T17:48:47+00:00 | Vulnerability · Source |
| CVE-2020-26137 | suse_vex | SUSE CVE CVE-2020-26137 | known affected: 326 known not affected: 40 recommended: 1335 | 2026-07-25T17:48:45+00:00 | Vulnerability · Source |
| CVE-2020-26143 | suse_vex | SUSE CVE CVE-2020-26143 | known affected: 22 known not affected: 165 recommended: 20 | 2026-07-25T17:48:44+00:00 | Vulnerability · Source |
| CVE-2020-26146 | suse_vex | SUSE CVE CVE-2020-26146 | known affected: 22 known not affected: 165 recommended: 20 | 2026-07-25T17:48:43+00:00 | Vulnerability · Source |
| CVE-2020-26154 | suse_vex | SUSE CVE CVE-2020-26154 | known affected: 336 known not affected: 4 recommended: 485 | 2026-07-25T17:48:41+00:00 | Vulnerability · Source |
| CVE-2020-26159 | suse_vex | SUSE CVE CVE-2020-26159 | known affected: 243 recommended: 274 | 2026-07-25T17:48:40+00:00 | Vulnerability · Source |
| CVE-2020-26418 | suse_vex | SUSE CVE CVE-2020-26418 | known not affected: 144 recommended: 650 | 2026-07-25T17:48:38+00:00 | Vulnerability · Source |
| CVE-2020-26419 | suse_vex | SUSE CVE CVE-2020-26419 | known not affected: 144 recommended: 650 | 2026-07-25T17:48:37+00:00 | Vulnerability · Source |
| CVE-2020-26422 | suse_vex | SUSE CVE CVE-2020-26422 | known not affected: 144 recommended: 650 | 2026-07-25T17:48:36+00:00 | Vulnerability · Source |
| CVE-2020-26557 | suse_vex | SUSE CVE CVE-2020-26557 | known not affected: 670 | 2026-07-25T17:48:34+00:00 | Vulnerability · Source |
| CVE-2020-26570 | suse_vex | SUSE CVE CVE-2020-26570 | known not affected: 27 recommended: 66 | 2026-07-25T17:48:33+00:00 | Vulnerability · Source |
| CVE-2020-26682 | suse_vex | SUSE CVE CVE-2020-26682 | known not affected: 54 recommended: 120 | 2026-07-25T17:48:32+00:00 | Vulnerability · Source |
| CVE-2020-26958 | suse_vex | SUSE CVE CVE-2020-26958 | known affected: 56 recommended: 405 | 2026-07-25T17:48:30+00:00 | Vulnerability · Source |
| CVE-2020-26959 | suse_vex | SUSE CVE CVE-2020-26959 | known affected: 56 recommended: 405 | 2026-07-25T17:48:29+00:00 | Vulnerability · Source |
| CVE-2020-26962 | suse_vex | SUSE CVE CVE-2020-26962 | known affected: 59 recommended: 9 | 2026-07-25T17:48:28+00:00 | Vulnerability · Source |
| CVE-2020-26965 | suse_vex | SUSE CVE CVE-2020-26965 | known affected: 56 recommended: 405 | 2026-07-25T17:48:26+00:00 | Vulnerability · Source |
| CVE-2020-26971 | suse_vex | SUSE CVE CVE-2020-26971 | recommended: 463 | 2026-07-25T17:48:25+00:00 | Vulnerability · Source |
| CVE-2020-26973 | suse_vex | SUSE CVE CVE-2020-26973 | recommended: 463 | 2026-07-25T17:48:24+00:00 | Vulnerability · Source |
| CVE-2020-27068 | suse_vex | SUSE CVE CVE-2020-27068 | known affected: 292 known not affected: 108 recommended: 1614 | 2026-07-25T17:48:22+00:00 | Vulnerability · Source |
| CVE-2020-27152 | suse_vex | SUSE CVE CVE-2020-27152 | known not affected: 605 recommended: 20 | 2026-07-25T17:48:21+00:00 | Vulnerability · Source |
| CVE-2020-27153 | suse_vex | SUSE CVE CVE-2020-27153 | known not affected: 62 recommended: 85 | 2026-07-25T17:48:19+00:00 | Vulnerability · Source |
| CVE-2020-27617 | suse_vex | SUSE CVE CVE-2020-27617 | known affected: 388 known not affected: 5 recommended: 847 | 2026-07-25T17:48:18+00:00 | Vulnerability · Source |
| CVE-2020-27618 | suse_vex | SUSE CVE CVE-2020-27618 | known affected: 330 known not affected: 60 recommended: 1441 | 2026-07-25T17:48:16+00:00 | Vulnerability · Source |