VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104645 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-19190 | suse_vex | SUSE CVE CVE-2020-19190 | known affected: 0 known not affected: 707 | 2026-10-17T01:47:09+00:00 | Vulnerability · Source |
| CVE-2020-19667 | suse_vex | SUSE CVE CVE-2020-19667 | recommended: 767 | 2026-10-17T01:47:07+00:00 | Vulnerability · Source |
| CVE-2020-19909 | suse_vex | SUSE CVE CVE-2020-19909 | recommended: 6 | 2026-10-17T01:47:06+00:00 | Vulnerability · Source |
| CVE-2020-21047 | suse_vex | SUSE CVE CVE-2020-21047 | known affected: 0 known not affected: 698 | 2026-10-17T01:47:04+00:00 | Vulnerability · Source |
| CVE-2020-21913 | suse_vex | SUSE CVE CVE-2020-21913 | known affected: 527 known not affected: 8 recommended: 611 | 2026-10-17T01:47:02+00:00 | Vulnerability · Source |
| CVE-2020-22046 | suse_vex | SUSE CVE CVE-2020-22046 | recommended: 1297 | 2026-10-17T01:47:00+00:00 | Vulnerability · Source |
| CVE-2020-22218 | suse_vex | SUSE CVE CVE-2020-22218 | known affected: 394 known not affected: 417 recommended: 126 | 2026-10-17T01:46:59+00:00 | Vulnerability · Source |
| CVE-2020-22628 | suse_vex | SUSE CVE CVE-2020-22628 | recommended: 87 | 2026-10-17T01:46:57+00:00 | Vulnerability · Source |
| CVE-2020-23793 | suse_vex | SUSE CVE CVE-2020-23793 | known affected: 0 known not affected: 544 | 2026-10-17T01:46:55+00:00 | Vulnerability · Source |
| CVE-2020-24165 | suse_vex | SUSE CVE CVE-2020-24165 | known affected: 0 known not affected: 939 | 2026-10-17T01:46:53+00:00 | Vulnerability · Source |
| CVE-2020-24352 | suse_vex | SUSE CVE CVE-2020-24352 | known affected: 0 known not affected: 1157 recommended: 1312 | 2026-10-17T01:46:52+00:00 | Vulnerability · Source |
| CVE-2020-24369 | suse_vex | SUSE CVE CVE-2020-24369 | known affected: 0 known not affected: 409 recommended: 27 | 2026-10-17T01:46:50+00:00 | Vulnerability · Source |
| CVE-2020-24370 | suse_vex | SUSE CVE CVE-2020-24370 | known affected: 323 known not affected: 293 recommended: 324 | 2026-10-17T01:46:49+00:00 | Vulnerability · Source |
| CVE-2020-24502 | suse_vex | SUSE CVE CVE-2020-24502 | known affected: 0 known not affected: 420 recommended: 20 | 2026-10-17T01:46:48+00:00 | Vulnerability · Source |
| CVE-2020-24511 | suse_vex | SUSE CVE CVE-2020-24511 | recommended: 94 | 2026-10-17T01:46:46+00:00 | Vulnerability · Source |
| CVE-2020-24513 | suse_vex | SUSE CVE CVE-2020-24513 | recommended: 94 | 2026-10-17T01:46:45+00:00 | Vulnerability · Source |
| CVE-2020-24586 | suse_vex | SUSE CVE CVE-2020-24586 | known affected: 318 known not affected: 122 recommended: 1546 | 2026-10-17T01:46:43+00:00 | Vulnerability · Source |
| CVE-2020-24588 | suse_vex | SUSE CVE CVE-2020-24588 | known affected: 213 known not affected: 10 recommended: 1841 | 2026-10-17T01:46:42+00:00 | Vulnerability · Source |
| CVE-2020-24606 | suse_vex | SUSE CVE CVE-2020-24606 | known affected: 396 recommended: 81 | 2026-10-17T01:46:40+00:00 | Vulnerability · Source |
| CVE-2020-24659 | suse_vex | SUSE CVE CVE-2020-24659 | known affected: 320 known not affected: 88 recommended: 487 | 2026-10-17T01:46:39+00:00 | Vulnerability · Source |
| CVE-2020-24977 | suse_vex | SUSE CVE CVE-2020-24977 | known affected: 415 known not affected: 79 recommended: 480 | 2026-10-17T01:46:37+00:00 | Vulnerability · Source |
| CVE-2020-24979 | suse_vex | SUSE CVE CVE-2020-24979 | known affected: 0 known not affected: 110 recommended: 11 | 2026-10-17T01:46:36+00:00 | Vulnerability · Source |
| CVE-2020-25211 | suse_vex | SUSE CVE CVE-2020-25211 | known affected: 364 known not affected: 122 recommended: 1217 | 2026-10-17T01:46:35+00:00 | Vulnerability · Source |
| CVE-2020-25219 | suse_vex | SUSE CVE CVE-2020-25219 | known affected: 322 known not affected: 64 recommended: 495 | 2026-10-17T01:46:33+00:00 | Vulnerability · Source |
| CVE-2020-25221 | suse_vex | SUSE CVE CVE-2020-25221 | known affected: 0 known not affected: 429 | 2026-10-17T01:46:32+00:00 | Vulnerability · Source |
| CVE-2020-25657 | suse_vex | SUSE CVE CVE-2020-25657 | known affected: 397 recommended: 196 | 2026-10-17T01:46:30+00:00 | Vulnerability · Source |
| CVE-2020-25658 | suse_vex | SUSE CVE CVE-2020-25658 | known affected: 426 recommended: 75 | 2026-10-17T01:46:29+00:00 | Vulnerability · Source |
| CVE-2020-25659 | suse_vex | SUSE CVE CVE-2020-25659 | known affected: 263 known not affected: 10 recommended: 378 | 2026-10-17T01:46:27+00:00 | Vulnerability · Source |
| CVE-2020-25665 | suse_vex | SUSE CVE CVE-2020-25665 | recommended: 764 | 2026-10-17T01:46:26+00:00 | Vulnerability · Source |
| CVE-2020-25668 | suse_vex | SUSE CVE CVE-2020-25668 | known affected: 548 known not affected: 10 recommended: 1826 | 2026-10-17T01:46:24+00:00 | Vulnerability · Source |
| CVE-2020-25673 | suse_vex | SUSE CVE CVE-2020-25673 | known affected: 300 known not affected: 98 recommended: 1502 | 2026-10-17T01:46:22+00:00 | Vulnerability · Source |
| CVE-2020-25676 | suse_vex | SUSE CVE CVE-2020-25676 | known affected: 0 known not affected: 4 recommended: 760 | 2026-10-17T01:46:21+00:00 | Vulnerability · Source |
| CVE-2020-25678 | suse_vex | SUSE CVE CVE-2020-25678 | known affected: 64 known not affected: 1016 recommended: 1009 | 2026-10-17T01:46:19+00:00 | Vulnerability · Source |
| CVE-2020-25683 | suse_vex | SUSE CVE CVE-2020-25683 | recommended: 113 | 2026-10-17T01:46:18+00:00 | Vulnerability · Source |
| CVE-2020-25695 | suse_vex | SUSE CVE CVE-2020-25695 | known affected: 471 known not affected: 189 recommended: 2163 | 2026-10-17T01:46:16+00:00 | Vulnerability · Source |
| CVE-2020-25707 | suse_vex | SUSE CVE CVE-2020-25707 | known affected: 1 recommended: 1918 | 2026-10-17T01:46:14+00:00 | Vulnerability · Source |
| CVE-2020-25709 | suse_vex | SUSE CVE CVE-2020-25709 | known affected: 371 recommended: 585 | 2026-10-17T01:46:12+00:00 | Vulnerability · Source |
| CVE-2020-25710 | suse_vex | SUSE CVE CVE-2020-25710 | known affected: 79 recommended: 483 | 2026-10-17T01:46:11+00:00 | Vulnerability · Source |
| CVE-2020-25719 | suse_vex | SUSE CVE CVE-2020-25719 | known affected: 335 known not affected: 2230 recommended: 1805 | 2026-10-17T01:46:09+00:00 | Vulnerability · Source |
| CVE-2020-25722 | suse_vex | SUSE CVE CVE-2020-25722 | known affected: 335 known not affected: 2230 recommended: 1770 | 2026-10-17T01:46:07+00:00 | Vulnerability · Source |
| CVE-2020-25723 | suse_vex | SUSE CVE CVE-2020-25723 | known affected: 389 known not affected: 228 recommended: 2014 | 2026-10-17T01:46:05+00:00 | Vulnerability · Source |
| CVE-2020-25862 | suse_vex | SUSE CVE CVE-2020-25862 | known affected: 37 known not affected: 158 recommended: 342 | 2026-10-17T01:46:04+00:00 | Vulnerability · Source |
| CVE-2020-25866 | suse_vex | SUSE CVE CVE-2020-25866 | known affected: 37 known not affected: 158 recommended: 342 | 2026-10-17T01:46:03+00:00 | Vulnerability · Source |
| CVE-2020-26146 | suse_vex | SUSE CVE CVE-2020-26146 | known affected: 22 known not affected: 174 recommended: 20 | 2026-10-17T01:45:59+00:00 | Vulnerability · Source |
| CVE-2020-26159 | suse_vex | SUSE CVE CVE-2020-26159 | known affected: 243 recommended: 274 | 2026-10-17T01:45:58+00:00 | Vulnerability · Source |
| CVE-2020-26240 | suse_vex | SUSE CVE CVE-2020-26240 | recommended: 5 | 2026-10-17T01:45:57+00:00 | Vulnerability · Source |
| CVE-2020-26241 | suse_vex | SUSE CVE CVE-2020-26241 | recommended: 5 | 2026-10-17T01:45:56+00:00 | Vulnerability · Source |
| CVE-2020-26418 | suse_vex | SUSE CVE CVE-2020-26418 | known affected: 0 known not affected: 150 recommended: 646 | 2026-10-17T01:45:54+00:00 | Vulnerability · Source |
| CVE-2020-26421 | suse_vex | SUSE CVE CVE-2020-26421 | known affected: 104 known not affected: 18 recommended: 679 | 2026-10-17T01:45:53+00:00 | Vulnerability · Source |
| CVE-2020-26541 | suse_vex | SUSE CVE CVE-2020-26541 | known affected: 374 known not affected: 75 recommended: 884 | 2026-10-17T01:45:52+00:00 | Vulnerability · Source |