VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100548 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-21444 | suse_vex | SUSE CVE CVE-2022-21444 | recommended: 24 | 2026-10-16T14:54:10+00:00 | Vulnerability · Source |
| CVE-2022-21449 | suse_vex | SUSE CVE CVE-2022-21449 | known affected: 1 known not affected: 490 recommended: 521 | 2026-10-16T14:54:08+00:00 | Vulnerability · Source |
| CVE-2022-21462 | suse_vex | SUSE CVE CVE-2022-21462 | recommended: 24 | 2026-10-16T14:54:06+00:00 | Vulnerability · Source |
| CVE-2022-21478 | suse_vex | SUSE CVE CVE-2022-21478 | recommended: 24 | 2026-10-16T14:54:04+00:00 | Vulnerability · Source |
| CVE-2022-21482 | suse_vex | SUSE CVE CVE-2022-21482 | No product status | 2026-10-16T14:54:02+00:00 | Vulnerability · Source |
| CVE-2022-21485 | suse_vex | SUSE CVE CVE-2022-21485 | No product status | 2026-10-16T14:54:00+00:00 | Vulnerability · Source |
| CVE-2022-21486 | suse_vex | SUSE CVE CVE-2022-21486 | No product status | 2026-10-16T14:53:59+00:00 | Vulnerability · Source |
| CVE-2022-21505 | suse_vex | SUSE CVE CVE-2022-21505 | known affected: 234 known not affected: 199 recommended: 1135 | 2026-10-16T14:53:57+00:00 | Vulnerability · Source |
| CVE-2022-21530 | suse_vex | SUSE CVE CVE-2022-21530 | recommended: 24 | 2026-10-16T14:53:55+00:00 | Vulnerability · Source |
| CVE-2022-21541 | suse_vex | SUSE CVE CVE-2022-21541 | known affected: 397 known not affected: 27 recommended: 1256 | 2026-10-16T14:53:53+00:00 | Vulnerability · Source |
| CVE-2022-21549 | suse_vex | SUSE CVE CVE-2022-21549 | known affected: 395 known not affected: 431 recommended: 537 | 2026-10-16T14:53:51+00:00 | Vulnerability · Source |
| CVE-2022-21599 | suse_vex | SUSE CVE CVE-2022-21599 | recommended: 25 | 2026-10-16T14:53:49+00:00 | Vulnerability · Source |
| CVE-2022-21619 | suse_vex | SUSE CVE CVE-2022-21619 | known affected: 396 recommended: 1197 | 2026-10-16T14:53:46+00:00 | Vulnerability · Source |
| CVE-2022-21624 | suse_vex | SUSE CVE CVE-2022-21624 | known affected: 396 recommended: 1197 | 2026-10-16T14:53:44+00:00 | Vulnerability · Source |
| CVE-2022-21682 | suse_vex | SUSE CVE CVE-2022-21682 | known affected: 0 known not affected: 56 recommended: 323 | 2026-10-16T14:53:42+00:00 | Vulnerability · Source |
| CVE-2022-21698 | suse_vex | SUSE CVE CVE-2022-21698 | known affected: 30 known not affected: 99 recommended: 641 | 2026-10-16T14:53:40+00:00 | Vulnerability · Source |
| CVE-2022-21702 | suse_vex | SUSE CVE CVE-2022-21702 | recommended: 165 | 2026-10-16T14:53:38+00:00 | Vulnerability · Source |
| CVE-2022-22576 | suse_vex | SUSE CVE CVE-2022-22576 | known affected: 263 known not affected: 56 recommended: 352 | 2026-10-16T14:53:36+00:00 | Vulnerability · Source |
| CVE-2022-22589 | suse_vex | SUSE CVE CVE-2022-22589 | known affected: 0 known not affected: 9 recommended: 929 | 2026-10-16T14:53:34+00:00 | Vulnerability · Source |
| CVE-2022-22592 | suse_vex | SUSE CVE CVE-2022-22592 | known affected: 0 known not affected: 9 recommended: 929 | 2026-10-16T14:53:32+00:00 | Vulnerability · Source |
| CVE-2022-22620 | suse_vex | SUSE CVE CVE-2022-22620 | known affected: 1 known not affected: 9 recommended: 929 | 2026-10-16T14:53:30+00:00 | Vulnerability · Source |
| CVE-2022-22720 | suse_vex | SUSE CVE CVE-2022-22720 | known affected: 394 known not affected: 76 recommended: 547 | 2026-10-16T14:53:28+00:00 | Vulnerability · Source |
| CVE-2022-22737 | suse_vex | SUSE CVE CVE-2022-22737 | recommended: 413 | 2026-10-16T14:53:26+00:00 | Vulnerability · Source |
| CVE-2022-22738 | suse_vex | SUSE CVE CVE-2022-22738 | recommended: 413 | 2026-10-16T14:53:24+00:00 | Vulnerability · Source |
| CVE-2022-22741 | suse_vex | SUSE CVE CVE-2022-22741 | recommended: 413 | 2026-10-16T14:53:22+00:00 | Vulnerability · Source |
| CVE-2022-22743 | suse_vex | SUSE CVE CVE-2022-22743 | recommended: 413 | 2026-10-16T14:53:20+00:00 | Vulnerability · Source |
| CVE-2022-22745 | suse_vex | SUSE CVE CVE-2022-22745 | recommended: 413 | 2026-10-16T14:53:18+00:00 | Vulnerability · Source |
| CVE-2022-22753 | suse_vex | SUSE CVE CVE-2022-22753 | recommended: 404 | 2026-10-16T14:53:16+00:00 | Vulnerability · Source |
| CVE-2022-22756 | suse_vex | SUSE CVE CVE-2022-22756 | recommended: 408 | 2026-10-16T14:53:14+00:00 | Vulnerability · Source |
| CVE-2022-22759 | suse_vex | SUSE CVE CVE-2022-22759 | recommended: 408 | 2026-10-16T14:53:11+00:00 | Vulnerability · Source |
| CVE-2022-22763 | suse_vex | SUSE CVE CVE-2022-22763 | recommended: 399 | 2026-10-16T14:53:08+00:00 | Vulnerability · Source |
| CVE-2022-22764 | suse_vex | SUSE CVE CVE-2022-22764 | recommended: 408 | 2026-10-16T14:53:06+00:00 | Vulnerability · Source |
| CVE-2022-22815 | suse_vex | SUSE CVE CVE-2022-22815 | known affected: 0 known not affected: 48 recommended: 111 | 2026-10-16T14:53:04+00:00 | Vulnerability · Source |
| CVE-2022-22822 | suse_vex | SUSE CVE CVE-2022-22822 | known affected: 330 known not affected: 32 recommended: 386 | 2026-10-16T14:53:01+00:00 | Vulnerability · Source |
| CVE-2022-22823 | suse_vex | SUSE CVE CVE-2022-22823 | known affected: 330 known not affected: 32 recommended: 386 | 2026-10-16T14:52:59+00:00 | Vulnerability · Source |
| CVE-2022-22824 | suse_vex | SUSE CVE CVE-2022-22824 | known affected: 330 known not affected: 32 recommended: 386 | 2026-10-16T14:52:57+00:00 | Vulnerability · Source |
| CVE-2022-22825 | suse_vex | SUSE CVE CVE-2022-22825 | known affected: 330 known not affected: 32 recommended: 384 | 2026-10-16T14:52:54+00:00 | Vulnerability · Source |
| CVE-2022-22826 | suse_vex | SUSE CVE CVE-2022-22826 | known affected: 330 known not affected: 32 recommended: 384 | 2026-10-16T14:52:52+00:00 | Vulnerability · Source |
| CVE-2022-22827 | suse_vex | SUSE CVE CVE-2022-22827 | known affected: 330 known not affected: 32 recommended: 384 | 2026-10-16T14:52:49+00:00 | Vulnerability · Source |
| CVE-2022-23041 | suse_vex | SUSE CVE CVE-2022-23041 | known affected: 344 known not affected: 65 recommended: 1298 | 2026-10-16T14:52:46+00:00 | Vulnerability · Source |
| CVE-2022-23042 | suse_vex | SUSE CVE CVE-2022-23042 | known affected: 344 known not affected: 65 recommended: 1298 | 2026-10-16T14:52:44+00:00 | Vulnerability · Source |
| CVE-2022-23181 | suse_vex | SUSE CVE CVE-2022-23181 | known affected: 439 recommended: 569 | 2026-10-16T14:52:42+00:00 | Vulnerability · Source |
| CVE-2022-23218 | suse_vex | SUSE CVE CVE-2022-23218 | known affected: 339 recommended: 1444 | 2026-10-16T14:52:40+00:00 | Vulnerability · Source |
| CVE-2022-23219 | suse_vex | SUSE CVE CVE-2022-23219 | known affected: 339 recommended: 1444 | 2026-10-16T14:52:37+00:00 | Vulnerability · Source |
| CVE-2022-23308 | suse_vex | SUSE CVE CVE-2022-23308 | known affected: 216 known not affected: 44 recommended: 663 | 2026-10-16T14:52:35+00:00 | Vulnerability · Source |
| CVE-2022-23491 | suse_vex | SUSE CVE CVE-2022-23491 | known affected: 321 known not affected: 83 recommended: 1075 | 2026-10-16T14:52:33+00:00 | Vulnerability · Source |
| CVE-2022-23521 | suse_vex | SUSE CVE CVE-2022-23521 | known affected: 1 known not affected: 141 recommended: 741 | 2026-10-16T14:52:31+00:00 | Vulnerability · Source |
| CVE-2022-23525 | suse_vex | SUSE CVE CVE-2022-23525 | known affected: 406 recommended: 100 | 2026-10-16T14:52:29+00:00 | Vulnerability · Source |
| CVE-2022-23527 | suse_vex | SUSE CVE CVE-2022-23527 | known affected: 20 recommended: 38 | 2026-10-16T14:52:28+00:00 | Vulnerability · Source |
| CVE-2022-23806 | suse_vex | SUSE CVE CVE-2022-23806 | known affected: 0 known not affected: 8 recommended: 298 | 2026-10-16T14:52:25+00:00 | Vulnerability · Source |