VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283447 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-48808 | suse_vex | SUSE CVE CVE-2022-48808 | known affected: 401 known not affected: 245 recommended: 288 | 2026-07-25T17:19:28+00:00 | Vulnerability · Source |
| CVE-2022-48813 | suse_vex | SUSE CVE CVE-2022-48813 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:27+00:00 | Vulnerability · Source |
| CVE-2022-48816 | suse_vex | SUSE CVE CVE-2022-48816 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:25+00:00 | Vulnerability · Source |
| CVE-2022-48821 | suse_vex | SUSE CVE CVE-2022-48821 | known affected: 292 known not affected: 147 recommended: 558 | 2026-07-25T17:19:24+00:00 | Vulnerability · Source |
| CVE-2022-48822 | suse_vex | SUSE CVE CVE-2022-48822 | known affected: 292 known not affected: 192 recommended: 584 | 2026-07-25T17:19:22+00:00 | Vulnerability · Source |
| CVE-2022-48823 | suse_vex | SUSE CVE CVE-2022-48823 | known affected: 379 known not affected: 116 recommended: 581 | 2026-07-25T17:19:21+00:00 | Vulnerability · Source |
| CVE-2022-48825 | suse_vex | SUSE CVE CVE-2022-48825 | known affected: 407 known not affected: 66 recommended: 426 | 2026-07-25T17:19:19+00:00 | Vulnerability · Source |
| CVE-2022-48826 | suse_vex | SUSE CVE CVE-2022-48826 | known affected: 405 known not affected: 71 recommended: 496 | 2026-07-25T17:19:17+00:00 | Vulnerability · Source |
| CVE-2022-48829 | suse_vex | SUSE CVE CVE-2022-48829 | known affected: 295 known not affected: 184 recommended: 510 | 2026-07-25T17:19:16+00:00 | Vulnerability · Source |
| CVE-2022-48833 | suse_vex | SUSE CVE CVE-2022-48833 | known not affected: 318 | 2026-07-25T17:19:15+00:00 | Vulnerability · Source |
| CVE-2022-48835 | suse_vex | SUSE CVE CVE-2022-48835 | known affected: 318 known not affected: 178 recommended: 511 | 2026-07-25T17:19:13+00:00 | Vulnerability · Source |
| CVE-2022-48836 | suse_vex | SUSE CVE CVE-2022-48836 | known affected: 381 known not affected: 94 recommended: 615 | 2026-07-25T17:19:11+00:00 | Vulnerability · Source |
| CVE-2022-48837 | suse_vex | SUSE CVE CVE-2022-48837 | known affected: 318 known not affected: 178 recommended: 511 | 2026-07-25T17:19:10+00:00 | Vulnerability · Source |