VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48792 | suse_vex | SUSE CVE CVE-2022-48792 | known affected: 387 known not affected: 69 recommended: 679 | 2026-10-16T14:36:44+00:00 | Vulnerability · Source |
| CVE-2022-48793 | suse_vex | SUSE CVE CVE-2022-48793 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:41+00:00 | Vulnerability · Source |
| CVE-2022-48795 | suse_vex | SUSE CVE CVE-2022-48795 | known not affected: 373 | 2026-10-16T14:36:39+00:00 | Vulnerability · Source |
| CVE-2022-48796 | suse_vex | SUSE CVE CVE-2022-48796 | known affected: 394 known not affected: 157 recommended: 426 | 2026-10-16T14:36:36+00:00 | Vulnerability · Source |
| CVE-2022-48797 | suse_vex | SUSE CVE CVE-2022-48797 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:34+00:00 | Vulnerability · Source |
| CVE-2022-48798 | suse_vex | SUSE CVE CVE-2022-48798 | known affected: 295 known not affected: 250 recommended: 511 | 2026-10-16T14:36:32+00:00 | Vulnerability · Source |
| CVE-2022-48799 | suse_vex | SUSE CVE CVE-2022-48799 | known affected: 472 known not affected: 78 recommended: 496 | 2026-10-16T14:36:30+00:00 | Vulnerability · Source |
| CVE-2022-48802 | suse_vex | SUSE CVE CVE-2022-48802 | known not affected: 451 recommended: 456 | 2026-10-16T14:36:24+00:00 | Vulnerability · Source |
| CVE-2022-48803 | suse_vex | SUSE CVE CVE-2022-48803 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:22+00:00 | Vulnerability · Source |
| CVE-2022-48804 | suse_vex | SUSE CVE CVE-2022-48804 | known affected: 478 known not affected: 70 recommended: 530 | 2026-10-16T14:36:20+00:00 | Vulnerability · Source |
| CVE-2022-48809 | suse_vex | SUSE CVE CVE-2022-48809 | known affected: 616 known not affected: 75 recommended: 338 | 2026-10-16T14:36:15+00:00 | Vulnerability · Source |
| CVE-2022-48810 | suse_vex | SUSE CVE CVE-2022-48810 | known affected: 580 known not affected: 75 recommended: 382 | 2026-10-16T14:36:13+00:00 | Vulnerability · Source |
| CVE-2022-48811 | suse_vex | SUSE CVE CVE-2022-48811 | known affected: 435 known not affected: 120 recommended: 581 | 2026-10-16T14:36:11+00:00 | Vulnerability · Source |
| CVE-2022-48815 | suse_vex | SUSE CVE CVE-2022-48815 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:08+00:00 | Vulnerability · Source |
| CVE-2022-48816 | suse_vex | SUSE CVE CVE-2022-48816 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:06+00:00 | Vulnerability · Source |
| CVE-2022-48818 | suse_vex | SUSE CVE CVE-2022-48818 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:01+00:00 | Vulnerability · Source |
| CVE-2022-48821 | suse_vex | SUSE CVE CVE-2022-48821 | known affected: 292 known not affected: 184 recommended: 558 | 2026-10-16T14:35:59+00:00 | Vulnerability · Source |
| CVE-2022-48822 | suse_vex | SUSE CVE CVE-2022-48822 | known affected: 292 known not affected: 235 recommended: 584 | 2026-10-16T14:35:56+00:00 | Vulnerability · Source |
| CVE-2022-48827 | suse_vex | SUSE CVE CVE-2022-48827 | known affected: 433 known not affected: 91 recommended: 595 | 2026-10-16T14:35:51+00:00 | Vulnerability · Source |
| CVE-2022-48828 | suse_vex | SUSE CVE CVE-2022-48828 | known affected: 478 known not affected: 69 recommended: 510 | 2026-10-16T14:35:48+00:00 | Vulnerability · Source |
| CVE-2022-48829 | suse_vex | SUSE CVE CVE-2022-48829 | known affected: 295 known not affected: 232 recommended: 510 | 2026-10-16T14:35:46+00:00 | Vulnerability · Source |
| CVE-2022-48831 | suse_vex | SUSE CVE CVE-2022-48831 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:35:43+00:00 | Vulnerability · Source |
| CVE-2022-48833 | suse_vex | SUSE CVE CVE-2022-48833 | known not affected: 373 | 2026-10-16T14:35:40+00:00 | Vulnerability · Source |
| CVE-2022-48835 | suse_vex | SUSE CVE CVE-2022-48835 | known affected: 324 known not affected: 221 recommended: 511 | 2026-10-16T14:35:38+00:00 | Vulnerability · Source |
| CVE-2022-48837 | suse_vex | SUSE CVE CVE-2022-48837 | known affected: 324 known not affected: 221 recommended: 511 | 2026-10-16T14:35:35+00:00 | Vulnerability · Source |
| CVE-2022-48841 | suse_vex | SUSE CVE CVE-2022-48841 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:35:32+00:00 | Vulnerability · Source |
| CVE-2022-48842 | suse_vex | SUSE CVE CVE-2022-48842 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:35:29+00:00 | Vulnerability · Source |
| CVE-2022-48843 | suse_vex | SUSE CVE CVE-2022-48843 | known affected: 356 known not affected: 189 recommended: 511 | 2026-10-16T14:35:27+00:00 | Vulnerability · Source |
| CVE-2022-48847 | suse_vex | SUSE CVE CVE-2022-48847 | known not affected: 254 recommended: 327 | 2026-10-16T14:35:21+00:00 | Vulnerability · Source |
| CVE-2022-48850 | suse_vex | SUSE CVE CVE-2022-48850 | known affected: 586 known not affected: 69 recommended: 382 | 2026-10-16T14:35:19+00:00 | Vulnerability · Source |
| CVE-2022-48851 | suse_vex | SUSE CVE CVE-2022-48851 | known affected: 295 known not affected: 490 recommended: 511 | 2026-10-16T14:35:16+00:00 | Vulnerability · Source |
| CVE-2022-48852 | suse_vex | SUSE CVE CVE-2022-48852 | known affected: 550 known not affected: 147 recommended: 298 | 2026-10-16T14:35:13+00:00 | Vulnerability · Source |
| CVE-2022-48856 | suse_vex | SUSE CVE CVE-2022-48856 | known affected: 324 known not affected: 221 recommended: 511 | 2026-10-16T14:35:11+00:00 | Vulnerability · Source |
| CVE-2022-48857 | suse_vex | SUSE CVE CVE-2022-48857 | known affected: 427 known not affected: 97 recommended: 595 | 2026-10-16T14:35:09+00:00 | Vulnerability · Source |
| CVE-2022-48861 | suse_vex | SUSE CVE CVE-2022-48861 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:35:07+00:00 | Vulnerability · Source |
| CVE-2022-48862 | suse_vex | SUSE CVE CVE-2022-48862 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:35:04+00:00 | Vulnerability · Source |
| CVE-2022-48863 | suse_vex | SUSE CVE CVE-2022-48863 | known affected: 484 known not affected: 64 recommended: 510 | 2026-10-16T14:35:02+00:00 | Vulnerability · Source |
| CVE-2022-48864 | suse_vex | SUSE CVE CVE-2022-48864 | known affected: 330 known not affected: 311 recommended: 298 | 2026-10-16T14:34:59+00:00 | Vulnerability · Source |
| CVE-2022-48865 | suse_vex | SUSE CVE CVE-2022-48865 | known affected: 582 known not affected: 83 recommended: 358 | 2026-10-16T14:34:56+00:00 | Vulnerability · Source |
| CVE-2022-48866 | suse_vex | SUSE CVE CVE-2022-48866 | known affected: 295 known not affected: 254 recommended: 468 | 2026-10-16T14:34:54+00:00 | Vulnerability · Source |
| CVE-2022-48867 | suse_vex | SUSE CVE CVE-2022-48867 | known not affected: 371 | 2026-10-16T14:34:51+00:00 | Vulnerability · Source |
| CVE-2022-48868 | suse_vex | SUSE CVE CVE-2022-48868 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:34:48+00:00 | Vulnerability · Source |
| CVE-2022-48869 | suse_vex | SUSE CVE CVE-2022-48869 | known affected: 61 known not affected: 185 recommended: 327 | 2026-10-16T14:34:46+00:00 | Vulnerability · Source |
| CVE-2022-48870 | suse_vex | SUSE CVE CVE-2022-48870 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:34:43+00:00 | Vulnerability · Source |
| CVE-2022-48873 | suse_vex | SUSE CVE CVE-2022-48873 | known affected: 310 known not affected: 185 recommended: 540 | 2026-10-16T14:34:41+00:00 | Vulnerability · Source |
| CVE-2022-48874 | suse_vex | SUSE CVE CVE-2022-48874 | known not affected: 371 | 2026-10-16T14:34:38+00:00 | Vulnerability · Source |
| CVE-2022-48877 | suse_vex | SUSE CVE CVE-2022-48877 | known not affected: 610 | 2026-10-16T14:34:33+00:00 | Vulnerability · Source |
| CVE-2022-48880 | suse_vex | SUSE CVE CVE-2022-48880 | known affected: 310 known not affected: 251 recommended: 411 | 2026-10-16T14:34:27+00:00 | Vulnerability · Source |
| CVE-2022-48887 | suse_vex | SUSE CVE CVE-2022-48887 | known affected: 401 known not affected: 185 recommended: 288 | 2026-10-16T14:34:25+00:00 | Vulnerability · Source |
| CVE-2022-48891 | suse_vex | SUSE CVE CVE-2022-48891 | known affected: 425 known not affected: 218 recommended: 411 | 2026-10-16T14:34:22+00:00 | Vulnerability · Source |