VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104633 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2021-42739 | suse_vex | SUSE CVE CVE-2021-42739 | known affected: 323 known not affected: 65 recommended: 1630 | 2026-10-17T01:34:20+00:00 | Vulnerability · Source |
| CVE-2021-42762 | suse_vex | SUSE CVE CVE-2021-42762 | known affected: 47 recommended: 929 | 2026-10-17T01:34:18+00:00 | Vulnerability · Source |
| CVE-2021-42771 | suse_vex | SUSE CVE CVE-2021-42771 | known affected: 352 recommended: 255 | 2026-10-17T01:34:17+00:00 | Vulnerability · Source |
| CVE-2021-42780 | suse_vex | SUSE CVE CVE-2021-42780 | known affected: 8 known not affected: 8 recommended: 92 | 2026-10-17T01:34:16+00:00 | Vulnerability · Source |
| CVE-2021-43057 | suse_vex | SUSE CVE CVE-2021-43057 | known affected: 0 known not affected: 340 recommended: 335 | 2026-10-17T01:34:14+00:00 | Vulnerability · Source |
| CVE-2021-43389 | suse_vex | SUSE CVE CVE-2021-43389 | known affected: 264 known not affected: 74 recommended: 1619 | 2026-10-17T01:34:12+00:00 | Vulnerability · Source |
| CVE-2021-43396 | suse_vex | SUSE CVE CVE-2021-43396 | known affected: 0 known not affected: 219 | 2026-10-17T01:34:11+00:00 | Vulnerability · Source |
| CVE-2021-43519 | suse_vex | SUSE CVE CVE-2021-43519 | known affected: 20 known not affected: 179 recommended: 33 | 2026-10-17T01:34:10+00:00 | Vulnerability · Source |
| CVE-2021-43527 | suse_vex | SUSE CVE CVE-2021-43527 | known affected: 327 recommended: 1865 | 2026-10-17T01:34:08+00:00 | Vulnerability · Source |
| CVE-2021-43538 | suse_vex | SUSE CVE CVE-2021-43538 | known affected: 1 recommended: 424 | 2026-10-17T01:34:06+00:00 | Vulnerability · Source |
| CVE-2021-43541 | suse_vex | SUSE CVE CVE-2021-43541 | known affected: 1 recommended: 424 | 2026-10-17T01:34:05+00:00 | Vulnerability · Source |
| CVE-2021-43545 | suse_vex | SUSE CVE CVE-2021-43545 | known affected: 1 recommended: 424 | 2026-10-17T01:34:03+00:00 | Vulnerability · Source |
| CVE-2021-43565 | suse_vex | SUSE CVE CVE-2021-43565 | known affected: 350 known not affected: 48 recommended: 546 | 2026-10-17T01:34:01+00:00 | Vulnerability · Source |
| CVE-2021-43618 | suse_vex | SUSE CVE CVE-2021-43618 | known affected: 407 recommended: 371 | 2026-10-17T01:33:59+00:00 | Vulnerability · Source |
| CVE-2021-43784 | suse_vex | SUSE CVE CVE-2021-43784 | known affected: 332 known not affected: 68 recommended: 125 | 2026-10-17T01:33:58+00:00 | Vulnerability · Source |
| CVE-2021-43818 | suse_vex | SUSE CVE CVE-2021-43818 | known affected: 394 recommended: 331 | 2026-10-17T01:33:56+00:00 | Vulnerability · Source |
| CVE-2021-43860 | suse_vex | SUSE CVE CVE-2021-43860 | known affected: 0 known not affected: 48 recommended: 340 | 2026-10-17T01:33:55+00:00 | Vulnerability · Source |
| CVE-2021-44224 | suse_vex | SUSE CVE CVE-2021-44224 | known affected: 395 known not affected: 7 recommended: 506 | 2026-10-17T01:33:53+00:00 | Vulnerability · Source |
| CVE-2021-44225 | suse_vex | SUSE CVE CVE-2021-44225 | recommended: 21 | 2026-10-17T01:33:52+00:00 | Vulnerability · Source |
| CVE-2021-44879 | suse_vex | SUSE CVE CVE-2021-44879 | known affected: 207 known not affected: 99 recommended: 1446 | 2026-10-17T01:33:50+00:00 | Vulnerability · Source |
| CVE-2021-45078 | suse_vex | SUSE CVE CVE-2021-45078 | known affected: 395 recommended: 462 | 2026-10-17T01:33:49+00:00 | Vulnerability · Source |
| CVE-2021-45079 | suse_vex | SUSE CVE CVE-2021-45079 | known affected: 1 recommended: 416 | 2026-10-17T01:33:47+00:00 | Vulnerability · Source |
| CVE-2021-45095 | suse_vex | SUSE CVE CVE-2021-45095 | known affected: 338 known not affected: 57 recommended: 1344 | 2026-10-17T01:33:46+00:00 | Vulnerability · Source |
| CVE-2021-45100 | suse_vex | SUSE CVE CVE-2021-45100 | known affected: 0 known not affected: 388 | 2026-10-17T01:33:44+00:00 | Vulnerability · Source |
| CVE-2021-45261 | suse_vex | SUSE CVE CVE-2021-45261 | known affected: 444 recommended: 18 | 2026-10-17T01:33:43+00:00 | Vulnerability · Source |
| CVE-2021-45469 | suse_vex | SUSE CVE CVE-2021-45469 | known affected: 0 known not affected: 439 | 2026-10-17T01:33:42+00:00 | Vulnerability · Source |
| CVE-2021-45482 | suse_vex | SUSE CVE CVE-2021-45482 | known affected: 0 known not affected: 99 recommended: 929 | 2026-10-17T01:33:40+00:00 | Vulnerability · Source |
| CVE-2021-45940 | suse_vex | SUSE CVE CVE-2021-45940 | known affected: 0 known not affected: 34 recommended: 40 | 2026-10-17T01:33:39+00:00 | Vulnerability · Source |
| CVE-2021-45949 | suse_vex | SUSE CVE CVE-2021-45949 | known affected: 1 known not affected: 8 recommended: 163 | 2026-10-17T01:33:38+00:00 | Vulnerability · Source |
| CVE-2021-45958 | suse_vex | SUSE CVE CVE-2021-45958 | known affected: 36 recommended: 41 | 2026-10-17T01:33:37+00:00 | Vulnerability · Source |
| CVE-2021-45960 | suse_vex | SUSE CVE CVE-2021-45960 | known affected: 330 known not affected: 32 recommended: 377 | 2026-10-17T01:33:35+00:00 | Vulnerability · Source |
| CVE-2021-46059 | suse_vex | SUSE CVE CVE-2021-46059 | known affected: 341 known not affected: 30 recommended: 407 | 2026-10-17T01:33:34+00:00 | Vulnerability · Source |