VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
103916 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-35477 | suse_vex | SUSE CVE CVE-2021-35477 | known affected: 311 known not affected: 101 recommended: 1376 | 2026-10-17T01:36:15+00:00 | Vulnerability · Source |
| CVE-2021-35517 | suse_vex | SUSE CVE CVE-2021-35517 | recommended: 57 | 2026-10-17T01:36:14+00:00 | Vulnerability · Source |
| CVE-2021-35567 | suse_vex | SUSE CVE CVE-2021-35567 | known affected: 396 known not affected: 54 recommended: 787 | 2026-10-17T01:36:12+00:00 | Vulnerability · Source |
| CVE-2021-35578 | suse_vex | SUSE CVE CVE-2021-35578 | known affected: 395 known not affected: 106 recommended: 1051 | 2026-10-17T01:36:11+00:00 | Vulnerability · Source |
| CVE-2021-35604 | suse_vex | SUSE CVE CVE-2021-35604 | known affected: 0 known not affected: 86 recommended: 454 | 2026-10-17T01:36:09+00:00 | Vulnerability · Source |
| CVE-2021-35940 | suse_vex | SUSE CVE CVE-2021-35940 | known affected: 0 known not affected: 92 recommended: 10 | 2026-10-17T01:36:08+00:00 | Vulnerability · Source |
| CVE-2021-35942 | suse_vex | SUSE CVE CVE-2021-35942 | known affected: 402 recommended: 1397 | 2026-10-17T01:36:07+00:00 | Vulnerability · Source |
| CVE-2021-36084 | suse_vex | SUSE CVE CVE-2021-36084 | known affected: 0 known not affected: 192 recommended: 3 | 2026-10-17T01:36:05+00:00 | Vulnerability · Source |
| CVE-2021-36085 | suse_vex | SUSE CVE CVE-2021-36085 | known affected: 0 known not affected: 192 recommended: 44 | 2026-10-17T01:36:04+00:00 | Vulnerability · Source |
| CVE-2021-36086 | suse_vex | SUSE CVE CVE-2021-36086 | known affected: 0 known not affected: 192 recommended: 44 | 2026-10-17T01:36:03+00:00 | Vulnerability · Source |
| CVE-2021-36087 | suse_vex | SUSE CVE CVE-2021-36087 | known affected: 0 known not affected: 673 recommended: 44 | 2026-10-17T01:36:01+00:00 | Vulnerability · Source |
| CVE-2021-36090 | suse_vex | SUSE CVE CVE-2021-36090 | recommended: 57 | 2026-10-17T01:36:00+00:00 | Vulnerability · Source |
| CVE-2021-36222 | suse_vex | SUSE CVE CVE-2021-36222 | known affected: 305 known not affected: 271 recommended: 1662 | 2026-10-17T01:35:58+00:00 | Vulnerability · Source |
| CVE-2021-36374 | suse_vex | SUSE CVE CVE-2021-36374 | known affected: 0 known not affected: 6 recommended: 1455 | 2026-10-17T01:35:57+00:00 | Vulnerability · Source |
| CVE-2021-36690 | suse_vex | SUSE CVE CVE-2021-36690 | known affected: 244 known not affected: 61 recommended: 538 | 2026-10-17T01:35:55+00:00 | Vulnerability · Source |
| CVE-2021-36976 | suse_vex | SUSE CVE CVE-2021-36976 | known affected: 394 known not affected: 96 recommended: 138 | 2026-10-17T01:35:54+00:00 | Vulnerability · Source |
| CVE-2021-36980 | suse_vex | SUSE CVE CVE-2021-36980 | known affected: 81 known not affected: 67 recommended: 530 | 2026-10-17T01:35:53+00:00 | Vulnerability · Source |
| CVE-2021-37577 | suse_vex | SUSE CVE CVE-2021-37577 | known affected: 800 | 2026-10-17T01:35:51+00:00 | Vulnerability · Source |
| CVE-2021-37600 | suse_vex | SUSE CVE CVE-2021-37600 | known affected: 424 known not affected: 178 recommended: 1276 | 2026-10-17T01:35:50+00:00 | Vulnerability · Source |
| CVE-2021-37620 | suse_vex | SUSE CVE CVE-2021-37620 | known affected: 9 recommended: 198 | 2026-10-17T01:35:48+00:00 | Vulnerability · Source |
| CVE-2021-37621 | suse_vex | SUSE CVE CVE-2021-37621 | known affected: 0 known not affected: 57 recommended: 180 | 2026-10-17T01:35:47+00:00 | Vulnerability · Source |
| CVE-2021-37714 | suse_vex | SUSE CVE CVE-2021-37714 | recommended: 112 | 2026-10-17T01:35:46+00:00 | Vulnerability · Source |
| CVE-2021-37750 | suse_vex | SUSE CVE CVE-2021-37750 | known affected: 367 known not affected: 365 recommended: 508 | 2026-10-17T01:35:44+00:00 | Vulnerability · Source |
| CVE-2021-38160 | suse_vex | SUSE CVE CVE-2021-38160 | known affected: 311 known not affected: 61 recommended: 1724 | 2026-10-17T01:35:42+00:00 | Vulnerability · Source |
| CVE-2021-38166 | suse_vex | SUSE CVE CVE-2021-38166 | known affected: 326 known not affected: 340 recommended: 751 | 2026-10-17T01:35:41+00:00 | Vulnerability · Source |
| CVE-2021-38185 | suse_vex | SUSE CVE CVE-2021-38185 | known affected: 306 recommended: 329 | 2026-10-17T01:35:40+00:00 | Vulnerability · Source |
| CVE-2021-38191 | suse_vex | SUSE CVE CVE-2021-38191 | recommended: 22 | 2026-10-17T01:35:38+00:00 | Vulnerability · Source |
| CVE-2021-38202 | suse_vex | SUSE CVE CVE-2021-38202 | known affected: 0 known not affected: 342 | 2026-10-17T01:35:37+00:00 | Vulnerability · Source |
| CVE-2021-38204 | suse_vex | SUSE CVE CVE-2021-38204 | known affected: 311 known not affected: 98 recommended: 1370 | 2026-10-17T01:35:36+00:00 | Vulnerability · Source |
| CVE-2021-38208 | suse_vex | SUSE CVE CVE-2021-38208 | known affected: 357 known not affected: 139 recommended: 799 | 2026-10-17T01:35:34+00:00 | Vulnerability · Source |
| CVE-2021-38297 | suse_vex | SUSE CVE CVE-2021-38297 | known affected: 356 known not affected: 8 recommended: 343 | 2026-10-17T01:35:33+00:00 | Vulnerability · Source |
| CVE-2021-38300 | suse_vex | SUSE CVE CVE-2021-38300 | known affected: 0 known not affected: 338 | 2026-10-17T01:35:32+00:00 | Vulnerability · Source |
| CVE-2021-38491 | suse_vex | SUSE CVE CVE-2021-38491 | recommended: 9 | 2026-10-17T01:35:30+00:00 | Vulnerability · Source |
| CVE-2021-38501 | suse_vex | SUSE CVE CVE-2021-38501 | known affected: 1 recommended: 485 | 2026-10-17T01:35:29+00:00 | Vulnerability · Source |
| CVE-2021-38506 | suse_vex | SUSE CVE CVE-2021-38506 | known affected: 1 recommended: 416 | 2026-10-17T01:35:27+00:00 | Vulnerability · Source |
| CVE-2021-38509 | suse_vex | SUSE CVE CVE-2021-38509 | known affected: 1 recommended: 416 | 2026-10-17T01:35:26+00:00 | Vulnerability · Source |
| CVE-2021-38510 | suse_vex | SUSE CVE CVE-2021-38510 | known affected: 1 recommended: 412 | 2026-10-17T01:35:25+00:00 | Vulnerability · Source |
| CVE-2021-38578 | suse_vex | SUSE CVE CVE-2021-38578 | known affected: 11 known not affected: 16 recommended: 205 | 2026-10-17T01:35:23+00:00 | Vulnerability · Source |
| CVE-2021-38604 | suse_vex | SUSE CVE CVE-2021-38604 | known affected: 0 known not affected: 705 | 2026-10-17T01:35:22+00:00 | Vulnerability · Source |
| CVE-2021-39242 | suse_vex | SUSE CVE CVE-2021-39242 | known affected: 0 known not affected: 15 recommended: 8 | 2026-10-17T01:35:21+00:00 | Vulnerability · Source |
| CVE-2021-39252 | suse_vex | SUSE CVE CVE-2021-39252 | recommended: 146 | 2026-10-17T01:35:19+00:00 | Vulnerability · Source |
| CVE-2021-39255 | suse_vex | SUSE CVE CVE-2021-39255 | recommended: 151 | 2026-10-17T01:35:18+00:00 | Vulnerability · Source |
| CVE-2021-39258 | suse_vex | SUSE CVE CVE-2021-39258 | recommended: 151 | 2026-10-17T01:35:17+00:00 | Vulnerability · Source |
| CVE-2021-39259 | suse_vex | SUSE CVE CVE-2021-39259 | recommended: 146 | 2026-10-17T01:35:15+00:00 | Vulnerability · Source |
| CVE-2021-39263 | suse_vex | SUSE CVE CVE-2021-39263 | recommended: 146 | 2026-10-17T01:35:14+00:00 | Vulnerability · Source |
| CVE-2021-39272 | suse_vex | SUSE CVE CVE-2021-39272 | known affected: 2 recommended: 121 | 2026-10-17T01:35:13+00:00 | Vulnerability · Source |
| CVE-2021-39648 | suse_vex | SUSE CVE CVE-2021-39648 | known affected: 338 known not affected: 121 recommended: 971 | 2026-10-17T01:35:11+00:00 | Vulnerability · Source |
| CVE-2021-39656 | suse_vex | SUSE CVE CVE-2021-39656 | known affected: 0 known not affected: 388 | 2026-10-17T01:35:10+00:00 | Vulnerability · Source |
| CVE-2021-39657 | suse_vex | SUSE CVE CVE-2021-39657 | known affected: 338 known not affected: 64 recommended: 980 | 2026-10-17T01:35:09+00:00 | Vulnerability · Source |
| CVE-2021-39713 | suse_vex | SUSE CVE CVE-2021-39713 | known affected: 391 known not affected: 154 recommended: 434 | 2026-10-17T01:35:07+00:00 | Vulnerability · Source |