VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291314 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48668 | suse_vex | SUSE CVE CVE-2022-48668 | known affected: 320 known not affected: 145 recommended: 532 | 2026-08-14T01:26:13+00:00 | Vulnerability · Source |
| CVE-2022-48673 | suse_vex | SUSE CVE CVE-2022-48673 | known affected: 280 known not affected: 157 recommended: 592 | 2026-08-14T01:26:11+00:00 | Vulnerability · Source |
| CVE-2022-48686 | suse_vex | SUSE CVE CVE-2022-48686 | known affected: 281 known not affected: 151 recommended: 670 | 2026-08-14T01:26:09+00:00 | Vulnerability · Source |
| CVE-2022-48688 | suse_vex | SUSE CVE CVE-2022-48688 | known affected: 303 known not affected: 79 recommended: 527 | 2026-08-14T01:26:06+00:00 | Vulnerability · Source |
| CVE-2022-48709 | suse_vex | SUSE CVE CVE-2022-48709 | known affected: 275 known not affected: 217 recommended: 452 | 2026-08-14T01:26:04+00:00 | Vulnerability · Source |
| CVE-2022-48711 | suse_vex | SUSE CVE CVE-2022-48711 | known not affected: 163 recommended: 526 | 2026-08-14T01:26:02+00:00 | Vulnerability · Source |
| CVE-2022-48713 | suse_vex | SUSE CVE CVE-2022-48713 | known affected: 295 known not affected: 205 recommended: 428 | 2026-08-14T01:26:01+00:00 | Vulnerability · Source |
| CVE-2022-48716 | suse_vex | SUSE CVE CVE-2022-48716 | known affected: 391 known not affected: 245 recommended: 298 | 2026-08-14T01:25:59+00:00 | Vulnerability · Source |
| CVE-2022-48725 | suse_vex | SUSE CVE CVE-2022-48725 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-14T01:25:58+00:00 | Vulnerability · Source |
| CVE-2022-48730 | suse_vex | SUSE CVE CVE-2022-48730 | known affected: 324 known not affected: 169 recommended: 484 | 2026-08-14T01:25:56+00:00 | Vulnerability · Source |
| CVE-2022-48738 | suse_vex | SUSE CVE CVE-2022-48738 | known affected: 450 known not affected: 125 recommended: 524 | 2026-08-14T01:25:54+00:00 | Vulnerability · Source |
| CVE-2022-48741 | suse_vex | SUSE CVE CVE-2022-48741 | known not affected: 318 | 2026-08-14T01:25:53+00:00 | Vulnerability · Source |
| CVE-2022-48743 | suse_vex | SUSE CVE CVE-2022-48743 | known affected: 471 known not affected: 76 recommended: 524 | 2026-08-14T01:25:51+00:00 | Vulnerability · Source |
| CVE-2022-48753 | suse_vex | SUSE CVE CVE-2022-48753 | known affected: 330 known not affected: 256 recommended: 298 | 2026-08-14T01:25:49+00:00 | Vulnerability · Source |
| CVE-2022-48756 | suse_vex | SUSE CVE CVE-2022-48756 | known affected: 420 known not affected: 66 recommended: 568 | 2026-08-14T01:25:48+00:00 | Vulnerability · Source |
| CVE-2022-48759 | suse_vex | SUSE CVE CVE-2022-48759 | known affected: 416 known not affected: 70 recommended: 552 | 2026-08-14T01:25:46+00:00 | Vulnerability · Source |
| CVE-2022-48760 | suse_vex | SUSE CVE CVE-2022-48760 | known affected: 383 known not affected: 76 recommended: 644 | 2026-08-14T01:25:45+00:00 | Vulnerability · Source |
| CVE-2022-48761 | suse_vex | SUSE CVE CVE-2022-48761 | known affected: 464 known not affected: 60 recommended: 475 | 2026-08-14T01:25:43+00:00 | Vulnerability · Source |
| CVE-2022-48767 | suse_vex | SUSE CVE CVE-2022-48767 | known affected: 347 known not affected: 146 recommended: 482 | 2026-08-14T01:25:42+00:00 | Vulnerability · Source |
| CVE-2022-48773 | suse_vex | SUSE CVE CVE-2022-48773 | known affected: 350 known not affected: 146 recommended: 446 | 2026-08-14T01:25:40+00:00 | Vulnerability · Source |
| CVE-2022-48775 | suse_vex | SUSE CVE CVE-2022-48775 | known affected: 377 known not affected: 98 recommended: 595 | 2026-08-14T01:25:38+00:00 | Vulnerability · Source |
| CVE-2022-48776 | suse_vex | SUSE CVE CVE-2022-48776 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:37+00:00 | Vulnerability · Source |
| CVE-2022-48780 | suse_vex | SUSE CVE CVE-2022-48780 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:35+00:00 | Vulnerability · Source |
| CVE-2022-48785 | suse_vex | SUSE CVE CVE-2022-48785 | known affected: 391 known not affected: 245 recommended: 298 | 2026-08-14T01:25:33+00:00 | Vulnerability · Source |
| CVE-2022-48787 | suse_vex | SUSE CVE CVE-2022-48787 | known affected: 295 known not affected: 201 recommended: 511 | 2026-08-14T01:25:32+00:00 | Vulnerability · Source |
| CVE-2022-48789 | suse_vex | SUSE CVE CVE-2022-48789 | known affected: 361 known not affected: 139 recommended: 605 | 2026-08-14T01:25:30+00:00 | Vulnerability · Source |
| CVE-2022-48792 | suse_vex | SUSE CVE CVE-2022-48792 | known affected: 347 known not affected: 72 recommended: 679 | 2026-08-14T01:25:29+00:00 | Vulnerability · Source |
| CVE-2022-48793 | suse_vex | SUSE CVE CVE-2022-48793 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:27+00:00 | Vulnerability · Source |
| CVE-2022-48799 | suse_vex | SUSE CVE CVE-2022-48799 | known affected: 420 known not affected: 81 recommended: 496 | 2026-08-14T01:25:25+00:00 | Vulnerability · Source |
| CVE-2022-48801 | suse_vex | SUSE CVE CVE-2022-48801 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:24+00:00 | Vulnerability · Source |
| CVE-2022-48806 | suse_vex | SUSE CVE CVE-2022-48806 | known affected: 327 known not affected: 169 recommended: 426 | 2026-08-14T01:25:22+00:00 | Vulnerability · Source |
| CVE-2022-48807 | suse_vex | SUSE CVE CVE-2022-48807 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:20+00:00 | Vulnerability · Source |
| CVE-2022-48809 | suse_vex | SUSE CVE CVE-2022-48809 | known affected: 554 known not affected: 82 recommended: 338 | 2026-08-14T01:25:19+00:00 | Vulnerability · Source |
| CVE-2022-48815 | suse_vex | SUSE CVE CVE-2022-48815 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:17+00:00 | Vulnerability · Source |
| CVE-2022-48817 | suse_vex | SUSE CVE CVE-2022-48817 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:16+00:00 | Vulnerability · Source |
| CVE-2022-48821 | suse_vex | SUSE CVE CVE-2022-48821 | known affected: 292 known not affected: 147 recommended: 558 | 2026-08-14T01:25:14+00:00 | Vulnerability · Source |
| CVE-2022-48823 | suse_vex | SUSE CVE CVE-2022-48823 | known affected: 379 known not affected: 116 recommended: 581 | 2026-08-14T01:25:12+00:00 | Vulnerability · Source |
| CVE-2022-48825 | suse_vex | SUSE CVE CVE-2022-48825 | known affected: 407 known not affected: 66 recommended: 426 | 2026-08-14T01:25:11+00:00 | Vulnerability · Source |
| CVE-2022-48827 | suse_vex | SUSE CVE CVE-2022-48827 | known affected: 383 known not affected: 92 recommended: 595 | 2026-08-14T01:25:09+00:00 | Vulnerability · Source |
| CVE-2022-48831 | suse_vex | SUSE CVE CVE-2022-48831 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:08+00:00 | Vulnerability · Source |
| CVE-2022-48836 | suse_vex | SUSE CVE CVE-2022-48836 | known affected: 381 known not affected: 94 recommended: 615 | 2026-08-14T01:25:06+00:00 | Vulnerability · Source |
| CVE-2022-48841 | suse_vex | SUSE CVE CVE-2022-48841 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:05+00:00 | Vulnerability · Source |
| CVE-2022-48842 | suse_vex | SUSE CVE CVE-2022-48842 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-14T01:25:03+00:00 | Vulnerability · Source |
| CVE-2022-48847 | suse_vex | SUSE CVE CVE-2022-48847 | known not affected: 205 recommended: 327 | 2026-08-14T01:25:02+00:00 | Vulnerability · Source |
| CVE-2022-48856 | suse_vex | SUSE CVE CVE-2022-48856 | known affected: 318 known not affected: 178 recommended: 511 | 2026-08-14T01:25:00+00:00 | Vulnerability · Source |
| CVE-2022-48860 | suse_vex | SUSE CVE CVE-2022-48860 | known affected: 442 known not affected: 70 recommended: 510 | 2026-08-14T01:24:59+00:00 | Vulnerability · Source |
| CVE-2022-48865 | suse_vex | SUSE CVE CVE-2022-48865 | known affected: 524 known not affected: 86 recommended: 358 | 2026-08-14T01:24:57+00:00 | Vulnerability · Source |
| CVE-2022-48870 | suse_vex | SUSE CVE CVE-2022-48870 | known affected: 310 known not affected: 195 recommended: 411 | 2026-08-14T01:24:56+00:00 | Vulnerability · Source |
| CVE-2022-48873 | suse_vex | SUSE CVE CVE-2022-48873 | known affected: 310 known not affected: 142 recommended: 540 | 2026-08-14T01:24:54+00:00 | Vulnerability · Source |
| CVE-2022-48880 | suse_vex | SUSE CVE CVE-2022-48880 | known affected: 310 known not affected: 196 recommended: 411 | 2026-08-14T01:24:53+00:00 | Vulnerability · Source |