VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284624 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-0181 | suse_vex | SUSE CVE CVE-2020-0181 | known affected: 9 recommended: 171 | 2026-07-25T17:56:34+00:00 | Vulnerability · Source |
| CVE-2020-0256 | suse_vex | SUSE CVE CVE-2020-0256 | recommended: 36 | 2026-07-25T17:56:32+00:00 | Vulnerability · Source |
| CVE-2020-0404 | suse_vex | SUSE CVE CVE-2020-0404 | known affected: 455 known not affected: 10 recommended: 1588 | 2026-07-25T17:56:31+00:00 | Vulnerability · Source |
| CVE-2020-0429 | suse_vex | SUSE CVE CVE-2020-0429 | known affected: 460 known not affected: 488 recommended: 425 | 2026-07-25T17:56:29+00:00 | Vulnerability · Source |
| CVE-2020-0465 | suse_vex | SUSE CVE CVE-2020-0465 | known affected: 292 known not affected: 2 recommended: 1828 | 2026-07-25T17:56:27+00:00 | Vulnerability · Source |
| CVE-2020-0487 | suse_vex | SUSE CVE CVE-2020-0487 | known affected: 420 known not affected: 112 recommended: 221 | 2026-07-25T17:56:26+00:00 | Vulnerability · Source |
| CVE-2020-0570 | suse_vex | SUSE CVE CVE-2020-0570 | known affected: 394 known not affected: 1999 recommended: 2002 | 2026-07-25T17:56:24+00:00 | Vulnerability · Source |
| CVE-2020-0599 | suse_vex | SUSE CVE CVE-2020-0599 | known not affected: 53 | 2026-07-25T17:56:23+00:00 | Vulnerability · Source |
| CVE-2020-1700 | suse_vex | SUSE CVE CVE-2020-1700 | known affected: 85 known not affected: 286 recommended: 214 | 2026-07-25T17:56:21+00:00 | Vulnerability · Source |
| CVE-2020-1711 | suse_vex | SUSE CVE CVE-2020-1711 | known affected: 632 known not affected: 489 recommended: 2079 | 2026-07-25T17:56:19+00:00 | Vulnerability · Source |
| CVE-2020-1712 | suse_vex | SUSE CVE CVE-2020-1712 | known affected: 439 known not affected: 26 recommended: 1324 | 2026-07-25T17:56:17+00:00 | Vulnerability · Source |
| CVE-2020-1730 | suse_vex | SUSE CVE CVE-2020-1730 | known affected: 320 known not affected: 79 recommended: 326 | 2026-07-25T17:56:16+00:00 | Vulnerability · Source |
| CVE-2020-1737 | suse_vex | SUSE CVE CVE-2020-1737 | known affected: 1 known not affected: 2 recommended: 248 | 2026-07-25T17:56:15+00:00 | Vulnerability · Source |
| CVE-2020-1749 | suse_vex | SUSE CVE CVE-2020-1749 | known affected: 320 known not affected: 449 recommended: 1788 | 2026-07-25T17:56:13+00:00 | Vulnerability · Source |
| CVE-2020-1751 | suse_vex | SUSE CVE CVE-2020-1751 | known affected: 320 known not affected: 315 recommended: 1084 | 2026-07-25T17:56:12+00:00 | Vulnerability · Source |
| CVE-2020-1759 | suse_vex | SUSE CVE CVE-2020-1759 | known not affected: 625 recommended: 1005 | 2026-07-25T17:56:10+00:00 | Vulnerability · Source |
| CVE-2020-1927 | suse_vex | SUSE CVE CVE-2020-1927 | known affected: 31 known not affected: 3 recommended: 256 | 2026-07-25T17:56:09+00:00 | Vulnerability · Source |
| CVE-2020-1930 | suse_vex | SUSE CVE CVE-2020-1930 | known affected: 24 recommended: 224 | 2026-07-25T17:56:08+00:00 | Vulnerability · Source |
| CVE-2020-1935 | suse_vex | SUSE CVE CVE-2020-1935 | known affected: 484 known not affected: 56 recommended: 388 | 2026-07-25T17:56:06+00:00 | Vulnerability · Source |
| CVE-2020-1945 | suse_vex | SUSE CVE CVE-2020-1945 | known affected: 33 known not affected: 91 recommended: 1327 | 2026-07-25T17:56:04+00:00 | Vulnerability · Source |
| CVE-2020-1968 | suse_vex | SUSE CVE CVE-2020-1968 | known not affected: 391 recommended: 61 | 2026-07-25T17:56:03+00:00 | Vulnerability · Source |
| CVE-2020-1971 | suse_vex | SUSE CVE CVE-2020-1971 | known affected: 405 known not affected: 422 recommended: 1356 | 2026-07-25T17:56:01+00:00 | Vulnerability · Source |
| CVE-2020-2654 | suse_vex | SUSE CVE CVE-2020-2654 | known affected: 481 recommended: 1199 | 2026-07-25T17:56:00+00:00 | Vulnerability · Source |
| CVE-2020-2655 | suse_vex | SUSE CVE CVE-2020-2655 | known affected: 554 recommended: 320 | 2026-07-25T17:55:58+00:00 | Vulnerability · Source |
| CVE-2020-2732 | suse_vex | SUSE CVE CVE-2020-2732 | known affected: 444 known not affected: 206 recommended: 1481 | 2026-07-25T17:55:56+00:00 | Vulnerability · Source |
| CVE-2020-2757 | suse_vex | SUSE CVE CVE-2020-2757 | known affected: 454 recommended: 1199 | 2026-07-25T17:55:55+00:00 | Vulnerability · Source |
| CVE-2020-2803 | suse_vex | SUSE CVE CVE-2020-2803 | known affected: 454 recommended: 1199 | 2026-07-25T17:55:53+00:00 | Vulnerability · Source |
| CVE-2020-2816 | suse_vex | SUSE CVE CVE-2020-2816 | known affected: 454 recommended: 297 | 2026-07-25T17:55:52+00:00 | Vulnerability · Source |
| CVE-2020-2830 | suse_vex | SUSE CVE CVE-2020-2830 | known affected: 454 recommended: 1192 | 2026-07-25T17:55:50+00:00 | Vulnerability · Source |
| CVE-2020-3702 | suse_vex | SUSE CVE CVE-2020-3702 | known affected: 317 known not affected: 57 recommended: 1337 | 2026-07-25T17:55:48+00:00 | Vulnerability · Source |
| CVE-2020-3895 | suse_vex | SUSE CVE CVE-2020-3895 | known affected: 45 known not affected: 90 recommended: 1030 | 2026-07-25T17:55:47+00:00 | Vulnerability · Source |
| CVE-2020-4032 | suse_vex | SUSE CVE CVE-2020-4032 | recommended: 171 | 2026-07-25T17:55:45+00:00 | Vulnerability · Source |
| CVE-2020-4788 | suse_vex | SUSE CVE CVE-2020-4788 | known affected: 304 known not affected: 27 recommended: 1654 | 2026-07-25T17:55:43+00:00 | Vulnerability · Source |
| CVE-2020-5208 | suse_vex | SUSE CVE CVE-2020-5208 | known affected: 394 known not affected: 46 recommended: 124 | 2026-07-25T17:55:42+00:00 | Vulnerability · Source |
| CVE-2020-5260 | suse_vex | SUSE CVE CVE-2020-5260 | known affected: 120 recommended: 972 | 2026-07-25T17:55:41+00:00 | Vulnerability · Source |
| CVE-2020-5291 | suse_vex | SUSE CVE CVE-2020-5291 | known not affected: 18 recommended: 65 | 2026-07-25T17:55:39+00:00 | Vulnerability · Source |
| CVE-2020-6097 | suse_vex | SUSE CVE CVE-2020-6097 | known not affected: 21 recommended: 2 | 2026-07-25T17:55:38+00:00 | Vulnerability · Source |
| CVE-2020-6463 | suse_vex | SUSE CVE CVE-2020-6463 | known affected: 24 recommended: 531 | 2026-07-25T17:55:33+00:00 | Vulnerability · Source |
| CVE-2020-6798 | suse_vex | SUSE CVE CVE-2020-6798 | known affected: 20 recommended: 402 | 2026-07-25T17:55:31+00:00 | Vulnerability · Source |
| CVE-2020-6811 | suse_vex | SUSE CVE CVE-2020-6811 | recommended: 380 | 2026-07-25T17:55:29+00:00 | Vulnerability · Source |
| CVE-2020-6814 | suse_vex | SUSE CVE CVE-2020-6814 | recommended: 380 | 2026-07-25T17:55:28+00:00 | Vulnerability · Source |
| CVE-2020-6820 | suse_vex | SUSE CVE CVE-2020-6820 | known affected: 24 recommended: 380 | 2026-07-25T17:55:27+00:00 | Vulnerability · Source |
| CVE-2020-6821 | suse_vex | SUSE CVE CVE-2020-6821 | recommended: 380 | 2026-07-25T17:55:25+00:00 | Vulnerability · Source |
| CVE-2020-6827 | suse_vex | SUSE CVE CVE-2020-6827 | recommended: 301 | 2026-07-25T17:55:23+00:00 | Vulnerability · Source |
| CVE-2020-7039 | suse_vex | SUSE CVE CVE-2020-7039 | known affected: 665 known not affected: 187 recommended: 2108 | 2026-07-25T17:55:22+00:00 | Vulnerability · Source |
| CVE-2020-7044 | suse_vex | SUSE CVE CVE-2020-7044 | known not affected: 134 recommended: 677 | 2026-07-25T17:55:20+00:00 | Vulnerability · Source |
| CVE-2020-7045 | suse_vex | SUSE CVE CVE-2020-7045 | known not affected: 189 | 2026-07-25T17:55:18+00:00 | Vulnerability · Source |
| CVE-2020-7053 | suse_vex | SUSE CVE CVE-2020-7053 | known affected: 102 known not affected: 243 recommended: 534 | 2026-07-25T17:55:16+00:00 | Vulnerability · Source |
| CVE-2020-7212 | suse_vex | SUSE CVE CVE-2020-7212 | known not affected: 119 | 2026-07-25T17:55:15+00:00 | Vulnerability · Source |
| CVE-2020-8016 | suse_vex | SUSE CVE CVE-2020-8016 | known affected: 30 known not affected: 1710 recommended: 13633 | 2026-07-25T17:55:11+00:00 | Vulnerability · Source |