VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292108 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-39260 | suse_vex | SUSE CVE CVE-2022-39260 | known affected: 86 known not affected: 125 recommended: 659 | 2026-07-25T17:23:08+00:00 | Vulnerability · Source |
| CVE-2022-40307 | suse_vex | SUSE CVE CVE-2022-40307 | known affected: 396 known not affected: 20 recommended: 458 | 2026-07-25T17:23:07+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-40540 | suse_vex | SUSE CVE CVE-2022-40540 | known not affected: 124 | 2026-07-25T17:23:03+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-40674 | suse_vex | SUSE CVE CVE-2022-40674 | known affected: 217 recommended: 498 | 2026-07-25T17:23:00+00:00 | Vulnerability · Source |
| CVE-2022-41844 | suse_vex | SUSE CVE CVE-2022-41844 | known not affected: 330 | 2026-07-25T17:22:50+00:00 | Vulnerability · Source |
| CVE-2022-41859 | suse_vex | SUSE CVE CVE-2022-41859 | known affected: 1 known not affected: 1 recommended: 756 | 2026-07-25T17:22:47+00:00 | Vulnerability · Source |
| CVE-2022-41903 | suse_vex | SUSE CVE CVE-2022-41903 | known affected: 1 known not affected: 131 recommended: 726 | 2026-07-25T17:22:44+00:00 | Vulnerability · Source |
| CVE-2022-42010 | suse_vex | SUSE CVE CVE-2022-42010 | known affected: 254 recommended: 529 | 2026-07-25T17:22:42+00:00 | Vulnerability · Source |
| CVE-2022-42252 | suse_vex | SUSE CVE CVE-2022-42252 | known affected: 395 recommended: 537 | 2026-07-25T17:22:41+00:00 | Vulnerability · Source |
| CVE-2022-42309 | suse_vex | SUSE CVE CVE-2022-42309 | known affected: 253 recommended: 518 | 2026-07-25T17:22:39+00:00 | Vulnerability · Source |
| CVE-2022-42318 | suse_vex | SUSE CVE CVE-2022-42318 | recommended: 377 | 2026-07-25T17:22:38+00:00 | Vulnerability · Source |
| CVE-2022-42320 | suse_vex | SUSE CVE CVE-2022-42320 | known affected: 253 recommended: 518 | 2026-07-25T17:22:37+00:00 | Vulnerability · Source |
| CVE-2022-42321 | suse_vex | SUSE CVE CVE-2022-42321 | known affected: 253 recommended: 518 | 2026-07-25T17:22:35+00:00 | Vulnerability · Source |
| 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 |