VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48892 | suse_vex | SUSE CVE CVE-2022-48892 | known not affected: 371 | 2026-10-16T14:34:20+00:00 | Vulnerability · Source |
| CVE-2022-48897 | suse_vex | SUSE CVE CVE-2022-48897 | known not affected: 371 | 2026-10-16T14:34:17+00:00 | Vulnerability · Source |
| CVE-2022-48899 | suse_vex | SUSE CVE CVE-2022-48899 | known affected: 487 known not affected: 71 recommended: 495 | 2026-10-16T14:34:15+00:00 | Vulnerability · Source |
| CVE-2022-48900 | suse_vex | SUSE CVE CVE-2022-48900 | known not affected: 364 | 2026-10-16T14:34:13+00:00 | Vulnerability · Source |
| CVE-2022-48902 | suse_vex | SUSE CVE CVE-2022-48902 | known affected: 144 known not affected: 294 | 2026-10-16T14:34:08+00:00 | Vulnerability · Source |
| CVE-2022-48903 | suse_vex | SUSE CVE CVE-2022-48903 | known affected: 310 known not affected: 245 recommended: 411 | 2026-10-16T14:34:05+00:00 | Vulnerability · Source |
| CVE-2022-48904 | suse_vex | SUSE CVE CVE-2022-48904 | known affected: 310 known not affected: 250 recommended: 431 | 2026-10-16T14:34:02+00:00 | Vulnerability · Source |
| CVE-2022-48907 | suse_vex | SUSE CVE CVE-2022-48907 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:33:59+00:00 | Vulnerability · Source |
| CVE-2022-48909 | suse_vex | SUSE CVE CVE-2022-48909 | known affected: 371 known not affected: 185 recommended: 411 | 2026-10-16T14:33:56+00:00 | Vulnerability · Source |
| CVE-2022-48913 | suse_vex | SUSE CVE CVE-2022-48913 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:33:50+00:00 | Vulnerability · Source |
| CVE-2022-48916 | suse_vex | SUSE CVE CVE-2022-48916 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:33:48+00:00 | Vulnerability · Source |
| CVE-2022-48918 | suse_vex | SUSE CVE CVE-2022-48918 | known affected: 310 known not affected: 250 recommended: 453 | 2026-10-16T14:33:42+00:00 | Vulnerability · Source |
| CVE-2022-48920 | suse_vex | SUSE CVE CVE-2022-48920 | known affected: 576 known not affected: 83 recommended: 358 | 2026-10-16T14:33:40+00:00 | Vulnerability · Source |
| CVE-2022-48922 | suse_vex | SUSE CVE CVE-2022-48922 | known affected: 144 known not affected: 294 | 2026-10-16T14:33:35+00:00 | Vulnerability · Source |
| CVE-2022-48925 | suse_vex | SUSE CVE CVE-2022-48925 | known affected: 312 known not affected: 162 recommended: 610 | 2026-10-16T14:33:33+00:00 | Vulnerability · Source |
| CVE-2022-48926 | suse_vex | SUSE CVE CVE-2022-48926 | known affected: 310 known not affected: 478 recommended: 496 | 2026-10-16T14:33:30+00:00 | Vulnerability · Source |
| CVE-2022-48929 | suse_vex | SUSE CVE CVE-2022-48929 | known not affected: 250 recommended: 327 | 2026-10-16T14:33:27+00:00 | Vulnerability · Source |
| CVE-2022-48930 | suse_vex | SUSE CVE CVE-2022-48930 | known affected: 440 known not affected: 95 recommended: 580 | 2026-10-16T14:33:24+00:00 | Vulnerability · Source |
| CVE-2022-48932 | suse_vex | SUSE CVE CVE-2022-48932 | known affected: 310 known not affected: 250 recommended: 411 | 2026-10-16T14:33:21+00:00 | Vulnerability · Source |
| CVE-2022-48933 | suse_vex | SUSE CVE CVE-2022-48933 | known affected: 493 known not affected: 290 recommended: 180 | 2026-10-16T14:33:18+00:00 | Vulnerability · Source |
| CVE-2022-48934 | suse_vex | SUSE CVE CVE-2022-48934 | known affected: 339 known not affected: 217 recommended: 523 | 2026-10-16T14:33:15+00:00 | Vulnerability · Source |
| CVE-2022-48936 | suse_vex | SUSE CVE CVE-2022-48936 | known not affected: 69 recommended: 42 | 2026-10-16T14:33:12+00:00 | Vulnerability · Source |
| CVE-2022-48938 | suse_vex | SUSE CVE CVE-2022-48938 | known affected: 483 known not affected: 72 recommended: 495 | 2026-10-16T14:33:09+00:00 | Vulnerability · Source |
| CVE-2022-48939 | suse_vex | SUSE CVE CVE-2022-48939 | known affected: 372 known not affected: 214 recommended: 315 | 2026-10-16T14:33:07+00:00 | Vulnerability · Source |
| CVE-2022-48944 | suse_vex | SUSE CVE CVE-2022-48944 | known affected: 310 known not affected: 279 recommended: 411 | 2026-10-16T14:33:01+00:00 | Vulnerability · Source |
| CVE-2022-48945 | suse_vex | SUSE CVE CVE-2022-48945 | known affected: 444 known not affected: 135 recommended: 638 | 2026-10-16T14:32:59+00:00 | Vulnerability · Source |
| CVE-2022-48946 | suse_vex | SUSE CVE CVE-2022-48946 | known affected: 528 known not affected: 107 recommended: 434 | 2026-10-16T14:32:57+00:00 | Vulnerability · Source |
| CVE-2022-48952 | suse_vex | SUSE CVE CVE-2022-48952 | known affected: 226 known not affected: 299 | 2026-10-16T14:32:55+00:00 | Vulnerability · Source |
| CVE-2022-48961 | suse_vex | SUSE CVE CVE-2022-48961 | known affected: 324 known not affected: 476 recommended: 394 | 2026-10-16T14:32:50+00:00 | Vulnerability · Source |
| CVE-2022-48962 | suse_vex | SUSE CVE CVE-2022-48962 | known affected: 382 known not affected: 188 recommended: 549 | 2026-10-16T14:32:48+00:00 | Vulnerability · Source |
| CVE-2022-48970 | suse_vex | SUSE CVE CVE-2022-48970 | known not affected: 314 recommended: 453 | 2026-10-16T14:32:45+00:00 | Vulnerability · Source |
| CVE-2022-48971 | suse_vex | SUSE CVE CVE-2022-48971 | known affected: 505 known not affected: 168 recommended: 420 | 2026-10-16T14:32:43+00:00 | Vulnerability · Source |
| CVE-2022-48973 | suse_vex | SUSE CVE CVE-2022-48973 | known affected: 553 known not affected: 109 recommended: 434 | 2026-10-16T14:32:40+00:00 | Vulnerability · Source |
| CVE-2022-48974 | suse_vex | SUSE CVE CVE-2022-48974 | known not affected: 498 recommended: 27 | 2026-10-16T14:32:38+00:00 | Vulnerability · Source |
| CVE-2022-48976 | suse_vex | SUSE CVE CVE-2022-48976 | known not affected: 498 recommended: 27 | 2026-10-16T14:32:35+00:00 | Vulnerability · Source |
| CVE-2022-48978 | suse_vex | SUSE CVE CVE-2022-48978 | known affected: 563 known not affected: 102 recommended: 474 | 2026-10-16T14:32:32+00:00 | Vulnerability · Source |
| CVE-2022-48980 | suse_vex | SUSE CVE CVE-2022-48980 | known affected: 428 known not affected: 355 recommended: 271 | 2026-10-16T14:32:29+00:00 | Vulnerability · Source |
| CVE-2022-48983 | suse_vex | SUSE CVE CVE-2022-48983 | known affected: 354 known not affected: 436 recommended: 269 | 2026-10-16T14:32:23+00:00 | Vulnerability · Source |
| CVE-2022-48984 | suse_vex | SUSE CVE CVE-2022-48984 | known not affected: 498 | 2026-10-16T14:32:21+00:00 | Vulnerability · Source |
| CVE-2022-48986 | suse_vex | SUSE CVE CVE-2022-48986 | known not affected: 561 | 2026-10-16T14:32:19+00:00 | Vulnerability · Source |
| CVE-2022-48988 | suse_vex | SUSE CVE CVE-2022-48988 | known affected: 416 known not affected: 109 recommended: 655 | 2026-10-16T14:32:16+00:00 | Vulnerability · Source |
| CVE-2022-48989 | suse_vex | SUSE CVE CVE-2022-48989 | known affected: 354 known not affected: 436 recommended: 312 | 2026-10-16T14:32:14+00:00 | Vulnerability · Source |
| CVE-2022-48991 | suse_vex | SUSE CVE CVE-2022-48991 | known affected: 436 known not affected: 177 recommended: 607 | 2026-10-16T14:32:11+00:00 | Vulnerability · Source |
| CVE-2022-48993 | suse_vex | SUSE CVE CVE-2022-48993 | No product status | 2026-10-16T14:32:09+00:00 | Vulnerability · Source |
| CVE-2022-48998 | suse_vex | SUSE CVE CVE-2022-48998 | known not affected: 477 | 2026-10-16T14:32:06+00:00 | Vulnerability · Source |
| CVE-2022-49001 | suse_vex | SUSE CVE CVE-2022-49001 | known not affected: 477 | 2026-10-16T14:32:03+00:00 | Vulnerability · Source |
| CVE-2022-49005 | suse_vex | SUSE CVE CVE-2022-49005 | known affected: 324 known not affected: 319 recommended: 394 | 2026-10-16T14:31:57+00:00 | Vulnerability · Source |
| CVE-2022-49011 | suse_vex | SUSE CVE CVE-2022-49011 | known affected: 498 known not affected: 116 recommended: 596 | 2026-10-16T14:31:54+00:00 | Vulnerability · Source |
| CVE-2022-49014 | suse_vex | SUSE CVE CVE-2022-49014 | known affected: 324 known not affected: 269 recommended: 607 | 2026-10-16T14:31:51+00:00 | Vulnerability · Source |
| CVE-2022-49017 | suse_vex | SUSE CVE CVE-2022-49017 | known affected: 428 known not affected: 355 recommended: 271 | 2026-10-16T14:31:48+00:00 | Vulnerability · Source |