VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285037 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2020-17527 | suse_vex | SUSE CVE CVE-2020-17527 | known affected: 394 known not affected: 151 recommended: 536 | 2026-07-25T17:50:17+00:00 | Vulnerability · Source |
| CVE-2020-18032 | suse_vex | SUSE CVE CVE-2020-18032 | known affected: 394 known not affected: 11 recommended: 329 | 2026-07-25T17:50:15+00:00 | Vulnerability · Source |
| CVE-2020-18652 | suse_vex | SUSE CVE CVE-2020-18652 | known not affected: 35 recommended: 62 | 2026-07-25T17:50:14+00:00 | Vulnerability · Source |
| CVE-2020-18771 | suse_vex | SUSE CVE CVE-2020-18771 | known not affected: 106 | 2026-07-25T17:50:13+00:00 | Vulnerability · Source |
| CVE-2020-18774 | suse_vex | SUSE CVE CVE-2020-18774 | known not affected: 106 | 2026-07-25T17:50:12+00:00 | Vulnerability · Source |
| CVE-2020-19143 | suse_vex | SUSE CVE CVE-2020-19143 | known not affected: 142 | 2026-07-25T17:50:10+00:00 | Vulnerability · Source |
| CVE-2020-19186 | suse_vex | SUSE CVE CVE-2020-19186 | known not affected: 635 | 2026-07-25T17:50:09+00:00 | Vulnerability · Source |
| CVE-2020-19189 | suse_vex | SUSE CVE CVE-2020-19189 | known not affected: 635 | 2026-07-25T17:50:07+00:00 | Vulnerability · Source |
| CVE-2020-19667 | suse_vex | SUSE CVE CVE-2020-19667 | recommended: 769 | 2026-07-25T17:50:06+00:00 | Vulnerability · Source |
| CVE-2020-19724 | suse_vex | SUSE CVE CVE-2020-19724 | known not affected: 234 | 2026-07-25T17:50:05+00:00 | Vulnerability · Source |
| CVE-2020-19726 | suse_vex | SUSE CVE CVE-2020-19726 | known affected: 450 recommended: 326 | 2026-07-25T17:50:03+00:00 | Vulnerability · Source |
| CVE-2020-20412 | suse_vex | SUSE CVE CVE-2020-20412 | known not affected: 246 | 2026-07-25T17:50:01+00:00 | Vulnerability · Source |
| CVE-2020-21047 | suse_vex | SUSE CVE CVE-2020-21047 | known not affected: 631 | 2026-07-25T17:50:00+00:00 | Vulnerability · Source |
| CVE-2020-21529 | suse_vex | SUSE CVE CVE-2020-21529 | known affected: 4 recommended: 47 | 2026-07-25T17:49:59+00:00 | Vulnerability · Source |
| CVE-2020-21532 | suse_vex | SUSE CVE CVE-2020-21532 | known affected: 3 recommended: 47 | 2026-07-25T17:49:57+00:00 | Vulnerability · Source |
| CVE-2020-21535 | suse_vex | SUSE CVE CVE-2020-21535 | known affected: 1 recommended: 47 | 2026-07-25T17:49:56+00:00 | Vulnerability · Source |
| CVE-2020-21583 | suse_vex | SUSE CVE CVE-2020-21583 | known not affected: 767 | 2026-07-25T17:49:55+00:00 | Vulnerability · Source |
| CVE-2020-21674 | suse_vex | SUSE CVE CVE-2020-21674 | known not affected: 149 | 2026-07-25T17:49:53+00:00 | Vulnerability · Source |
| CVE-2020-21679 | suse_vex | SUSE CVE CVE-2020-21679 | recommended: 96 | 2026-07-25T17:49:52+00:00 | Vulnerability · Source |
| CVE-2020-22217 | suse_vex | SUSE CVE CVE-2020-22217 | known affected: 13 known not affected: 112 recommended: 14 | 2026-07-25T17:49:50+00:00 | Vulnerability · Source |