VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283449 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-14401 | suse_vex | SUSE CVE CVE-2020-14401 | known affected: 24 recommended: 119 | 2026-07-25T17:51:29+00:00 | Vulnerability · Source |
| CVE-2020-14402 | suse_vex | SUSE CVE CVE-2020-14402 | known affected: 24 recommended: 119 | 2026-07-25T17:51:28+00:00 | Vulnerability · Source |
| CVE-2020-14404 | suse_vex | SUSE CVE CVE-2020-14404 | known affected: 24 recommended: 72 | 2026-07-25T17:51:27+00:00 | Vulnerability · Source |
| CVE-2020-14409 | suse_vex | SUSE CVE CVE-2020-14409 | known affected: 36 recommended: 298 | 2026-07-25T17:51:25+00:00 | Vulnerability · Source |
| CVE-2020-14415 | suse_vex | SUSE CVE CVE-2020-14415 | known not affected: 1872 | 2026-07-25T17:51:24+00:00 | Vulnerability · Source |
| CVE-2020-14556 | suse_vex | SUSE CVE CVE-2020-14556 | known affected: 564 recommended: 1004 | 2026-07-25T17:51:22+00:00 | Vulnerability · Source |
| CVE-2020-14583 | suse_vex | SUSE CVE CVE-2020-14583 | known affected: 564 recommended: 1246 | 2026-07-25T17:51:21+00:00 | Vulnerability · Source |
| CVE-2020-14621 | suse_vex | SUSE CVE CVE-2020-14621 | known affected: 564 recommended: 1246 | 2026-07-25T17:51:19+00:00 | Vulnerability · Source |
| CVE-2020-14664 | suse_vex | SUSE CVE CVE-2020-14664 | known affected: 170 recommended: 5 | 2026-07-25T17:51:18+00:00 | Vulnerability · Source |
| CVE-2020-14781 | suse_vex | SUSE CVE CVE-2020-14781 | known affected: 484 recommended: 1242 | 2026-07-25T17:51:16+00:00 | Vulnerability · Source |
| CVE-2020-14782 | suse_vex | SUSE CVE CVE-2020-14782 | known affected: 484 recommended: 938 | 2026-07-25T17:51:15+00:00 | Vulnerability · Source |
| CVE-2020-14789 | suse_vex | SUSE CVE CVE-2020-14789 | known not affected: 90 recommended: 664 | 2026-07-25T17:51:13+00:00 | Vulnerability · Source |
| CVE-2020-14796 | suse_vex | SUSE CVE CVE-2020-14796 | known affected: 484 recommended: 1242 | 2026-07-25T17:51:11+00:00 | Vulnerability · Source |
| CVE-2020-14803 | suse_vex | SUSE CVE CVE-2020-14803 | known affected: 484 recommended: 1328 | 2026-07-25T17:51:10+00:00 | Vulnerability · Source |
| CVE-2020-14871 | suse_vex | SUSE CVE CVE-2020-14871 | known not affected: 142 | 2026-07-25T17:51:08+00:00 | Vulnerability · Source |
| CVE-2020-15011 | suse_vex | SUSE CVE CVE-2020-15011 | known affected: 8 recommended: 33 | 2026-07-25T17:51:07+00:00 | Vulnerability · Source |
| CVE-2020-15254 | suse_vex | SUSE CVE CVE-2020-15254 | known affected: 56 recommended: 9 | 2026-07-25T17:51:06+00:00 | Vulnerability · Source |
| CVE-2020-15304 | suse_vex | SUSE CVE CVE-2020-15304 | known affected: 28 known not affected: 58 recommended: 202 | 2026-07-25T17:51:04+00:00 | Vulnerability · Source |
| CVE-2020-15305 | suse_vex | SUSE CVE CVE-2020-15305 | known affected: 28 known not affected: 58 recommended: 202 | 2026-07-25T17:51:03+00:00 | Vulnerability · Source |
| CVE-2020-15365 | suse_vex | SUSE CVE CVE-2020-15365 | known not affected: 707 | 2026-07-25T17:51:02+00:00 | Vulnerability · Source |
| CVE-2020-15389 | suse_vex | SUSE CVE CVE-2020-15389 | known affected: 4 known not affected: 423 recommended: 334 | 2026-07-25T17:51:01+00:00 | Vulnerability · Source |
| CVE-2020-15469 | suse_vex | SUSE CVE CVE-2020-15469 | known affected: 454 known not affected: 32 recommended: 850 | 2026-07-25T17:50:59+00:00 | Vulnerability · Source |
| CVE-2020-15523 | suse_vex | SUSE CVE CVE-2020-15523 | known affected: 14 known not affected: 678 recommended: 274 | 2026-07-25T17:50:57+00:00 | Vulnerability · Source |
| CVE-2020-15564 | suse_vex | SUSE CVE CVE-2020-15564 | known not affected: 278 | 2026-07-25T17:50:56+00:00 | Vulnerability · Source |
| CVE-2020-15565 | suse_vex | SUSE CVE CVE-2020-15565 | known affected: 406 recommended: 531 | 2026-07-25T17:50:55+00:00 | Vulnerability · Source |
| CVE-2020-15567 | suse_vex | SUSE CVE CVE-2020-15567 | known affected: 413 recommended: 539 | 2026-07-25T17:50:53+00:00 | Vulnerability · Source |
| CVE-2020-15650 | suse_vex | SUSE CVE CVE-2020-15650 | known affected: 24 known not affected: 24 | 2026-07-25T17:50:52+00:00 | Vulnerability · Source |
| CVE-2020-15654 | suse_vex | SUSE CVE CVE-2020-15654 | known affected: 24 recommended: 455 | 2026-07-25T17:50:51+00:00 | Vulnerability · Source |
| CVE-2020-15655 | suse_vex | SUSE CVE CVE-2020-15655 | known affected: 24 recommended: 453 | 2026-07-25T17:50:49+00:00 | Vulnerability · Source |
| CVE-2020-15665 | suse_vex | SUSE CVE CVE-2020-15665 | known affected: 21 recommended: 9 | 2026-07-25T17:50:48+00:00 | Vulnerability · Source |
| CVE-2020-15667 | suse_vex | SUSE CVE CVE-2020-15667 | known affected: 21 recommended: 9 | 2026-07-25T17:50:47+00:00 | Vulnerability · Source |
| CVE-2020-15677 | suse_vex | SUSE CVE CVE-2020-15677 | known affected: 3 known not affected: 155 recommended: 561 | 2026-07-25T17:50:45+00:00 | Vulnerability · Source |
| CVE-2020-15683 | suse_vex | SUSE CVE CVE-2020-15683 | known affected: 56 recommended: 561 | 2026-07-25T17:50:44+00:00 | Vulnerability · Source |
| CVE-2020-15705 | suse_vex | SUSE CVE CVE-2020-15705 | known affected: 414 recommended: 850 | 2026-07-25T17:50:42+00:00 | Vulnerability · Source |
| CVE-2020-15719 | suse_vex | SUSE CVE CVE-2020-15719 | known affected: 326 recommended: 577 | 2026-07-25T17:50:40+00:00 | Vulnerability · Source |
| CVE-2020-15778 | suse_vex | SUSE CVE CVE-2020-15778 | recommended: 8 | 2026-07-25T17:50:39+00:00 | Vulnerability · Source |
| CVE-2020-15803 | suse_vex | SUSE CVE CVE-2020-15803 | known affected: 20 recommended: 83 | 2026-07-25T17:50:38+00:00 | Vulnerability · Source |
| CVE-2020-15863 | suse_vex | SUSE CVE CVE-2020-15863 | known affected: 454 known not affected: 33 recommended: 1900 | 2026-07-25T17:50:36+00:00 | Vulnerability · Source |
| CVE-2020-15999 | suse_vex | SUSE CVE CVE-2020-15999 | known affected: 282 known not affected: 87 recommended: 1072 | 2026-07-25T17:50:34+00:00 | Vulnerability · Source |
| CVE-2020-16119 | suse_vex | SUSE CVE CVE-2020-16119 | known affected: 253 known not affected: 751 recommended: 896 | 2026-07-25T17:50:33+00:00 | Vulnerability · Source |
| CVE-2020-16120 | suse_vex | SUSE CVE CVE-2020-16120 | known affected: 413 known not affected: 140 recommended: 1379 | 2026-07-25T17:50:31+00:00 | Vulnerability · Source |
| CVE-2020-16295 | suse_vex | SUSE CVE CVE-2020-16295 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:30+00:00 | Vulnerability · Source |
| CVE-2020-16301 | suse_vex | SUSE CVE CVE-2020-16301 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:28+00:00 | Vulnerability · Source |
| CVE-2020-16302 | suse_vex | SUSE CVE CVE-2020-16302 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:27+00:00 | Vulnerability · Source |
| CVE-2020-16303 | suse_vex | SUSE CVE CVE-2020-16303 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:26+00:00 | Vulnerability · Source |
| CVE-2020-16307 | suse_vex | SUSE CVE CVE-2020-16307 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:24+00:00 | Vulnerability · Source |
| CVE-2020-16310 | suse_vex | SUSE CVE CVE-2020-16310 | known not affected: 172 recommended: 8 | 2026-07-25T17:50:23+00:00 | Vulnerability · Source |
| CVE-2020-16593 | suse_vex | SUSE CVE CVE-2020-16593 | known affected: 395 known not affected: 85 recommended: 540 | 2026-07-25T17:50:22+00:00 | Vulnerability · Source |
| CVE-2020-16598 | suse_vex | SUSE CVE CVE-2020-16598 | known affected: 398 known not affected: 23 recommended: 540 | 2026-07-25T17:50:20+00:00 | Vulnerability · Source |
| CVE-2020-17380 | suse_vex | SUSE CVE CVE-2020-17380 | known affected: 460 known not affected: 45 recommended: 1378 | 2026-07-25T17:50:19+00:00 | Vulnerability · Source |