VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283120 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-34483 | suse_vex | SUSE CVE CVE-2022-34483 | known affected: 1 recommended: 349 | 2026-07-19T18:11:01+00:00 | Vulnerability · Source |
| CVE-2022-34484 | suse_vex | SUSE CVE CVE-2022-34484 | known affected: 1 recommended: 463 | 2026-07-19T18:11:00+00:00 | Vulnerability · Source |
| CVE-2022-34903 | suse_vex | SUSE CVE CVE-2022-34903 | known affected: 231 recommended: 356 | 2026-07-19T18:10:59+00:00 | Vulnerability · Source |
| CVE-2022-35737 | suse_vex | SUSE CVE CVE-2022-35737 | known affected: 244 known not affected: 5 recommended: 524 | 2026-07-19T18:10:57+00:00 | Vulnerability · Source |
| CVE-2022-36033 | suse_vex | SUSE CVE CVE-2022-36033 | known affected: 5 recommended: 46 | 2026-07-19T18:10:56+00:00 | Vulnerability · Source |
| CVE-2022-36763 | suse_vex | SUSE CVE CVE-2022-36763 | known not affected: 272 recommended: 38 | 2026-07-19T18:10:55+00:00 | Vulnerability · Source |
| CVE-2022-37035 | suse_vex | SUSE CVE CVE-2022-37035 | recommended: 276 | 2026-07-19T18:10:53+00:00 | Vulnerability · Source |
| CVE-2022-37436 | suse_vex | SUSE CVE CVE-2022-37436 | known affected: 395 recommended: 412 | 2026-07-19T18:10:52+00:00 | Vulnerability · Source |
| CVE-2022-38090 | suse_vex | SUSE CVE CVE-2022-38090 | recommended: 65 | 2026-07-19T18:10:50+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 445 | 2026-07-19T18:10:49+00:00 | Vulnerability · Source |
| CVE-2022-38127 | suse_vex | SUSE CVE CVE-2022-38127 | known affected: 394 known not affected: 1 recommended: 445 | 2026-07-19T18:10:48+00:00 | Vulnerability · Source |
| CVE-2022-38178 | suse_vex | SUSE CVE CVE-2022-38178 | known affected: 254 known not affected: 16 recommended: 1021 | 2026-07-19T18:10:46+00:00 | Vulnerability · Source |
| CVE-2022-38472 | suse_vex | SUSE CVE CVE-2022-38472 | known affected: 2 recommended: 445 | 2026-07-19T18:10:45+00:00 | Vulnerability · Source |
| CVE-2022-38473 | suse_vex | SUSE CVE CVE-2022-38473 | known affected: 2 recommended: 445 | 2026-07-19T18:10:44+00:00 | Vulnerability · Source |
| CVE-2022-38648 | suse_vex | SUSE CVE CVE-2022-38648 | recommended: 114 | 2026-07-19T18:10:43+00:00 | Vulnerability · Source |
| CVE-2022-38749 | suse_vex | SUSE CVE CVE-2022-38749 | known affected: 399 recommended: 49 | 2026-07-19T18:10:41+00:00 | Vulnerability · Source |
| CVE-2022-38750 | suse_vex | SUSE CVE CVE-2022-38750 | known affected: 399 recommended: 49 | 2026-07-19T18:10:40+00:00 | Vulnerability · Source |
| CVE-2022-38752 | suse_vex | SUSE CVE CVE-2022-38752 | known affected: 399 recommended: 59 | 2026-07-19T18:10:39+00:00 | Vulnerability · Source |
| CVE-2022-38784 | suse_vex | SUSE CVE CVE-2022-38784 | known affected: 1 recommended: 449 | 2026-07-19T18:10:37+00:00 | Vulnerability · Source |
| CVE-2022-39028 | suse_vex | SUSE CVE CVE-2022-39028 | known affected: 394 known not affected: 353 recommended: 150 | 2026-07-19T18:10:36+00:00 | Vulnerability · Source |
| CVE-2022-39282 | suse_vex | SUSE CVE CVE-2022-39282 | recommended: 195 | 2026-07-19T18:10:35+00:00 | Vulnerability · Source |
| CVE-2022-39318 | suse_vex | SUSE CVE CVE-2022-39318 | recommended: 185 | 2026-07-19T18:10:34+00:00 | Vulnerability · Source |
| CVE-2022-40146 | suse_vex | SUSE CVE CVE-2022-40146 | recommended: 114 | 2026-07-19T18:10:32+00:00 | Vulnerability · Source |
| CVE-2022-40303 | suse_vex | SUSE CVE CVE-2022-40303 | known affected: 254 known not affected: 97 recommended: 564 | 2026-07-19T18:10:31+00:00 | Vulnerability · Source |
| CVE-2022-40674 | suse_vex | SUSE CVE CVE-2022-40674 | known affected: 217 recommended: 486 | 2026-07-19T18:10:30+00:00 | Vulnerability · Source |
| CVE-2022-40958 | suse_vex | SUSE CVE CVE-2022-40958 | known affected: 1 recommended: 425 | 2026-07-19T18:10:28+00:00 | Vulnerability · Source |
| CVE-2022-40962 | suse_vex | SUSE CVE CVE-2022-40962 | known affected: 1 recommended: 425 | 2026-07-19T18:10:27+00:00 | Vulnerability · Source |
| CVE-2022-41741 | suse_vex | SUSE CVE CVE-2022-41741 | known affected: 394 recommended: 90 | 2026-07-19T18:10:26+00:00 | Vulnerability · Source |
| CVE-2022-41859 | suse_vex | SUSE CVE CVE-2022-41859 | known affected: 1 known not affected: 1 recommended: 712 | 2026-07-19T18:10:24+00:00 | Vulnerability · Source |
| CVE-2022-41860 | suse_vex | SUSE CVE CVE-2022-41860 | known affected: 1 recommended: 717 | 2026-07-19T18:10:23+00:00 | Vulnerability · Source |
| CVE-2022-41861 | suse_vex | SUSE CVE CVE-2022-41861 | known affected: 1 recommended: 717 | 2026-07-19T18:10:22+00:00 | Vulnerability · Source |
| CVE-2022-41877 | suse_vex | SUSE CVE CVE-2022-41877 | recommended: 145 | 2026-07-19T18:10:20+00:00 | Vulnerability · Source |
| CVE-2022-41946 | suse_vex | SUSE CVE CVE-2022-41946 | known affected: 411 known not affected: 1 recommended: 39 | 2026-07-19T18:10:19+00:00 | Vulnerability · Source |
| CVE-2022-42003 | suse_vex | SUSE CVE CVE-2022-42003 | known affected: 394 recommended: 68 | 2026-07-19T18:10:18+00:00 | Vulnerability · Source |
| CVE-2022-42010 | suse_vex | SUSE CVE CVE-2022-42010 | known affected: 254 recommended: 517 | 2026-07-19T18:10:17+00:00 | Vulnerability · Source |
| CVE-2022-42252 | suse_vex | SUSE CVE CVE-2022-42252 | known affected: 395 recommended: 501 | 2026-07-19T18:10:15+00:00 | Vulnerability · Source |
| CVE-2022-42867 | suse_vex | SUSE CVE CVE-2022-42867 | known affected: 1 recommended: 854 | 2026-07-19T18:10:14+00:00 | Vulnerability · Source |
| CVE-2022-42916 | suse_vex | SUSE CVE CVE-2022-42916 | known affected: 271 known not affected: 140 recommended: 253 | 2026-07-19T18:10:12+00:00 | Vulnerability · Source |
| CVE-2022-42927 | suse_vex | SUSE CVE CVE-2022-42927 | known affected: 1 recommended: 378 | 2026-07-19T18:10:11+00:00 | Vulnerability · Source |
| CVE-2022-42929 | suse_vex | SUSE CVE CVE-2022-42929 | known affected: 1 recommended: 378 | 2026-07-19T18:10:10+00:00 | Vulnerability · Source |
| CVE-2022-44267 | suse_vex | SUSE CVE CVE-2022-44267 | known affected: 45 known not affected: 58 recommended: 534 | 2026-07-19T18:10:08+00:00 | Vulnerability · Source |
| CVE-2022-44617 | suse_vex | SUSE CVE CVE-2022-44617 | known affected: 394 recommended: 158 | 2026-07-19T18:10:07+00:00 | Vulnerability · Source |
| CVE-2022-44638 | suse_vex | SUSE CVE CVE-2022-44638 | known affected: 411 recommended: 215 | 2026-07-19T18:10:06+00:00 | Vulnerability · Source |
| CVE-2022-44792 | suse_vex | SUSE CVE CVE-2022-44792 | known affected: 31 known not affected: 2 recommended: 190 | 2026-07-19T18:10:05+00:00 | Vulnerability · Source |
| CVE-2022-45404 | suse_vex | SUSE CVE CVE-2022-45404 | known affected: 1 recommended: 393 | 2026-07-19T18:10:03+00:00 | Vulnerability · Source |
| CVE-2022-45410 | suse_vex | SUSE CVE CVE-2022-45410 | known affected: 1 recommended: 393 | 2026-07-19T18:10:02+00:00 | Vulnerability · Source |
| CVE-2022-45411 | suse_vex | SUSE CVE CVE-2022-45411 | known affected: 1 recommended: 393 | 2026-07-19T18:10:01+00:00 | Vulnerability · Source |
| CVE-2022-45418 | suse_vex | SUSE CVE CVE-2022-45418 | known affected: 1 recommended: 393 | 2026-07-19T18:10:00+00:00 | Vulnerability · Source |
| CVE-2022-45421 | suse_vex | SUSE CVE CVE-2022-45421 | known affected: 1 recommended: 393 | 2026-07-19T18:09:58+00:00 | Vulnerability · Source |
| CVE-2022-45939 | suse_vex | SUSE CVE CVE-2022-45939 | known affected: 120 recommended: 433 | 2026-07-19T18:09:57+00:00 | Vulnerability · Source |