VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294017 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-35230 | suse_vex | SUSE CVE CVE-2022-35230 | known affected: 23 recommended: 15 | 2026-07-25T17:23:56+00:00 | Vulnerability · Source |
| CVE-2022-36123 | suse_vex | SUSE CVE CVE-2022-36123 | known not affected: 327 | 2026-07-25T17:23:54+00:00 | Vulnerability · Source |
| CVE-2022-37052 | suse_vex | SUSE CVE CVE-2022-37052 | known affected: 202 known not affected: 5 recommended: 185 | 2026-07-25T17:23:39+00:00 | Vulnerability · Source |
| CVE-2022-38228 | suse_vex | SUSE CVE CVE-2022-38228 | known not affected: 330 | 2026-07-25T17:23:23+00:00 | Vulnerability · Source |
| CVE-2022-38234 | suse_vex | SUSE CVE CVE-2022-38234 | known not affected: 330 | 2026-07-25T17:23:22+00:00 | Vulnerability · Source |
| CVE-2022-39177 | suse_vex | SUSE CVE CVE-2022-39177 | known affected: 1 known not affected: 38 recommended: 96 | 2026-07-25T17:23:15+00:00 | Vulnerability · Source |
| CVE-2022-40433 | suse_vex | SUSE CVE CVE-2022-40433 | known affected: 4 known not affected: 477 recommended: 37 | 2026-07-25T17:23:06+00:00 | Vulnerability · Source |
| CVE-2022-40626 | suse_vex | SUSE CVE CVE-2022-40626 | known not affected: 25 | 2026-07-25T17:23:01+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-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-47111 | suse_vex | SUSE CVE CVE-2022-47111 | known affected: 93 | 2026-07-25T17:21:23+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-48545 | suse_vex | SUSE CVE CVE-2022-48545 | recommended: 38 | 2026-07-25T17:21:05+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-48833 | suse_vex | SUSE CVE CVE-2022-48833 | known not affected: 318 | 2026-07-25T17:19:15+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-48908 | suse_vex | SUSE CVE CVE-2022-48908 | known not affected: 514 | 2026-07-25T17:18:31+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-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-49186 | suse_vex | SUSE CVE CVE-2022-49186 | known not affected: 352 | 2026-07-25T17:15:47+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-49457 | suse_vex | SUSE CVE CVE-2022-49457 | known not affected: 348 | 2026-07-25T17:13:37+00:00 | Vulnerability · Source |
| CVE-2022-49578 | suse_vex | SUSE CVE CVE-2022-49578 | known affected: 618 known not affected: 104 recommended: 53 | 2026-07-25T17:12:48+00:00 | Vulnerability · Source |
| CVE-2022-49590 | suse_vex | SUSE CVE CVE-2022-49590 | known affected: 632 known not affected: 124 recommended: 67 | 2026-07-25T17:12:39+00:00 | Vulnerability · Source |
| CVE-2022-49602 | suse_vex | SUSE CVE CVE-2022-49602 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:32+00:00 | Vulnerability · Source |
| CVE-2022-49817 | suse_vex | SUSE CVE CVE-2022-49817 | known affected: 112 known not affected: 285 | 2026-07-25T17:11:04+00:00 | Vulnerability · Source |
| CVE-2022-49947 | suse_vex | SUSE CVE CVE-2022-49947 | known not affected: 401 | 2026-07-25T17:10:21+00:00 | Vulnerability · Source |
| CVE-2022-50114 | suse_vex | SUSE CVE CVE-2022-50114 | known affected: 106 known not affected: 295 | 2026-07-25T17:09:20+00:00 | Vulnerability · Source |
| CVE-2022-50163 | suse_vex | SUSE CVE CVE-2022-50163 | known affected: 92 known not affected: 309 | 2026-07-25T17:08:51+00:00 | Vulnerability · Source |
| CVE-2022-50205 | suse_vex | SUSE CVE CVE-2022-50205 | known affected: 245 known not affected: 171 | 2026-07-25T17:08:30+00:00 | Vulnerability · Source |
| CVE-2022-50384 | suse_vex | SUSE CVE CVE-2022-50384 | known affected: 224 known not affected: 192 | 2026-07-25T17:07:08+00:00 | Vulnerability · Source |
| CVE-2022-50415 | suse_vex | SUSE CVE CVE-2022-50415 | known not affected: 416 | 2026-07-25T17:06:52+00:00 | Vulnerability · Source |
| CVE-2022-50550 | suse_vex | SUSE CVE CVE-2022-50550 | known affected: 106 known not affected: 310 recommended: 29 | 2026-07-25T17:06:10+00:00 | Vulnerability · Source |
| CVE-2022-50659 | suse_vex | SUSE CVE CVE-2022-50659 | known affected: 6 known not affected: 402 | 2026-07-25T17:05:36+00:00 | Vulnerability · Source |
| CVE-2022-50725 | suse_vex | SUSE CVE CVE-2022-50725 | known not affected: 453 | 2026-07-25T17:05:17+00:00 | Vulnerability · Source |
| CVE-2022-50857 | suse_vex | SUSE CVE CVE-2022-50857 | known affected: 61 known not affected: 193 | 2026-07-25T17:04:21+00:00 | Vulnerability · Source |
| CVE-2023-3355 | suse_vex | SUSE CVE CVE-2023-3355 | known not affected: 361 | 2026-07-25T17:03:23+00:00 | Vulnerability · Source |
| CVE-2023-7216 | suse_vex | SUSE CVE CVE-2023-7216 | known affected: 3 known not affected: 74 | 2026-07-25T17:02:46+00:00 | Vulnerability · Source |
| CVE-2023-29454 | suse_vex | SUSE CVE CVE-2023-29454 | known not affected: 21 recommended: 50 | 2026-07-25T17:02:20+00:00 | Vulnerability · Source |
| CVE-2023-31554 | suse_vex | SUSE CVE CVE-2023-31554 | known not affected: 410 | 2026-07-25T17:02:08+00:00 | Vulnerability · Source |
| CVE-2023-32255 | suse_vex | SUSE CVE CVE-2023-32255 | known not affected: 416 | 2026-07-25T17:02:04+00:00 | Vulnerability · Source |
| CVE-2023-32722 | suse_vex | SUSE CVE CVE-2023-32722 | known not affected: 17 recommended: 10 | 2026-07-25T17:02:01+00:00 | Vulnerability · Source |
| CVE-2023-34322 | suse_vex | SUSE CVE CVE-2023-34322 | known affected: 239 recommended: 464 | 2026-07-25T17:01:55+00:00 | Vulnerability · Source |
| CVE-2023-35825 | suse_vex | SUSE CVE CVE-2023-35825 | recommended: 49 | 2026-07-25T17:01:49+00:00 | Vulnerability · Source |
| CVE-2023-39327 | suse_vex | SUSE CVE CVE-2023-39327 | known affected: 748 known not affected: 7 recommended: 79 | 2026-07-25T17:01:36+00:00 | Vulnerability · Source |
| CVE-2023-45468 | suse_vex | SUSE CVE CVE-2023-45468 | recommended: 18 | 2026-07-25T17:01:17+00:00 | Vulnerability · Source |
| CVE-2023-45918 | suse_vex | SUSE CVE CVE-2023-45918 | known affected: 616 known not affected: 92 recommended: 425 | 2026-07-25T17:01:13+00:00 | Vulnerability · Source |
| CVE-2023-46839 | suse_vex | SUSE CVE CVE-2023-46839 | known affected: 361 recommended: 390 | 2026-07-25T17:01:07+00:00 | Vulnerability · Source |
| CVE-2023-52444 | suse_vex | SUSE CVE CVE-2023-52444 | known not affected: 312 | 2026-07-25T17:00:56+00:00 | Vulnerability · Source |