VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288586 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-15219 | suse_vex | SUSE CVE CVE-2019-15219 | known affected: 133 known not affected: 84 recommended: 914 | 2026-08-04T00:04:27+00:00 | Vulnerability · Source |
| CVE-2019-17371 | suse_vex | SUSE CVE CVE-2019-17371 | known affected: 6 known not affected: 270 | 2026-08-04T00:04:21+00:00 | Vulnerability · Source |
| CVE-2019-17498 | suse_vex | SUSE CVE CVE-2019-17498 | known affected: 450 recommended: 296 | 2026-08-04T00:04:19+00:00 | Vulnerability · Source |
| CVE-2020-0430 | suse_vex | SUSE CVE CVE-2020-0430 | known affected: 511 known not affected: 316 recommended: 479 | 2026-08-04T00:04:11+00:00 | Vulnerability · Source |
| CVE-2020-0432 | suse_vex | SUSE CVE CVE-2020-0432 | known affected: 449 known not affected: 56 recommended: 1519 | 2026-08-04T00:04:08+00:00 | Vulnerability · Source |
| CVE-2020-6096 | suse_vex | SUSE CVE CVE-2020-6096 | known not affected: 384 recommended: 216 | 2026-08-04T00:04:04+00:00 | Vulnerability · Source |
| CVE-2020-8623 | suse_vex | SUSE CVE CVE-2020-8623 | known affected: 320 known not affected: 150 recommended: 995 | 2026-08-04T00:03:58+00:00 | Vulnerability · Source |
| CVE-2020-10700 | suse_vex | SUSE CVE CVE-2020-10700 | known affected: 320 known not affected: 1677 recommended: 2493 | 2026-08-04T00:03:55+00:00 | Vulnerability · Source |
| CVE-2020-12362 | suse_vex | SUSE CVE CVE-2020-12362 | known affected: 304 known not affected: 359 recommended: 948 | 2026-08-04T00:03:50+00:00 | Vulnerability · Source |
| CVE-2020-14339 | suse_vex | SUSE CVE CVE-2020-14339 | known affected: 555 known not affected: 473 recommended: 1554 | 2026-08-04T00:03:45+00:00 | Vulnerability · Source |
| CVE-2020-14387 | suse_vex | SUSE CVE CVE-2020-14387 | known not affected: 48 recommended: 50 | 2026-08-04T00:03:42+00:00 | Vulnerability · Source |
| CVE-2020-19131 | suse_vex | SUSE CVE CVE-2020-19131 | known affected: 395 known not affected: 15 recommended: 278 | 2026-08-04T00:03:38+00:00 | Vulnerability · Source |
| CVE-2020-24165 | suse_vex | SUSE CVE CVE-2020-24165 | known not affected: 895 | 2026-08-04T00:03:34+00:00 | Vulnerability · Source |
| CVE-2020-25643 | suse_vex | SUSE CVE CVE-2020-25643 | known affected: 320 known not affected: 112 recommended: 1621 | 2026-08-04T00:03:31+00:00 | Vulnerability · Source |
| CVE-2020-25674 | suse_vex | SUSE CVE CVE-2020-25674 | known not affected: 4 recommended: 762 | 2026-08-04T00:03:28+00:00 | Vulnerability · Source |
| CVE-2020-27067 | suse_vex | SUSE CVE CVE-2020-27067 | known not affected: 353 | 2026-08-04T00:03:25+00:00 | Vulnerability · Source |
| CVE-2020-27619 | suse_vex | SUSE CVE CVE-2020-27619 | known affected: 299 known not affected: 235 recommended: 899 | 2026-08-04T00:03:22+00:00 | Vulnerability · Source |
| CVE-2020-29485 | suse_vex | SUSE CVE CVE-2020-29485 | known not affected: 334 | 2026-08-04T00:03:19+00:00 | Vulnerability · Source |
| CVE-2021-4008 | suse_vex | SUSE CVE CVE-2021-4008 | known affected: 408 known not affected: 29 recommended: 301 | 2026-08-04T00:03:06+00:00 | Vulnerability · Source |
| CVE-2021-28690 | suse_vex | SUSE CVE CVE-2021-28690 | known affected: 312 known not affected: 46 recommended: 496 | 2026-08-04T00:02:48+00:00 | Vulnerability · Source |
| CVE-2021-39713 | suse_vex | SUSE CVE CVE-2021-39713 | known affected: 391 known not affected: 148 recommended: 434 | 2026-08-04T00:02:38+00:00 | Vulnerability · Source |
| CVE-2021-46744 | suse_vex | SUSE CVE CVE-2021-46744 | known affected: 1 known not affected: 24 recommended: 1324 | 2026-08-04T00:02:34+00:00 | Vulnerability · Source |
| CVE-2021-47568 | suse_vex | SUSE CVE CVE-2021-47568 | known not affected: 330 | 2026-08-04T00:02:24+00:00 | Vulnerability · Source |
| CVE-2022-1116 | suse_vex | SUSE CVE CVE-2022-1116 | known affected: 368 known not affected: 304 recommended: 736 | 2026-08-04T00:02:12+00:00 | Vulnerability · Source |
| CVE-2022-2319 | suse_vex | SUSE CVE CVE-2022-2319 | known affected: 401 recommended: 277 | 2026-08-04T00:02:06+00:00 | Vulnerability · Source |
| CVE-2022-3296 | suse_vex | SUSE CVE CVE-2022-3296 | known affected: 260 recommended: 464 | 2026-08-04T00:02:00+00:00 | Vulnerability · Source |
| CVE-2022-3715 | suse_vex | SUSE CVE CVE-2022-3715 | known not affected: 350 recommended: 2 | 2026-08-04T00:01:51+00:00 | Vulnerability · Source |
| CVE-2022-20009 | suse_vex | SUSE CVE CVE-2022-20009 | known not affected: 390 | 2026-08-04T00:01:47+00:00 | Vulnerability · Source |
| CVE-2022-22822 | suse_vex | SUSE CVE CVE-2022-22822 | known affected: 330 known not affected: 32 recommended: 386 | 2026-08-04T00:01:40+00:00 | Vulnerability · Source |
| CVE-2022-22824 | suse_vex | SUSE CVE CVE-2022-22824 | known affected: 330 known not affected: 32 recommended: 386 | 2026-08-04T00:01:37+00:00 | Vulnerability · Source |
| CVE-2022-22827 | suse_vex | SUSE CVE CVE-2022-22827 | known affected: 330 known not affected: 32 recommended: 384 | 2026-08-04T00:01:34+00:00 | Vulnerability · Source |
| CVE-2022-23960 | suse_vex | SUSE CVE CVE-2022-23960 | known affected: 394 known not affected: 401 recommended: 818 | 2026-08-04T00:01:28+00:00 | Vulnerability · Source |
| CVE-2022-28737 | suse_vex | SUSE CVE CVE-2022-28737 | known affected: 294 recommended: 187 | 2026-08-04T00:01:23+00:00 | Vulnerability · Source |
| CVE-2022-29155 | suse_vex | SUSE CVE CVE-2022-29155 | known affected: 350 recommended: 730 | 2026-08-04T00:01:21+00:00 | Vulnerability · Source |
| CVE-2022-48952 | suse_vex | SUSE CVE CVE-2022-48952 | known affected: 208 known not affected: 221 | 2026-08-04T00:01:07+00:00 | Vulnerability · Source |
| CVE-2022-48996 | suse_vex | SUSE CVE CVE-2022-48996 | known not affected: 379 | 2026-08-04T00:01:06+00:00 | Vulnerability · Source |
| CVE-2022-49255 | suse_vex | SUSE CVE CVE-2022-49255 | known not affected: 352 | 2026-08-04T00:01:00+00:00 | Vulnerability · Source |
| CVE-2022-49390 | suse_vex | SUSE CVE CVE-2022-49390 | known affected: 513 known not affected: 165 recommended: 126 | 2026-08-04T00:00:57+00:00 | Vulnerability · Source |
| CVE-2022-49743 | suse_vex | SUSE CVE CVE-2022-49743 | known affected: 112 known not affected: 272 | 2026-08-04T00:00:52+00:00 | Vulnerability · Source |
| CVE-2022-49798 | suse_vex | SUSE CVE CVE-2022-49798 | known not affected: 402 | 2026-08-04T00:00:51+00:00 | Vulnerability · Source |
| CVE-2022-49884 | suse_vex | SUSE CVE CVE-2022-49884 | known not affected: 397 | 2026-08-04T00:00:49+00:00 | Vulnerability · Source |
| CVE-2022-50182 | suse_vex | SUSE CVE CVE-2022-50182 | known affected: 55 known not affected: 346 | 2026-08-04T00:00:42+00:00 | Vulnerability · Source |
| CVE-2022-50298 | suse_vex | SUSE CVE CVE-2022-50298 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-04T00:00:38+00:00 | Vulnerability · Source |
| CVE-2022-50676 | suse_vex | SUSE CVE CVE-2022-50676 | known affected: 608 known not affected: 204 recommended: 23 | 2026-08-04T00:00:35+00:00 | Vulnerability · Source |
| CVE-2023-2861 | suse_vex | SUSE CVE CVE-2023-2861 | known affected: 485 recommended: 1461 | 2026-08-04T00:00:28+00:00 | Vulnerability · Source |
| CVE-2023-25193 | suse_vex | SUSE CVE CVE-2023-25193 | known affected: 434 recommended: 1026 | 2026-08-04T00:00:17+00:00 | Vulnerability · Source |
| CVE-2023-40590 | suse_vex | SUSE CVE CVE-2023-40590 | known not affected: 3 recommended: 12 | 2026-08-04T00:00:10+00:00 | Vulnerability · Source |
| CVE-2023-43040 | suse_vex | SUSE CVE CVE-2023-43040 | known not affected: 746 | 2026-08-04T00:00:08+00:00 | Vulnerability · Source |
| CVE-2023-52613 | suse_vex | SUSE CVE CVE-2023-52613 | known not affected: 292 recommended: 59 | 2026-08-03T23:59:59+00:00 | Vulnerability · Source |
| CVE-2023-52643 | suse_vex | SUSE CVE CVE-2023-52643 | known affected: 376 known not affected: 267 recommended: 519 | 2026-08-03T23:59:57+00:00 | Vulnerability · Source |