VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283762 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2021-38205 | suse_vex | SUSE CVE CVE-2021-38205 | known affected: 317 known not affected: 259 recommended: 997 | 2026-07-25T17:39:32+00:00 | Vulnerability · Source |
| CVE-2021-38507 | suse_vex | SUSE CVE CVE-2021-38507 | known affected: 1 recommended: 416 | 2026-07-25T17:39:29+00:00 | Vulnerability · Source |
| CVE-2021-38508 | suse_vex | SUSE CVE CVE-2021-38508 | known affected: 1 recommended: 416 | 2026-07-25T17:39:28+00:00 | Vulnerability · Source |
| CVE-2021-39257 | suse_vex | SUSE CVE CVE-2021-39257 | recommended: 144 | 2026-07-25T17:39:26+00:00 | Vulnerability · Source |
| CVE-2021-39275 | suse_vex | SUSE CVE CVE-2021-39275 | known affected: 419 known not affected: 1 recommended: 421 | 2026-07-25T17:39:25+00:00 | Vulnerability · Source |
| CVE-2021-39359 | suse_vex | SUSE CVE CVE-2021-39359 | known affected: 19 known not affected: 8 recommended: 106 | 2026-07-25T17:39:24+00:00 | Vulnerability · Source |
| CVE-2021-39365 | suse_vex | SUSE CVE CVE-2021-39365 | known affected: 25 recommended: 448 | 2026-07-25T17:39:22+00:00 | Vulnerability · Source |
| CVE-2021-39636 | suse_vex | SUSE CVE CVE-2021-39636 | known not affected: 365 | 2026-07-25T17:39:21+00:00 | Vulnerability · Source |
| CVE-2021-39648 | suse_vex | SUSE CVE CVE-2021-39648 | known affected: 338 known not affected: 121 recommended: 971 | 2026-07-25T17:39:19+00:00 | Vulnerability · Source |
| CVE-2021-39656 | suse_vex | SUSE CVE CVE-2021-39656 | known not affected: 365 | 2026-07-25T17:39:18+00:00 | Vulnerability · Source |
| CVE-2021-39686 | suse_vex | SUSE CVE CVE-2021-39686 | known not affected: 401 | 2026-07-25T17:39:16+00:00 | Vulnerability · Source |
| CVE-2021-39713 | suse_vex | SUSE CVE CVE-2021-39713 | known affected: 391 known not affected: 148 recommended: 434 | 2026-07-25T17:39:15+00:00 | Vulnerability · Source |
| CVE-2021-39714 | suse_vex | SUSE CVE CVE-2021-39714 | known not affected: 401 | 2026-07-25T17:39:13+00:00 | Vulnerability · Source |
| CVE-2021-39922 | suse_vex | SUSE CVE CVE-2021-39922 | known affected: 20 recommended: 288 | 2026-07-25T17:39:12+00:00 | Vulnerability · Source |
| CVE-2021-39928 | suse_vex | SUSE CVE CVE-2021-39928 | known affected: 20 recommended: 288 | 2026-07-25T17:39:11+00:00 | Vulnerability · Source |
| CVE-2021-39929 | suse_vex | SUSE CVE CVE-2021-39929 | known affected: 20 recommended: 288 | 2026-07-25T17:39:09+00:00 | Vulnerability · Source |
| CVE-2021-40211 | suse_vex | SUSE CVE CVE-2021-40211 | known not affected: 389 recommended: 12 | 2026-07-25T17:39:08+00:00 | Vulnerability · Source |
| CVE-2021-40438 | suse_vex | SUSE CVE CVE-2021-40438 | known affected: 419 known not affected: 5 recommended: 398 | 2026-07-25T17:39:07+00:00 | Vulnerability · Source |
| CVE-2021-40490 | suse_vex | SUSE CVE CVE-2021-40490 | known affected: 322 known not affected: 82 recommended: 1147 | 2026-07-25T17:39:05+00:00 | Vulnerability · Source |
| CVE-2021-41091 | suse_vex | SUSE CVE CVE-2021-41091 | known affected: 45 recommended: 381 | 2026-07-25T17:39:03+00:00 | Vulnerability · Source |
| CVE-2021-41229 | suse_vex | SUSE CVE CVE-2021-41229 | known not affected: 293 recommended: 105 | 2026-07-25T17:39:02+00:00 | Vulnerability · Source |
| CVE-2021-41524 | suse_vex | SUSE CVE CVE-2021-41524 | known not affected: 235 | 2026-07-25T17:39:00+00:00 | Vulnerability · Source |
| CVE-2021-41773 | suse_vex | SUSE CVE CVE-2021-41773 | known not affected: 235 recommended: 47 | 2026-07-25T17:38:59+00:00 | Vulnerability · Source |
| CVE-2021-41819 | suse_vex | SUSE CVE CVE-2021-41819 | known affected: 425 recommended: 331 | 2026-07-25T17:38:58+00:00 | Vulnerability · Source |
| CVE-2021-42008 | suse_vex | SUSE CVE CVE-2021-42008 | known affected: 323 known not affected: 53 recommended: 1079 | 2026-07-25T17:38:56+00:00 | Vulnerability · Source |
| CVE-2021-42252 | suse_vex | SUSE CVE CVE-2021-42252 | known affected: 323 known not affected: 178 recommended: 1287 | 2026-07-25T17:38:54+00:00 | Vulnerability · Source |
| CVE-2021-42327 | suse_vex | SUSE CVE CVE-2021-42327 | known affected: 354 known not affected: 381 recommended: 457 | 2026-07-25T17:38:53+00:00 | Vulnerability · Source |
| CVE-2021-42340 | suse_vex | SUSE CVE CVE-2021-42340 | known not affected: 308 recommended: 2 | 2026-07-25T17:38:52+00:00 | Vulnerability · Source |
| CVE-2021-42375 | suse_vex | SUSE CVE CVE-2021-42375 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:50+00:00 | Vulnerability · Source |
| CVE-2021-42376 | suse_vex | SUSE CVE CVE-2021-42376 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:49+00:00 | Vulnerability · Source |
| CVE-2021-42377 | suse_vex | SUSE CVE CVE-2021-42377 | known affected: 4 known not affected: 8 recommended: 136 | 2026-07-25T17:38:48+00:00 | Vulnerability · Source |
| CVE-2021-42379 | suse_vex | SUSE CVE CVE-2021-42379 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:47+00:00 | Vulnerability · Source |
| CVE-2021-42382 | suse_vex | SUSE CVE CVE-2021-42382 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:45+00:00 | Vulnerability · Source |
| CVE-2021-42383 | suse_vex | SUSE CVE CVE-2021-42383 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:44+00:00 | Vulnerability · Source |
| CVE-2021-42384 | suse_vex | SUSE CVE CVE-2021-42384 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:43+00:00 | Vulnerability · Source |
| CVE-2021-42386 | suse_vex | SUSE CVE CVE-2021-42386 | known affected: 4 known not affected: 8 recommended: 132 | 2026-07-25T17:38:41+00:00 | Vulnerability · Source |
| CVE-2021-42523 | suse_vex | SUSE CVE CVE-2021-42523 | recommended: 344 | 2026-07-25T17:38:40+00:00 | Vulnerability · Source |
| CVE-2021-42717 | suse_vex | SUSE CVE CVE-2021-42717 | known not affected: 60 recommended: 24 | 2026-07-25T17:38:39+00:00 | Vulnerability · Source |
| CVE-2021-42762 | suse_vex | SUSE CVE CVE-2021-42762 | known affected: 38 recommended: 941 | 2026-07-25T17:38:37+00:00 | Vulnerability · Source |
| CVE-2021-42778 | suse_vex | SUSE CVE CVE-2021-42778 | known not affected: 47 | 2026-07-25T17:38:36+00:00 | Vulnerability · Source |
| CVE-2021-42779 | suse_vex | SUSE CVE CVE-2021-42779 | known affected: 7 known not affected: 27 recommended: 77 | 2026-07-25T17:38:35+00:00 | Vulnerability · Source |
| CVE-2021-42781 | suse_vex | SUSE CVE CVE-2021-42781 | known affected: 7 known not affected: 27 recommended: 77 | 2026-07-25T17:38:33+00:00 | Vulnerability · Source |
| CVE-2021-43057 | suse_vex | SUSE CVE CVE-2021-43057 | known not affected: 318 recommended: 364 | 2026-07-25T17:38:32+00:00 | Vulnerability · Source |
| CVE-2021-43331 | suse_vex | SUSE CVE CVE-2021-43331 | known affected: 3 recommended: 21 | 2026-07-25T17:38:31+00:00 | Vulnerability · Source |
| CVE-2021-43389 | suse_vex | SUSE CVE CVE-2021-43389 | known affected: 264 known not affected: 74 recommended: 1648 | 2026-07-25T17:38:29+00:00 | Vulnerability · Source |
| CVE-2021-43396 | suse_vex | SUSE CVE CVE-2021-43396 | known not affected: 193 | 2026-07-25T17:38:28+00:00 | Vulnerability · Source |
| CVE-2021-43527 | suse_vex | SUSE CVE CVE-2021-43527 | known affected: 327 recommended: 1873 | 2026-07-25T17:38:26+00:00 | Vulnerability · Source |
| CVE-2021-43537 | suse_vex | SUSE CVE CVE-2021-43537 | known affected: 1 recommended: 424 | 2026-07-25T17:38:24+00:00 | Vulnerability · Source |
| CVE-2021-43538 | suse_vex | SUSE CVE CVE-2021-43538 | known affected: 1 recommended: 424 | 2026-07-25T17:38:23+00:00 | Vulnerability · Source |
| CVE-2021-43541 | suse_vex | SUSE CVE CVE-2021-43541 | known affected: 1 recommended: 424 | 2026-07-25T17:38:21+00:00 | Vulnerability · Source |