VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283445 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48657 | suse_vex | SUSE CVE CVE-2022-48657 | known affected: 265 known not affected: 202 recommended: 462 | 2026-07-25T17:20:43+00:00 | Vulnerability · Source |
| CVE-2022-48658 | suse_vex | SUSE CVE CVE-2022-48658 | known affected: 377 known not affected: 263 recommended: 318 | 2026-07-25T17:20:41+00:00 | Vulnerability · Source |
| CVE-2022-48662 | suse_vex | SUSE CVE CVE-2022-48662 | known affected: 265 known not affected: 217 recommended: 522 | 2026-07-25T17:20:40+00:00 | Vulnerability · Source |
| CVE-2022-48664 | suse_vex | SUSE CVE CVE-2022-48664 | known affected: 131 known not affected: 80 recommended: 493 | 2026-07-25T17:20:38+00:00 | Vulnerability · Source |
| CVE-2022-48665 | suse_vex | SUSE CVE CVE-2022-48665 | known not affected: 288 | 2026-07-25T17:20:37+00:00 | Vulnerability · Source |
| CVE-2022-48668 | suse_vex | SUSE CVE CVE-2022-48668 | known affected: 320 known not affected: 145 recommended: 532 | 2026-07-25T17:20:36+00:00 | Vulnerability · Source |
| CVE-2022-48669 | suse_vex | SUSE CVE CVE-2022-48669 | known affected: 419 known not affected: 208 recommended: 546 | 2026-07-25T17:20:34+00:00 | Vulnerability · Source |
| CVE-2022-48672 | suse_vex | SUSE CVE CVE-2022-48672 | known affected: 354 known not affected: 79 recommended: 618 | 2026-07-25T17:20:33+00:00 | Vulnerability · Source |
| CVE-2022-48673 | suse_vex | SUSE CVE CVE-2022-48673 | known affected: 280 known not affected: 157 recommended: 592 | 2026-07-25T17:20:31+00:00 | Vulnerability · Source |
| CVE-2022-48687 | suse_vex | SUSE CVE CVE-2022-48687 | known affected: 16 known not affected: 140 recommended: 536 | 2026-07-25T17:20:30+00:00 | Vulnerability · Source |
| CVE-2022-48691 | suse_vex | SUSE CVE CVE-2022-48691 | known affected: 426 known not affected: 185 recommended: 234 | 2026-07-25T17:20:28+00:00 | Vulnerability · Source |
| CVE-2022-48694 | suse_vex | SUSE CVE CVE-2022-48694 | known affected: 270 known not affected: 225 recommended: 457 | 2026-07-25T17:20:27+00:00 | Vulnerability · Source |
| CVE-2022-48698 | suse_vex | SUSE CVE CVE-2022-48698 | known affected: 529 known not affected: 115 recommended: 318 | 2026-07-25T17:20:25+00:00 | Vulnerability · Source |
| CVE-2022-48701 | suse_vex | SUSE CVE CVE-2022-48701 | known affected: 324 known not affected: 74 recommended: 692 | 2026-07-25T17:20:23+00:00 | Vulnerability · Source |
| CVE-2022-48705 | suse_vex | SUSE CVE CVE-2022-48705 | known affected: 315 known not affected: 268 recommended: 313 | 2026-07-25T17:20:22+00:00 | Vulnerability · Source |
| CVE-2022-48706 | suse_vex | SUSE CVE CVE-2022-48706 | known affected: 340 known not affected: 277 recommended: 288 | 2026-07-25T17:20:20+00:00 | Vulnerability · Source |
| CVE-2022-48709 | suse_vex | SUSE CVE CVE-2022-48709 | known affected: 275 known not affected: 217 recommended: 452 | 2026-07-25T17:20:19+00:00 | Vulnerability · Source |
| CVE-2022-48711 | suse_vex | SUSE CVE CVE-2022-48711 | known not affected: 163 recommended: 526 | 2026-07-25T17:20:17+00:00 | Vulnerability · Source |
| CVE-2022-48712 | suse_vex | SUSE CVE CVE-2022-48712 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-25T17:20:16+00:00 | Vulnerability · Source |
| CVE-2022-48713 | suse_vex | SUSE CVE CVE-2022-48713 | known affected: 295 known not affected: 205 recommended: 428 | 2026-07-25T17:20:14+00:00 | Vulnerability · Source |
| CVE-2022-48714 | suse_vex | SUSE CVE CVE-2022-48714 | known affected: 409 known not affected: 169 recommended: 298 | 2026-07-25T17:20:13+00:00 | Vulnerability · Source |
| CVE-2022-48718 | suse_vex | SUSE CVE CVE-2022-48718 | known affected: 330 known not affected: 256 recommended: 298 | 2026-07-25T17:20:11+00:00 | Vulnerability · Source |
| CVE-2022-48724 | suse_vex | SUSE CVE CVE-2022-48724 | known affected: 347 known not affected: 146 recommended: 482 | 2026-07-25T17:20:10+00:00 | Vulnerability · Source |
| CVE-2022-48729 | suse_vex | SUSE CVE CVE-2022-48729 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-25T17:20:09+00:00 | Vulnerability · Source |
| CVE-2022-48732 | suse_vex | SUSE CVE CVE-2022-48732 | known affected: 416 known not affected: 70 recommended: 554 | 2026-07-25T17:20:07+00:00 | Vulnerability · Source |
| CVE-2022-48736 | suse_vex | SUSE CVE CVE-2022-48736 | known affected: 324 known not affected: 66 recommended: 482 | 2026-07-25T17:20:06+00:00 | Vulnerability · Source |
| CVE-2022-48738 | suse_vex | SUSE CVE CVE-2022-48738 | known affected: 450 known not affected: 125 recommended: 524 | 2026-07-25T17:20:04+00:00 | Vulnerability · Source |
| CVE-2022-48739 | suse_vex | SUSE CVE CVE-2022-48739 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-25T17:20:03+00:00 | Vulnerability · Source |
| CVE-2022-48746 | suse_vex | SUSE CVE CVE-2022-48746 | known affected: 324 known not affected: 169 recommended: 482 | 2026-07-25T17:20:01+00:00 | Vulnerability · Source |
| CVE-2022-48747 | suse_vex | SUSE CVE CVE-2022-48747 | known affected: 324 known not affected: 169 recommended: 502 | 2026-07-25T17:20:00+00:00 | Vulnerability · Source |
| CVE-2022-48754 | suse_vex | SUSE CVE CVE-2022-48754 | known affected: 364 known not affected: 122 recommended: 572 | 2026-07-25T17:19:58+00:00 | Vulnerability · Source |
| CVE-2022-48755 | suse_vex | SUSE CVE CVE-2022-48755 | known affected: 550 known not affected: 86 recommended: 298 | 2026-07-25T17:19:57+00:00 | Vulnerability · Source |
| CVE-2022-48756 | suse_vex | SUSE CVE CVE-2022-48756 | known affected: 420 known not affected: 66 recommended: 568 | 2026-07-25T17:19:55+00:00 | Vulnerability · Source |
| CVE-2022-48757 | suse_vex | SUSE CVE CVE-2022-48757 | known affected: 353 known not affected: 139 recommended: 20 | 2026-07-25T17:19:54+00:00 | Vulnerability · Source |
| CVE-2022-48763 | suse_vex | SUSE CVE CVE-2022-48763 | known affected: 330 known not affected: 205 recommended: 391 | 2026-07-25T17:19:53+00:00 | Vulnerability · Source |
| CVE-2022-48766 | suse_vex | SUSE CVE CVE-2022-48766 | known affected: 393 known not affected: 193 recommended: 298 | 2026-07-25T17:19:51+00:00 | Vulnerability · Source |
| CVE-2022-48767 | suse_vex | SUSE CVE CVE-2022-48767 | known affected: 347 known not affected: 146 recommended: 482 | 2026-07-25T17:19:50+00:00 | Vulnerability · Source |
| CVE-2022-48769 | suse_vex | SUSE CVE CVE-2022-48769 | known affected: 463 known not affected: 71 recommended: 475 | 2026-07-25T17:19:48+00:00 | Vulnerability · Source |
| CVE-2022-48776 | suse_vex | SUSE CVE CVE-2022-48776 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:47+00:00 | Vulnerability · Source |
| CVE-2022-48778 | suse_vex | SUSE CVE CVE-2022-48778 | known affected: 295 known not affected: 201 recommended: 511 | 2026-07-25T17:19:45+00:00 | Vulnerability · Source |
| CVE-2022-48779 | suse_vex | SUSE CVE CVE-2022-48779 | known not affected: 318 | 2026-07-25T17:19:44+00:00 | Vulnerability · Source |
| CVE-2022-48780 | suse_vex | SUSE CVE CVE-2022-48780 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:42+00:00 | Vulnerability · Source |
| CVE-2022-48781 | suse_vex | SUSE CVE CVE-2022-48781 | known not affected: 318 | 2026-07-25T17:19:40+00:00 | Vulnerability · Source |
| CVE-2022-48785 | suse_vex | SUSE CVE CVE-2022-48785 | known affected: 391 known not affected: 245 recommended: 298 | 2026-07-25T17:19:39+00:00 | Vulnerability · Source |
| CVE-2022-48791 | suse_vex | SUSE CVE CVE-2022-48791 | known affected: 364 known not affected: 76 recommended: 679 | 2026-07-25T17:19:38+00:00 | Vulnerability · Source |
| CVE-2022-48794 | suse_vex | SUSE CVE CVE-2022-48794 | known affected: 295 known not affected: 184 recommended: 496 | 2026-07-25T17:19:36+00:00 | Vulnerability · Source |
| CVE-2022-48795 | suse_vex | SUSE CVE CVE-2022-48795 | known not affected: 318 | 2026-07-25T17:19:35+00:00 | Vulnerability · Source |
| CVE-2022-48796 | suse_vex | SUSE CVE CVE-2022-48796 | known affected: 366 known not affected: 136 recommended: 426 | 2026-07-25T17:19:33+00:00 | Vulnerability · Source |
| CVE-2022-48800 | suse_vex | SUSE CVE CVE-2022-48800 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:32+00:00 | Vulnerability · Source |
| CVE-2022-48803 | suse_vex | SUSE CVE CVE-2022-48803 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:30+00:00 | Vulnerability · Source |