VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-42323 | suse_vex | SUSE CVE CVE-2022-42323 | recommended: 377 | 2026-07-25T17:22:34+00:00 | Vulnerability · Source |
| CVE-2022-42332 | suse_vex | SUSE CVE CVE-2022-42332 | known affected: 287 known not affected: 28 recommended: 413 | 2026-07-25T17:22:33+00:00 | Vulnerability · Source |
| CVE-2022-42336 | suse_vex | SUSE CVE CVE-2022-42336 | known not affected: 312 recommended: 78 | 2026-07-25T17:22:31+00:00 | Vulnerability · Source |
| CVE-2022-42432 | suse_vex | SUSE CVE CVE-2022-42432 | known not affected: 175 recommended: 22 | 2026-07-25T17:22:29+00:00 | Vulnerability · Source |
| CVE-2022-42916 | suse_vex | SUSE CVE CVE-2022-42916 | known affected: 271 known not affected: 151 recommended: 253 | 2026-07-25T17:22:12+00:00 | Vulnerability · Source |
| CVE-2022-42920 | suse_vex | SUSE CVE CVE-2022-42920 | known affected: 403 recommended: 53 | 2026-07-25T17:22:11+00:00 | Vulnerability · Source |
| CVE-2022-42928 | suse_vex | SUSE CVE CVE-2022-42928 | known affected: 1 recommended: 390 | 2026-07-25T17:22:09+00:00 | Vulnerability · Source |
| CVE-2022-43995 | suse_vex | SUSE CVE CVE-2022-43995 | known affected: 254 known not affected: 1 recommended: 360 | 2026-07-25T17:22:06+00:00 | Vulnerability · Source |
| CVE-2022-44032 | suse_vex | SUSE CVE CVE-2022-44032 | known not affected: 352 recommended: 34 | 2026-07-25T17:22:05+00:00 | Vulnerability · Source |
| CVE-2022-44034 | suse_vex | SUSE CVE CVE-2022-44034 | known not affected: 333 recommended: 6 | 2026-07-25T17:22:03+00:00 | Vulnerability · Source |
| CVE-2022-45142 | suse_vex | SUSE CVE CVE-2022-45142 | known not affected: 1583 recommended: 18 | 2026-07-25T17:21:59+00:00 | Vulnerability · Source |
| CVE-2022-45411 | suse_vex | SUSE CVE CVE-2022-45411 | known affected: 1 recommended: 405 | 2026-07-25T17:21:51+00:00 | Vulnerability · Source |
| CVE-2022-45412 | suse_vex | SUSE CVE CVE-2022-45412 | known affected: 1 recommended: 405 | 2026-07-25T17:21:50+00:00 | Vulnerability · Source |
| CVE-2022-45415 | suse_vex | SUSE CVE CVE-2022-45415 | known affected: 1 recommended: 9 | 2026-07-25T17:21:48+00:00 | Vulnerability · Source |
| CVE-2022-45418 | suse_vex | SUSE CVE CVE-2022-45418 | known affected: 1 recommended: 405 | 2026-07-25T17:21:47+00:00 | Vulnerability · Source |
| CVE-2022-45873 | suse_vex | SUSE CVE CVE-2022-45873 | known not affected: 605 recommended: 10 | 2026-07-25T17:21:42+00:00 | Vulnerability · Source |
| CVE-2022-46875 | suse_vex | SUSE CVE CVE-2022-46875 | known affected: 21 recommended: 372 | 2026-07-25T17:21:31+00:00 | Vulnerability · Source |
| CVE-2022-46908 | suse_vex | SUSE CVE CVE-2022-46908 | known affected: 165 known not affected: 13 recommended: 563 | 2026-07-25T17:21:27+00:00 | Vulnerability · Source |
| CVE-2022-47008 | suse_vex | SUSE CVE CVE-2022-47008 | known affected: 10 known not affected: 224 | 2026-07-25T17:21:26+00:00 | Vulnerability · Source |
| CVE-2022-47011 | suse_vex | SUSE CVE CVE-2022-47011 | known affected: 10 known not affected: 224 | 2026-07-25T17:21:24+00:00 | Vulnerability · Source |
| CVE-2022-47111 | suse_vex | SUSE CVE CVE-2022-47111 | known affected: 93 | 2026-07-25T17:21:23+00:00 | Vulnerability · Source |
| CVE-2022-47942 | suse_vex | SUSE CVE CVE-2022-47942 | known not affected: 362 | 2026-07-25T17:21:18+00:00 | Vulnerability · Source |
| CVE-2022-47943 | suse_vex | SUSE CVE CVE-2022-47943 | known not affected: 362 | 2026-07-25T17:21:17+00:00 | Vulnerability · Source |
| CVE-2022-48423 | suse_vex | SUSE CVE CVE-2022-48423 | known not affected: 519 | 2026-07-25T17:21:07+00:00 | Vulnerability · Source |
| CVE-2022-48545 | suse_vex | SUSE CVE CVE-2022-48545 | recommended: 38 | 2026-07-25T17:21:05+00:00 | Vulnerability · Source |
| CVE-2022-48565 | suse_vex | SUSE CVE CVE-2022-48565 | known affected: 566 known not affected: 384 recommended: 238 | 2026-07-25T17:21:04+00:00 | Vulnerability · Source |
| CVE-2022-48619 | suse_vex | SUSE CVE CVE-2022-48619 | known affected: 509 known not affected: 280 recommended: 132 | 2026-07-25T17:21:02+00:00 | Vulnerability · Source |
| CVE-2022-48626 | suse_vex | SUSE CVE CVE-2022-48626 | known not affected: 136 recommended: 566 | 2026-07-25T17:20:59+00:00 | Vulnerability · Source |
| CVE-2022-48644 | suse_vex | SUSE CVE CVE-2022-48644 | known affected: 441 known not affected: 195 recommended: 318 | 2026-07-25T17:20:50+00:00 | Vulnerability · Source |
| CVE-2022-48650 | suse_vex | SUSE CVE CVE-2022-48650 | known affected: 259 known not affected: 145 recommended: 648 | 2026-07-25T17:20:47+00:00 | Vulnerability · Source |
| CVE-2022-48665 | suse_vex | SUSE CVE CVE-2022-48665 | known not affected: 288 | 2026-07-25T17:20:37+00:00 | Vulnerability · Source |
| CVE-2022-48687 | suse_vex | SUSE CVE CVE-2022-48687 | known affected: 16 known not affected: 140 recommended: 536 | 2026-07-25T17:20:30+00:00 | Vulnerability · Source |
| 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-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 |