VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
103222 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2021-39801 | suse_vex | SUSE CVE CVE-2021-39801 | known affected: 0 known not affected: 418 | 2026-10-17T01:35:06+00:00 | Vulnerability · Source |
| CVE-2021-39922 | suse_vex | SUSE CVE CVE-2021-39922 | known affected: 20 recommended: 288 | 2026-10-17T01:35:05+00:00 | Vulnerability · Source |
| CVE-2021-39924 | suse_vex | SUSE CVE CVE-2021-39924 | known affected: 20 recommended: 288 | 2026-10-17T01:35:03+00:00 | Vulnerability · Source |
| CVE-2021-39926 | suse_vex | SUSE CVE CVE-2021-39926 | known affected: 20 recommended: 288 | 2026-10-17T01:35:02+00:00 | Vulnerability · Source |
| CVE-2021-40346 | suse_vex | SUSE CVE CVE-2021-40346 | known affected: 0 known not affected: 11 recommended: 15 | 2026-10-17T01:35:01+00:00 | Vulnerability · Source |
| CVE-2021-40528 | suse_vex | SUSE CVE CVE-2021-40528 | known affected: 16 known not affected: 303 recommended: 50 | 2026-10-17T01:34:59+00:00 | Vulnerability · Source |
| CVE-2021-40633 | suse_vex | SUSE CVE CVE-2021-40633 | known affected: 444 known not affected: 98 recommended: 105 | 2026-10-17T01:34:58+00:00 | Vulnerability · Source |
| CVE-2021-41073 | suse_vex | SUSE CVE CVE-2021-41073 | known affected: 0 known not affected: 340 recommended: 335 | 2026-10-17T01:34:56+00:00 | Vulnerability · Source |
| CVE-2021-41089 | suse_vex | SUSE CVE CVE-2021-41089 | known affected: 388 recommended: 453 | 2026-10-17T01:34:55+00:00 | Vulnerability · Source |
| CVE-2021-41091 | suse_vex | SUSE CVE CVE-2021-41091 | known affected: 50 recommended: 387 | 2026-10-17T01:34:54+00:00 | Vulnerability · Source |
| CVE-2021-41092 | suse_vex | SUSE CVE CVE-2021-41092 | known affected: 367 recommended: 474 | 2026-10-17T01:34:52+00:00 | Vulnerability · Source |
| CVE-2021-41103 | suse_vex | SUSE CVE CVE-2021-41103 | known affected: 367 recommended: 494 | 2026-10-17T01:34:51+00:00 | Vulnerability · Source |
| CVE-2021-41116 | suse_vex | SUSE CVE CVE-2021-41116 | recommended: 8 | 2026-10-17T01:34:49+00:00 | Vulnerability · Source |
| CVE-2021-41190 | suse_vex | SUSE CVE CVE-2021-41190 | known affected: 389 known not affected: 16 recommended: 617 | 2026-10-17T01:34:48+00:00 | Vulnerability · Source |
| CVE-2021-41229 | suse_vex | SUSE CVE CVE-2021-41229 | known affected: 0 known not affected: 301 recommended: 105 | 2026-10-17T01:34:46+00:00 | Vulnerability · Source |
| CVE-2021-41244 | suse_vex | SUSE CVE CVE-2021-41244 | known affected: 0 known not affected: 5 recommended: 232 | 2026-10-17T01:34:45+00:00 | Vulnerability · Source |
| CVE-2021-41773 | suse_vex | SUSE CVE CVE-2021-41773 | known affected: 0 known not affected: 247 recommended: 54 | 2026-10-17T01:34:42+00:00 | Vulnerability · Source |
| CVE-2021-41816 | suse_vex | SUSE CVE CVE-2021-41816 | known affected: 0 known not affected: 235 recommended: 90 | 2026-10-17T01:34:41+00:00 | Vulnerability · Source |
| CVE-2021-41817 | suse_vex | SUSE CVE CVE-2021-41817 | known affected: 356 known not affected: 130 recommended: 505 | 2026-10-17T01:34:39+00:00 | Vulnerability · Source |
| CVE-2021-41945 | suse_vex | SUSE CVE CVE-2021-41945 | recommended: 16 | 2026-10-17T01:34:38+00:00 | Vulnerability · Source |
| CVE-2021-41991 | suse_vex | SUSE CVE CVE-2021-41991 | known affected: 1 recommended: 439 | 2026-10-17T01:34:37+00:00 | Vulnerability · Source |
| CVE-2021-42375 | suse_vex | SUSE CVE CVE-2021-42375 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:35+00:00 | Vulnerability · Source |
| CVE-2021-42376 | suse_vex | SUSE CVE CVE-2021-42376 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:34+00:00 | Vulnerability · Source |
| CVE-2021-42378 | suse_vex | SUSE CVE CVE-2021-42378 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:33+00:00 | Vulnerability · Source |
| CVE-2021-42380 | suse_vex | SUSE CVE CVE-2021-42380 | known affected: 4 known not affected: 10 recommended: 151 | 2026-10-17T01:34:31+00:00 | Vulnerability · Source |
| CVE-2021-42381 | suse_vex | SUSE CVE CVE-2021-42381 | known affected: 4 known not affected: 10 recommended: 138 | 2026-10-17T01:34:30+00:00 | Vulnerability · Source |
| CVE-2021-42382 | suse_vex | SUSE CVE CVE-2021-42382 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:29+00:00 | Vulnerability · Source |
| CVE-2021-42384 | suse_vex | SUSE CVE CVE-2021-42384 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:27+00:00 | Vulnerability · Source |
| CVE-2021-42385 | suse_vex | SUSE CVE CVE-2021-42385 | known affected: 4 known not affected: 10 recommended: 138 | 2026-10-17T01:34:26+00:00 | Vulnerability · Source |
| CVE-2021-42386 | suse_vex | SUSE CVE CVE-2021-42386 | known affected: 4 known not affected: 10 recommended: 134 | 2026-10-17T01:34:25+00:00 | Vulnerability · Source |
| CVE-2021-42523 | suse_vex | SUSE CVE CVE-2021-42523 | recommended: 347 | 2026-10-17T01:34:24+00:00 | Vulnerability · Source |
| CVE-2021-42715 | suse_vex | SUSE CVE CVE-2021-42715 | recommended: 62 | 2026-10-17T01:34:23+00:00 | Vulnerability · Source |
| CVE-2021-42716 | suse_vex | SUSE CVE CVE-2021-42716 | recommended: 64 | 2026-10-17T01:34:21+00:00 | Vulnerability · Source |