VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290399 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2020-21681 | suse_vex | SUSE CVE CVE-2020-21681 | recommended: 47 | 2026-07-31T17:06:29+00:00 | Vulnerability · Source |
| CVE-2020-25692 | suse_vex | SUSE CVE CVE-2020-25692 | known affected: 392 recommended: 854 | 2026-07-31T17:06:23+00:00 | Vulnerability · Source |
| CVE-2020-29573 | suse_vex | SUSE CVE CVE-2020-29573 | known affected: 330 known not affected: 60 recommended: 1236 | 2026-07-31T17:06:15+00:00 | Vulnerability · Source |
| CVE-2021-0326 | suse_vex | SUSE CVE CVE-2021-0326 | known not affected: 3 recommended: 99 | 2026-07-31T17:06:12+00:00 | Vulnerability · Source |
| CVE-2021-1788 | suse_vex | SUSE CVE CVE-2021-1788 | recommended: 1118 | 2026-07-31T17:06:11+00:00 | Vulnerability · Source |
| CVE-2021-2372 | suse_vex | SUSE CVE CVE-2021-2372 | known not affected: 42 recommended: 467 | 2026-07-31T17:06:07+00:00 | Vulnerability · Source |
| CVE-2021-3639 | suse_vex | SUSE CVE CVE-2021-3639 | known affected: 1 recommended: 99 | 2026-07-31T17:06:05+00:00 | Vulnerability · Source |
| CVE-2021-3682 | suse_vex | SUSE CVE CVE-2021-3682 | known affected: 432 known not affected: 647 recommended: 1847 | 2026-07-31T17:06:03+00:00 | Vulnerability · Source |
| CVE-2021-3695 | suse_vex | SUSE CVE CVE-2021-3695 | known affected: 353 recommended: 724 | 2026-07-31T17:06:01+00:00 | Vulnerability · Source |
| CVE-2021-3999 | suse_vex | SUSE CVE CVE-2021-3999 | known affected: 339 recommended: 1452 | 2026-07-31T17:05:55+00:00 | Vulnerability · Source |
| CVE-2021-4069 | suse_vex | SUSE CVE CVE-2021-4069 | known affected: 363 known not affected: 15 recommended: 366 | 2026-07-31T17:05:52+00:00 | Vulnerability · Source |
| CVE-2021-20246 | suse_vex | SUSE CVE CVE-2021-20246 | known not affected: 130 recommended: 588 | 2026-07-31T17:05:49+00:00 | Vulnerability · Source |
| CVE-2021-20251 | suse_vex | SUSE CVE CVE-2021-20251 | known affected: 272 known not affected: 102 recommended: 2190 | 2026-07-31T17:05:47+00:00 | Vulnerability · Source |
| CVE-2021-23336 | suse_vex | SUSE CVE CVE-2021-23336 | known affected: 299 known not affected: 182 recommended: 2016 | 2026-07-31T17:05:44+00:00 | Vulnerability · Source |
| CVE-2021-25217 | suse_vex | SUSE CVE CVE-2021-25217 | known affected: 329 recommended: 473 | 2026-07-31T17:05:42+00:00 | Vulnerability · Source |
| CVE-2021-30846 | suse_vex | SUSE CVE CVE-2021-30846 | known affected: 38 known not affected: 10 recommended: 1023 | 2026-07-31T17:05:35+00:00 | Vulnerability · Source |
| CVE-2021-31535 | suse_vex | SUSE CVE CVE-2021-31535 | known affected: 403 recommended: 504 | 2026-07-31T17:05:33+00:00 | Vulnerability · Source |
| CVE-2021-34798 | suse_vex | SUSE CVE CVE-2021-34798 | known affected: 419 known not affected: 5 recommended: 396 | 2026-07-31T17:05:29+00:00 | Vulnerability · Source |
| CVE-2021-45469 | suse_vex | SUSE CVE CVE-2021-45469 | known not affected: 416 | 2026-07-31T17:05:17+00:00 | Vulnerability · Source |
| CVE-2021-46904 | suse_vex | SUSE CVE CVE-2021-46904 | known affected: 480 known not affected: 180 recommended: 264 | 2026-07-31T17:05:15+00:00 | Vulnerability · Source |
| CVE-2021-47279 | suse_vex | SUSE CVE CVE-2021-47279 | known not affected: 330 | 2026-07-31T17:05:10+00:00 | Vulnerability · Source |
| CVE-2022-1015 | suse_vex | SUSE CVE CVE-2022-1015 | known affected: 32 known not affected: 18 recommended: 364 | 2026-07-31T17:04:55+00:00 | Vulnerability · Source |
| CVE-2022-1651 | suse_vex | SUSE CVE CVE-2022-1651 | known affected: 257 known not affected: 339 recommended: 615 | 2026-07-31T17:04:51+00:00 | Vulnerability · Source |
| CVE-2022-3531 | suse_vex | SUSE CVE CVE-2022-3531 | known not affected: 327 | 2026-07-31T17:04:43+00:00 | Vulnerability · Source |
| CVE-2022-22620 | suse_vex | SUSE CVE CVE-2022-22620 | known affected: 1 known not affected: 9 recommended: 941 | 2026-07-31T17:04:35+00:00 | Vulnerability · Source |
| CVE-2022-22629 | suse_vex | SUSE CVE CVE-2022-22629 | known affected: 24 known not affected: 374 recommended: 952 | 2026-07-31T17:04:33+00:00 | Vulnerability · Source |
| CVE-2022-22737 | suse_vex | SUSE CVE CVE-2022-22737 | recommended: 413 | 2026-07-31T17:04:31+00:00 | Vulnerability · Source |
| CVE-2022-27666 | suse_vex | SUSE CVE CVE-2022-27666 | known not affected: 208 recommended: 1026 | 2026-07-31T17:04:26+00:00 | Vulnerability · Source |
| CVE-2022-34468 | suse_vex | SUSE CVE CVE-2022-34468 | known affected: 1 recommended: 482 | 2026-07-31T17:04:20+00:00 | Vulnerability · Source |
| CVE-2022-35948 | suse_vex | SUSE CVE CVE-2022-35948 | known not affected: 194 recommended: 128 | 2026-07-31T17:04:19+00:00 | Vulnerability · Source |
| CVE-2022-38238 | suse_vex | SUSE CVE CVE-2022-38238 | known not affected: 330 | 2026-07-31T17:04:16+00:00 | Vulnerability · Source |
| CVE-2022-38477 | suse_vex | SUSE CVE CVE-2022-38477 | known affected: 2 recommended: 461 | 2026-07-31T17:04:14+00:00 | Vulnerability · Source |
| CVE-2022-42890 | suse_vex | SUSE CVE CVE-2022-42890 | recommended: 71 | 2026-07-31T17:04:05+00:00 | Vulnerability · Source |
| CVE-2022-44792 | suse_vex | SUSE CVE CVE-2022-44792 | known affected: 36 known not affected: 2 recommended: 195 | 2026-07-31T17:04:03+00:00 | Vulnerability · Source |
| CVE-2022-46344 | suse_vex | SUSE CVE CVE-2022-46344 | known affected: 395 recommended: 309 | 2026-07-31T17:03:59+00:00 | Vulnerability · Source |
| CVE-2022-48770 | suse_vex | SUSE CVE CVE-2022-48770 | known affected: 434 known not affected: 202 recommended: 298 | 2026-07-31T17:03:55+00:00 | Vulnerability · Source |
| CVE-2022-48966 | suse_vex | SUSE CVE CVE-2022-48966 | known affected: 390 known not affected: 260 recommended: 311 | 2026-07-31T17:03:45+00:00 | Vulnerability · Source |
| CVE-2022-49048 | suse_vex | SUSE CVE CVE-2022-49048 | known affected: 112 known not affected: 240 | 2026-07-31T17:03:39+00:00 | Vulnerability · Source |
| CVE-2022-49192 | suse_vex | SUSE CVE CVE-2022-49192 | known not affected: 302 recommended: 70 | 2026-07-31T17:03:36+00:00 | Vulnerability · Source |
| CVE-2022-49245 | suse_vex | SUSE CVE CVE-2022-49245 | known not affected: 352 | 2026-07-31T17:03:33+00:00 | Vulnerability · Source |
| CVE-2022-49510 | suse_vex | SUSE CVE CVE-2022-49510 | known affected: 364 known not affected: 302 recommended: 100 | 2026-07-31T17:03:28+00:00 | Vulnerability · Source |
| CVE-2022-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-31T17:03:25+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known not affected: 397 | 2026-07-31T17:03:19+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 55 known not affected: 342 recommended: 27 | 2026-07-31T17:03:17+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 154 known not affected: 258 | 2026-07-31T17:03:16+00:00 | Vulnerability · Source |
| CVE-2022-50039 | suse_vex | SUSE CVE CVE-2022-50039 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-31T17:03:14+00:00 | Vulnerability · Source |
| CVE-2022-50113 | suse_vex | SUSE CVE CVE-2022-50113 | known not affected: 401 recommended: 47 | 2026-07-31T17:03:12+00:00 | Vulnerability · Source |
| CVE-2022-50639 | suse_vex | SUSE CVE CVE-2022-50639 | known not affected: 408 recommended: 29 | 2026-07-31T17:03:03+00:00 | Vulnerability · Source |
| CVE-2022-50645 | suse_vex | SUSE CVE CVE-2022-50645 | known affected: 191 known not affected: 217 recommended: 29 | 2026-07-31T17:03:01+00:00 | Vulnerability · Source |
| CVE-2022-50758 | suse_vex | SUSE CVE CVE-2022-50758 | known affected: 354 known not affected: 329 recommended: 200 | 2026-07-31T17:02:59+00:00 | Vulnerability · Source |