VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291949 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-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-48779 | suse_vex | SUSE CVE CVE-2022-48779 | known not affected: 318 | 2026-07-25T17:19:44+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-48795 | suse_vex | SUSE CVE CVE-2022-48795 | known not affected: 318 | 2026-07-25T17:19:35+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-48848 | suse_vex | SUSE CVE CVE-2022-48848 | known not affected: 318 | 2026-07-25T17:19:05+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-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-48895 | suse_vex | SUSE CVE CVE-2022-48895 | known not affected: 310 | 2026-07-25T17:18:40+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-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-48926 | suse_vex | SUSE CVE CVE-2022-48926 | known affected: 310 known not affected: 376 recommended: 496 | 2026-07-25T17:18:22+00:00 | Vulnerability · Source |
| CVE-2022-48929 | suse_vex | SUSE CVE CVE-2022-48929 | known not affected: 195 recommended: 327 | 2026-07-25T17:18:21+00:00 | Vulnerability · Source |
| CVE-2022-48942 | suse_vex | SUSE CVE CVE-2022-48942 | known affected: 310 known not affected: 195 recommended: 438 | 2026-07-25T17:18:13+00:00 | Vulnerability · Source |
| CVE-2022-48963 | suse_vex | SUSE CVE CVE-2022-48963 | known not affected: 402 | 2026-07-25T17:18:03+00:00 | Vulnerability · Source |
| CVE-2022-48964 | suse_vex | SUSE CVE CVE-2022-48964 | known not affected: 402 | 2026-07-25T17:18:02+00:00 | Vulnerability · Source |
| CVE-2022-48976 | suse_vex | SUSE CVE CVE-2022-48976 | known not affected: 402 recommended: 27 | 2026-07-25T17:17:59+00:00 | Vulnerability · Source |
| CVE-2022-48984 | suse_vex | SUSE CVE CVE-2022-48984 | known not affected: 402 | 2026-07-25T17:17:54+00:00 | Vulnerability · Source |
| CVE-2022-49002 | suse_vex | SUSE CVE CVE-2022-49002 | known affected: 481 known not affected: 72 recommended: 434 | 2026-07-25T17:17:44+00:00 | Vulnerability · Source |
| CVE-2022-49009 | suse_vex | SUSE CVE CVE-2022-49009 | known not affected: 379 | 2026-07-25T17:17:35+00:00 | Vulnerability · Source |
| CVE-2022-49010 | suse_vex | SUSE CVE CVE-2022-49010 | known affected: 449 known not affected: 123 recommended: 565 | 2026-07-25T17:17:33+00:00 | Vulnerability · Source |
| CVE-2022-49034 | suse_vex | SUSE CVE CVE-2022-49034 | known not affected: 425 | 2026-07-25T17:17:19+00:00 | Vulnerability · Source |
| CVE-2022-49047 | suse_vex | SUSE CVE CVE-2022-49047 | known not affected: 352 | 2026-07-25T17:17:16+00:00 | Vulnerability · Source |
| CVE-2022-49072 | suse_vex | SUSE CVE CVE-2022-49072 | known affected: 163 known not affected: 189 recommended: 27 | 2026-07-25T17:16:59+00:00 | Vulnerability · Source |
| CVE-2022-49081 | suse_vex | SUSE CVE CVE-2022-49081 | known affected: 112 known not affected: 240 recommended: 47 | 2026-07-25T17:16:52+00:00 | Vulnerability · Source |
| CVE-2022-49101 | suse_vex | SUSE CVE CVE-2022-49101 | known not affected: 352 | 2026-07-25T17:16:35+00:00 | Vulnerability · Source |
| CVE-2022-49103 | suse_vex | SUSE CVE CVE-2022-49103 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:16:33+00:00 | Vulnerability · Source |
| CVE-2022-49108 | suse_vex | SUSE CVE CVE-2022-49108 | known not affected: 352 | 2026-07-25T17:16:29+00:00 | Vulnerability · Source |
| CVE-2022-49150 | suse_vex | SUSE CVE CVE-2022-49150 | known not affected: 352 | 2026-07-25T17:16:13+00:00 | Vulnerability · Source |
| CVE-2022-49152 | suse_vex | SUSE CVE CVE-2022-49152 | known not affected: 352 recommended: 22 | 2026-07-25T17:16:11+00:00 | Vulnerability · Source |
| CVE-2022-49156 | suse_vex | SUSE CVE CVE-2022-49156 | known affected: 415 known not affected: 163 recommended: 375 | 2026-07-25T17:16:08+00:00 | Vulnerability · Source |
| CVE-2022-49166 | suse_vex | SUSE CVE CVE-2022-49166 | known not affected: 348 | 2026-07-25T17:16:01+00:00 | Vulnerability · Source |
| CVE-2022-49170 | suse_vex | SUSE CVE CVE-2022-49170 | known not affected: 352 | 2026-07-25T17:16:00+00:00 | Vulnerability · Source |
| CVE-2022-49171 | suse_vex | SUSE CVE CVE-2022-49171 | known affected: 475 known not affected: 241 recommended: 40 | 2026-07-25T17:15:58+00:00 | Vulnerability · Source |
| CVE-2022-49173 | suse_vex | SUSE CVE CVE-2022-49173 | known not affected: 348 | 2026-07-25T17:15:57+00:00 | Vulnerability · Source |
| CVE-2022-49181 | suse_vex | SUSE CVE CVE-2022-49181 | known not affected: 352 | 2026-07-25T17:15:52+00:00 | Vulnerability · Source |
| CVE-2022-49184 | suse_vex | SUSE CVE CVE-2022-49184 | known not affected: 352 | 2026-07-25T17:15:48+00:00 | Vulnerability · Source |
| CVE-2022-49186 | suse_vex | SUSE CVE CVE-2022-49186 | known not affected: 352 | 2026-07-25T17:15:47+00:00 | Vulnerability · Source |
| CVE-2022-49190 | suse_vex | SUSE CVE CVE-2022-49190 | known affected: 573 known not affected: 183 recommended: 37 | 2026-07-25T17:15:44+00:00 | Vulnerability · Source |
| CVE-2022-49191 | suse_vex | SUSE CVE CVE-2022-49191 | known affected: 567 known not affected: 153 recommended: 40 | 2026-07-25T17:15:43+00:00 | Vulnerability · Source |
| CVE-2022-49195 | suse_vex | SUSE CVE CVE-2022-49195 | known not affected: 403 | 2026-07-25T17:15:39+00:00 | Vulnerability · Source |
| CVE-2022-49206 | suse_vex | SUSE CVE CVE-2022-49206 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-25T17:15:34+00:00 | Vulnerability · Source |
| CVE-2022-49221 | suse_vex | SUSE CVE CVE-2022-49221 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:28+00:00 | Vulnerability · Source |
| CVE-2022-49229 | suse_vex | SUSE CVE CVE-2022-49229 | known affected: 112 known not affected: 240 recommended: 22 | 2026-07-25T17:15:24+00:00 | Vulnerability · Source |
| CVE-2022-49249 | suse_vex | SUSE CVE CVE-2022-49249 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:13+00:00 | Vulnerability · Source |
| CVE-2022-49252 | suse_vex | SUSE CVE CVE-2022-49252 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:15:12+00:00 | Vulnerability · Source |