VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284477 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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 |
| CVE-2022-48840 | suse_vex | SUSE CVE CVE-2022-48840 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:08+00:00 | Vulnerability · Source |
| CVE-2022-48847 | suse_vex | SUSE CVE CVE-2022-48847 | known not affected: 205 recommended: 327 | 2026-07-25T17:19:07+00:00 | Vulnerability · Source |
| CVE-2022-48848 | suse_vex | SUSE CVE CVE-2022-48848 | known not affected: 318 | 2026-07-25T17:19:05+00:00 | Vulnerability · Source |
| CVE-2022-48849 | suse_vex | SUSE CVE CVE-2022-48849 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:19:04+00:00 | Vulnerability · Source |
| CVE-2022-48852 | suse_vex | SUSE CVE CVE-2022-48852 | known affected: 500 known not affected: 142 recommended: 298 | 2026-07-25T17:19: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-07-25T17:19:01+00:00 | Vulnerability · Source |
| CVE-2022-48858 | suse_vex | SUSE CVE CVE-2022-48858 | known affected: 295 known not affected: 201 recommended: 511 | 2026-07-25T17:18:59+00:00 | Vulnerability · Source |
| CVE-2022-48861 | suse_vex | SUSE CVE CVE-2022-48861 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:18:58+00:00 | Vulnerability · Source |
| CVE-2022-48862 | suse_vex | SUSE CVE CVE-2022-48862 | known affected: 295 known not affected: 205 recommended: 426 | 2026-07-25T17:18:56+00:00 | Vulnerability · Source |
| CVE-2022-48863 | suse_vex | SUSE CVE CVE-2022-48863 | known affected: 428 known not affected: 71 recommended: 510 | 2026-07-25T17:18:54+00:00 | Vulnerability · Source |
| CVE-2022-48865 | suse_vex | SUSE CVE CVE-2022-48865 | known affected: 524 known not affected: 86 recommended: 358 | 2026-07-25T17:18:52+00:00 | Vulnerability · Source |
| CVE-2022-48875 | suse_vex | SUSE CVE CVE-2022-48875 | known affected: 431 known not affected: 70 recommended: 518 | 2026-07-25T17:18:50+00:00 | Vulnerability · Source |
| CVE-2022-48879 | suse_vex | SUSE CVE CVE-2022-48879 | known affected: 411 known not affected: 205 recommended: 394 | 2026-07-25T17:18:48+00:00 | Vulnerability · Source |
| CVE-2022-48881 | suse_vex | SUSE CVE CVE-2022-48881 | known affected: 340 known not affected: 249 recommended: 288 | 2026-07-25T17:18:47+00:00 | Vulnerability · Source |
| CVE-2022-48888 | suse_vex | SUSE CVE CVE-2022-48888 | known affected: 340 known not affected: 248 recommended: 288 | 2026-07-25T17:18:45+00:00 | Vulnerability · Source |
| CVE-2022-48889 | suse_vex | SUSE CVE CVE-2022-48889 | known affected: 340 known not affected: 248 recommended: 288 | 2026-07-25T17:18:44+00:00 | Vulnerability · Source |
| CVE-2022-48890 | suse_vex | SUSE CVE CVE-2022-48890 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:43+00:00 | Vulnerability · Source |
| CVE-2022-48893 | suse_vex | SUSE CVE CVE-2022-48893 | known affected: 340 known not affected: 169 recommended: 288 | 2026-07-25T17:18:41+00:00 | Vulnerability · Source |
| CVE-2022-48895 | suse_vex | SUSE CVE CVE-2022-48895 | known not affected: 310 | 2026-07-25T17:18:40+00:00 | Vulnerability · Source |
| CVE-2022-48898 | suse_vex | SUSE CVE CVE-2022-48898 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:38+00:00 | Vulnerability · Source |
| CVE-2022-48900 | suse_vex | SUSE CVE CVE-2022-48900 | known not affected: 301 | 2026-07-25T17:18:37+00:00 | Vulnerability · Source |
| CVE-2022-48902 | suse_vex | SUSE CVE CVE-2022-48902 | known affected: 138 known not affected: 239 | 2026-07-25T17:18:36+00:00 | Vulnerability · Source |
| CVE-2022-48905 | suse_vex | SUSE CVE CVE-2022-48905 | known affected: 384 known not affected: 98 recommended: 588 | 2026-07-25T17:18:34+00:00 | Vulnerability · Source |
| CVE-2022-48907 | suse_vex | SUSE CVE CVE-2022-48907 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:33+00:00 | Vulnerability · Source |
| CVE-2022-48908 | suse_vex | SUSE CVE CVE-2022-48908 | known not affected: 514 | 2026-07-25T17:18:31+00:00 | Vulnerability · Source |
| CVE-2022-48909 | suse_vex | SUSE CVE CVE-2022-48909 | known affected: 359 known not affected: 142 recommended: 411 | 2026-07-25T17:18:30+00:00 | Vulnerability · Source |
| CVE-2022-48911 | suse_vex | SUSE CVE CVE-2022-48911 | known affected: 357 known not affected: 124 recommended: 701 | 2026-07-25T17:18:28+00:00 | Vulnerability · Source |
| CVE-2022-48914 | suse_vex | SUSE CVE CVE-2022-48914 | known affected: 310 known not affected: 195 recommended: 411 | 2026-07-25T17:18:27+00:00 | Vulnerability · Source |
| CVE-2022-48917 | suse_vex | SUSE CVE CVE-2022-48917 | known affected: 310 known not affected: 191 recommended: 496 | 2026-07-25T17:18:25+00:00 | Vulnerability · Source |