VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
290591 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-47007 | suse_vex | SUSE CVE CVE-2022-47007 | known affected: 10 known not affected: 224 | 2026-08-13T02:29:49+00:00 | Vulnerability · Source |
| CVE-2022-47520 | suse_vex | SUSE CVE CVE-2022-47520 | known affected: 272 known not affected: 175 recommended: 880 | 2026-08-13T02:29:47+00:00 | Vulnerability · Source |
| CVE-2022-47929 | suse_vex | SUSE CVE CVE-2022-47929 | known affected: 287 known not affected: 41 recommended: 1166 | 2026-08-13T02:29:46+00:00 | Vulnerability · Source |
| CVE-2022-47938 | suse_vex | SUSE CVE CVE-2022-47938 | known not affected: 362 | 2026-08-13T02:29:44+00:00 | Vulnerability · Source |
| CVE-2022-48338 | suse_vex | SUSE CVE CVE-2022-48338 | known not affected: 182 recommended: 176 | 2026-08-13T02:29:42+00:00 | Vulnerability · Source |
| CVE-2022-48630 | suse_vex | SUSE CVE CVE-2022-48630 | known affected: 260 known not affected: 200 recommended: 471 | 2026-08-13T02:29:39+00:00 | Vulnerability · Source |
| CVE-2022-48634 | suse_vex | SUSE CVE CVE-2022-48634 | known affected: 270 known not affected: 202 recommended: 457 | 2026-08-13T02:29:36+00:00 | Vulnerability · Source |
| CVE-2022-48641 | suse_vex | SUSE CVE CVE-2022-48641 | known not affected: 288 | 2026-08-13T02:29:34+00:00 | Vulnerability · Source |
| CVE-2022-48645 | suse_vex | SUSE CVE CVE-2022-48645 | known affected: 367 known not affected: 181 recommended: 288 | 2026-08-13T02:29:32+00:00 | Vulnerability · Source |
| CVE-2022-48646 | suse_vex | SUSE CVE CVE-2022-48646 | known affected: 357 known not affected: 225 recommended: 318 | 2026-08-13T02:29:30+00:00 | Vulnerability · Source |
| CVE-2022-48647 | suse_vex | SUSE CVE CVE-2022-48647 | known affected: 265 known not affected: 298 recommended: 462 | 2026-08-13T02:29:29+00:00 | Vulnerability · Source |
| CVE-2022-48656 | suse_vex | SUSE CVE CVE-2022-48656 | known affected: 265 known not affected: 202 recommended: 462 | 2026-08-13T02:29:27+00:00 | Vulnerability · Source |
| CVE-2022-48661 | suse_vex | SUSE CVE CVE-2022-48661 | known not affected: 288 | 2026-08-13T02:29:26+00:00 | Vulnerability · Source |
| CVE-2022-48675 | suse_vex | SUSE CVE CVE-2022-48675 | known affected: 270 known not affected: 225 recommended: 457 | 2026-08-13T02:29:21+00:00 | Vulnerability · Source |
| CVE-2022-48694 | suse_vex | SUSE CVE CVE-2022-48694 | known affected: 270 known not affected: 225 recommended: 457 | 2026-08-13T02:29:20+00:00 | Vulnerability · Source |
| CVE-2022-48698 | suse_vex | SUSE CVE CVE-2022-48698 | known affected: 529 known not affected: 115 recommended: 318 | 2026-08-13T02:29:18+00:00 | Vulnerability · Source |
| CVE-2022-48702 | suse_vex | SUSE CVE CVE-2022-48702 | known affected: 325 known not affected: 74 recommended: 632 | 2026-08-13T02:29:16+00:00 | Vulnerability · Source |
| CVE-2022-48703 | suse_vex | SUSE CVE CVE-2022-48703 | known affected: 270 known not affected: 225 recommended: 457 | 2026-08-13T02:29:15+00:00 | Vulnerability · Source |
| CVE-2022-48705 | suse_vex | SUSE CVE CVE-2022-48705 | known affected: 315 known not affected: 268 recommended: 313 | 2026-08-13T02:29:14+00:00 | Vulnerability · Source |
| CVE-2022-48706 | suse_vex | SUSE CVE CVE-2022-48706 | known affected: 340 known not affected: 277 recommended: 288 | 2026-08-13T02:29:13+00:00 | Vulnerability · Source |
| CVE-2022-48710 | suse_vex | SUSE CVE CVE-2022-48710 | known affected: 369 known not affected: 66 recommended: 627 | 2026-08-13T02:29:11+00:00 | Vulnerability · Source |
| CVE-2022-48712 | suse_vex | SUSE CVE CVE-2022-48712 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-13T02:29:10+00:00 | Vulnerability · Source |
| CVE-2022-48715 | suse_vex | SUSE CVE CVE-2022-48715 | known affected: 410 known not affected: 77 recommended: 566 | 2026-08-13T02:29:08+00:00 | Vulnerability · Source |
| CVE-2022-48717 | suse_vex | SUSE CVE CVE-2022-48717 | known affected: 347 known not affected: 146 recommended: 482 | 2026-08-13T02:29:07+00:00 | Vulnerability · Source |
| CVE-2022-48721 | suse_vex | SUSE CVE CVE-2022-48721 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-13T02:29:06+00:00 | Vulnerability · Source |
| CVE-2022-48723 | suse_vex | SUSE CVE CVE-2022-48723 | known affected: 330 known not affected: 205 recommended: 391 | 2026-08-13T02:29:05+00:00 | Vulnerability · Source |
| CVE-2022-48724 | suse_vex | SUSE CVE CVE-2022-48724 | known affected: 347 known not affected: 146 recommended: 482 | 2026-08-13T02:29:03+00:00 | Vulnerability · Source |
| CVE-2022-48728 | suse_vex | SUSE CVE CVE-2022-48728 | known affected: 324 known not affected: 169 recommended: 482 | 2026-08-13T02:29:02+00:00 | Vulnerability · Source |
| CVE-2022-48735 | suse_vex | SUSE CVE CVE-2022-48735 | known affected: 346 known not affected: 113 recommended: 433 | 2026-08-13T02:29:00+00:00 | Vulnerability · Source |
| CVE-2022-48736 | suse_vex | SUSE CVE CVE-2022-48736 | known affected: 324 known not affected: 66 recommended: 482 | 2026-08-13T02:28:58+00:00 | Vulnerability · Source |
| CVE-2022-48746 | suse_vex | SUSE CVE CVE-2022-48746 | known affected: 324 known not affected: 169 recommended: 482 | 2026-08-13T02:28:55+00:00 | Vulnerability · Source |
| CVE-2022-48748 | suse_vex | SUSE CVE CVE-2022-48748 | known affected: 324 known not affected: 169 recommended: 389 | 2026-08-13T02:28:54+00:00 | Vulnerability · Source |
| CVE-2022-48768 | suse_vex | SUSE CVE CVE-2022-48768 | known affected: 347 known not affected: 146 recommended: 482 | 2026-08-13T02:28:52+00:00 | Vulnerability · Source |
| CVE-2022-48769 | suse_vex | SUSE CVE CVE-2022-48769 | known affected: 463 known not affected: 71 recommended: 475 | 2026-08-13T02:28:51+00:00 | Vulnerability · Source |
| CVE-2022-48774 | suse_vex | SUSE CVE CVE-2022-48774 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-13T02:28:49+00:00 | Vulnerability · Source |
| CVE-2022-48778 | suse_vex | SUSE CVE CVE-2022-48778 | known affected: 295 known not affected: 201 recommended: 511 | 2026-08-13T02:28:48+00:00 | Vulnerability · Source |
| CVE-2022-48794 | suse_vex | SUSE CVE CVE-2022-48794 | known affected: 295 known not affected: 183 recommended: 496 | 2026-08-13T02:28:46+00:00 | Vulnerability · Source |
| CVE-2022-48818 | suse_vex | SUSE CVE CVE-2022-48818 | known affected: 295 known not affected: 205 recommended: 426 | 2026-08-13T02:28:43+00:00 | Vulnerability · Source |
| CVE-2022-48826 | suse_vex | SUSE CVE CVE-2022-48826 | known affected: 405 known not affected: 71 recommended: 496 | 2026-08-13T02:28:40+00:00 | Vulnerability · Source |
| CVE-2022-48828 | suse_vex | SUSE CVE CVE-2022-48828 | known affected: 422 known not affected: 76 recommended: 510 | 2026-08-13T02:28:39+00:00 | Vulnerability · Source |
| CVE-2022-48829 | suse_vex | SUSE CVE CVE-2022-48829 | known affected: 295 known not affected: 183 recommended: 510 | 2026-08-13T02:28:38+00:00 | Vulnerability · Source |
| CVE-2022-48834 | suse_vex | SUSE CVE CVE-2022-48834 | known affected: 318 known not affected: 178 recommended: 511 | 2026-08-13T02:28:36+00:00 | Vulnerability · Source |
| CVE-2022-48835 | suse_vex | SUSE CVE CVE-2022-48835 | known affected: 318 known not affected: 178 recommended: 511 | 2026-08-13T02:28:34+00:00 | Vulnerability · Source |
| CVE-2022-48837 | suse_vex | SUSE CVE CVE-2022-48837 | known affected: 318 known not affected: 178 recommended: 511 | 2026-08-13T02:28:33+00:00 | Vulnerability · Source |
| CVE-2022-48839 | suse_vex | SUSE CVE CVE-2022-48839 | known not affected: 148 recommended: 568 | 2026-08-13T02:28:32+00:00 | Vulnerability · Source |
| CVE-2022-48852 | suse_vex | SUSE CVE CVE-2022-48852 | known affected: 500 known not affected: 142 recommended: 298 | 2026-08-13T02:28:30+00:00 | Vulnerability · Source |
| CVE-2022-48855 | suse_vex | SUSE CVE CVE-2022-48855 | known affected: 514 known not affected: 86 recommended: 368 | 2026-08-13T02:28:27+00:00 | Vulnerability · Source |
| CVE-2022-48875 | suse_vex | SUSE CVE CVE-2022-48875 | known affected: 431 known not affected: 70 recommended: 518 | 2026-08-13T02:28:25+00:00 | Vulnerability · Source |
| CVE-2022-48905 | suse_vex | SUSE CVE CVE-2022-48905 | known affected: 384 known not affected: 97 recommended: 588 | 2026-08-13T02:28:22+00:00 | Vulnerability · Source |
| CVE-2022-48906 | suse_vex | SUSE CVE CVE-2022-48906 | known affected: 401 known not affected: 233 recommended: 288 | 2026-08-13T02:28:21+00:00 | Vulnerability · Source |