VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100576 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48713 | suse_vex | SUSE CVE CVE-2022-48713 | known affected: 295 known not affected: 254 recommended: 428 | 2026-10-16T14:38:21+00:00 | Vulnerability · Source |
| CVE-2022-48715 | suse_vex | SUSE CVE CVE-2022-48715 | known affected: 460 known not affected: 70 recommended: 566 | 2026-10-16T14:38:16+00:00 | Vulnerability · Source |
| CVE-2022-48717 | suse_vex | SUSE CVE CVE-2022-48717 | known affected: 353 known not affected: 183 recommended: 482 | 2026-10-16T14:38:11+00:00 | Vulnerability · Source |
| CVE-2022-48719 | suse_vex | SUSE CVE CVE-2022-48719 | known not affected: 373 | 2026-10-16T14:38:09+00:00 | Vulnerability · Source |
| CVE-2022-48722 | suse_vex | SUSE CVE CVE-2022-48722 | known affected: 446 known not affected: 83 recommended: 552 | 2026-10-16T14:38:06+00:00 | Vulnerability · Source |
| CVE-2022-48724 | suse_vex | SUSE CVE CVE-2022-48724 | known affected: 353 known not affected: 183 recommended: 482 | 2026-10-16T14:38:01+00:00 | Vulnerability · Source |
| CVE-2022-48725 | suse_vex | SUSE CVE CVE-2022-48725 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:58+00:00 | Vulnerability · Source |
| CVE-2022-48727 | suse_vex | SUSE CVE CVE-2022-48727 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:56+00:00 | Vulnerability · Source |
| CVE-2022-48730 | suse_vex | SUSE CVE CVE-2022-48730 | known affected: 324 known not affected: 212 recommended: 484 | 2026-10-16T14:37:48+00:00 | Vulnerability · Source |
| CVE-2022-48731 | suse_vex | SUSE CVE CVE-2022-48731 | known not affected: 318 | 2026-10-16T14:37:46+00:00 | Vulnerability · Source |
| CVE-2022-48735 | suse_vex | SUSE CVE CVE-2022-48735 | known affected: 362 known not affected: 118 recommended: 433 | 2026-10-16T14:37:41+00:00 | Vulnerability · Source |
| CVE-2022-48738 | suse_vex | SUSE CVE CVE-2022-48738 | known affected: 500 known not affected: 114 recommended: 524 | 2026-10-16T14:37:36+00:00 | Vulnerability · Source |
| CVE-2022-48745 | suse_vex | SUSE CVE CVE-2022-48745 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:31+00:00 | Vulnerability · Source |
| CVE-2022-48746 | suse_vex | SUSE CVE CVE-2022-48746 | known affected: 324 known not affected: 212 recommended: 482 | 2026-10-16T14:37:29+00:00 | Vulnerability · Source |
| CVE-2022-48747 | suse_vex | SUSE CVE CVE-2022-48747 | known affected: 324 known not affected: 212 recommended: 502 | 2026-10-16T14:37:27+00:00 | Vulnerability · Source |
| CVE-2022-48749 | suse_vex | SUSE CVE CVE-2022-48749 | known affected: 324 known not affected: 212 recommended: 484 | 2026-10-16T14:37:25+00:00 | Vulnerability · Source |
| CVE-2022-48751 | suse_vex | SUSE CVE CVE-2022-48751 | known affected: 473 known not affected: 110 recommended: 461 | 2026-10-16T14:37:22+00:00 | Vulnerability · Source |
| CVE-2022-48756 | suse_vex | SUSE CVE CVE-2022-48756 | known affected: 470 known not affected: 59 recommended: 568 | 2026-10-16T14:37:20+00:00 | Vulnerability · Source |
| CVE-2022-48757 | suse_vex | SUSE CVE CVE-2022-48757 | known affected: 433 known not affected: 125 recommended: 20 | 2026-10-16T14:37:17+00:00 | Vulnerability · Source |
| CVE-2022-48759 | suse_vex | SUSE CVE CVE-2022-48759 | known affected: 462 known not affected: 67 recommended: 552 | 2026-10-16T14:37:14+00:00 | Vulnerability · Source |
| CVE-2022-48761 | suse_vex | SUSE CVE CVE-2022-48761 | known affected: 520 known not affected: 53 recommended: 475 | 2026-10-16T14:37:12+00:00 | Vulnerability · Source |
| CVE-2022-48762 | suse_vex | SUSE CVE CVE-2022-48762 | known not affected: 373 | 2026-10-16T14:37:09+00:00 | Vulnerability · Source |
| CVE-2022-48763 | suse_vex | SUSE CVE CVE-2022-48763 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:07+00:00 | Vulnerability · Source |
| CVE-2022-48768 | suse_vex | SUSE CVE CVE-2022-48768 | known affected: 353 known not affected: 183 recommended: 482 | 2026-10-16T14:37:03+00:00 | Vulnerability · Source |
| CVE-2022-48776 | suse_vex | SUSE CVE CVE-2022-48776 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:55+00:00 | Vulnerability · Source |
| CVE-2022-48779 | suse_vex | SUSE CVE CVE-2022-48779 | known not affected: 373 | 2026-10-16T14:36:51+00:00 | Vulnerability · Source |
| CVE-2022-48784 | suse_vex | SUSE CVE CVE-2022-48784 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-16T14:36:49+00:00 | Vulnerability · Source |
| CVE-2022-48788 | suse_vex | SUSE CVE CVE-2022-48788 | known affected: 435 known not affected: 115 recommended: 619 | 2026-10-16T14:36:47+00:00 | Vulnerability · Source |
| 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 |