VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-34918 | suse_vex | SUSE CVE CVE-2022-34918 | known affected: 227 known not affected: 297 recommended: 1131 | 2026-10-16T14:45:59+00:00 | Vulnerability · Source |
| CVE-2022-35205 | suse_vex | SUSE CVE CVE-2022-35205 | known affected: 420 known not affected: 43 recommended: 327 | 2026-10-16T14:45:57+00:00 | Vulnerability · Source |
| CVE-2022-35206 | suse_vex | SUSE CVE CVE-2022-35206 | known affected: 462 recommended: 327 | 2026-10-16T14:45:55+00:00 | Vulnerability · Source |
| CVE-2022-35252 | suse_vex | SUSE CVE CVE-2022-35252 | known affected: 269 recommended: 449 | 2026-10-16T14:45:53+00:00 | Vulnerability · Source |
| CVE-2022-35255 | suse_vex | SUSE CVE CVE-2022-35255 | known affected: 0 known not affected: 542 recommended: 281 | 2026-10-16T14:45:51+00:00 | Vulnerability · Source |
| CVE-2022-35260 | suse_vex | SUSE CVE CVE-2022-35260 | known affected: 304 known not affected: 199 recommended: 179 | 2026-10-16T14:45:49+00:00 | Vulnerability · Source |
| CVE-2022-35737 | suse_vex | SUSE CVE CVE-2022-35737 | known affected: 244 known not affected: 5 recommended: 549 | 2026-10-16T14:45:47+00:00 | Vulnerability · Source |
| CVE-2022-36033 | suse_vex | SUSE CVE CVE-2022-36033 | known affected: 6 recommended: 48 | 2026-10-16T14:45:45+00:00 | Vulnerability · Source |
| CVE-2022-36056 | suse_vex | SUSE CVE CVE-2022-36056 | known affected: 0 known not affected: 8 recommended: 42 | 2026-10-16T14:45:44+00:00 | Vulnerability · Source |
| CVE-2022-36123 | suse_vex | SUSE CVE CVE-2022-36123 | known affected: 0 known not affected: 357 | 2026-10-16T14:45:42+00:00 | Vulnerability · Source |
| CVE-2022-36314 | suse_vex | SUSE CVE CVE-2022-36314 | known affected: 1 recommended: 453 | 2026-10-16T14:45:39+00:00 | Vulnerability · Source |
| CVE-2022-36318 | suse_vex | SUSE CVE CVE-2022-36318 | known affected: 1 recommended: 461 | 2026-10-16T14:45:37+00:00 | Vulnerability · Source |
| CVE-2022-36319 | suse_vex | SUSE CVE CVE-2022-36319 | known affected: 1 recommended: 461 | 2026-10-16T14:45:35+00:00 | Vulnerability · Source |
| CVE-2022-36402 | suse_vex | SUSE CVE CVE-2022-36402 | known affected: 388 known not affected: 493 recommended: 438 | 2026-10-16T14:45:33+00:00 | Vulnerability · Source |
| CVE-2022-36764 | suse_vex | SUSE CVE CVE-2022-36764 | known not affected: 314 recommended: 37 | 2026-10-16T14:45:31+00:00 | Vulnerability · Source |
| CVE-2022-36765 | suse_vex | SUSE CVE CVE-2022-36765 | known affected: 247 recommended: 78 | 2026-10-16T14:45:30+00:00 | Vulnerability · Source |
| CVE-2022-36879 | suse_vex | SUSE CVE CVE-2022-36879 | known affected: 237 recommended: 1554 | 2026-10-16T14:45:28+00:00 | Vulnerability · Source |
| CVE-2022-36946 | suse_vex | SUSE CVE CVE-2022-36946 | known affected: 239 recommended: 1790 | 2026-10-16T14:45:26+00:00 | Vulnerability · Source |
| CVE-2022-37290 | suse_vex | SUSE CVE CVE-2022-37290 | known affected: 102 recommended: 260 | 2026-10-16T14:45:24+00:00 | Vulnerability · Source |
| CVE-2022-37434 | suse_vex | SUSE CVE CVE-2022-37434 | known affected: 237 known not affected: 4766 recommended: 1425 | 2026-10-16T14:45:22+00:00 | Vulnerability · Source |
| CVE-2022-37454 | suse_vex | SUSE CVE CVE-2022-37454 | known affected: 260 known not affected: 744 recommended: 5053 | 2026-10-16T14:45:19+00:00 | Vulnerability · Source |
| CVE-2022-37865 | suse_vex | SUSE CVE CVE-2022-37865 | recommended: 146 | 2026-10-16T14:45:17+00:00 | Vulnerability · Source |
| CVE-2022-37866 | suse_vex | SUSE CVE CVE-2022-37866 | recommended: 146 | 2026-10-16T14:45:15+00:00 | Vulnerability · Source |
| CVE-2022-37967 | suse_vex | SUSE CVE CVE-2022-37967 | known affected: 272 known not affected: 103 recommended: 1059 | 2026-10-16T14:45:13+00:00 | Vulnerability · Source |
| CVE-2022-38023 | suse_vex | SUSE CVE CVE-2022-38023 | known affected: 272 known not affected: 106 recommended: 2502 | 2026-10-16T14:45:10+00:00 | Vulnerability · Source |
| CVE-2022-38096 | suse_vex | SUSE CVE CVE-2022-38096 | known affected: 321 known not affected: 291 recommended: 1308 | 2026-10-16T14:45:08+00:00 | Vulnerability · Source |
| CVE-2022-38126 | suse_vex | SUSE CVE CVE-2022-38126 | known affected: 395 known not affected: 1 recommended: 462 | 2026-10-16T14:45:06+00:00 | Vulnerability · Source |
| CVE-2022-38127 | suse_vex | SUSE CVE CVE-2022-38127 | known affected: 394 known not affected: 1 recommended: 462 | 2026-10-16T14:45:04+00:00 | Vulnerability · Source |
| CVE-2022-38223 | suse_vex | SUSE CVE CVE-2022-38223 | known affected: 423 known not affected: 6 recommended: 42 | 2026-10-16T14:45:02+00:00 | Vulnerability · Source |
| CVE-2022-38472 | suse_vex | SUSE CVE CVE-2022-38472 | known affected: 2 recommended: 461 | 2026-10-16T14:45:00+00:00 | Vulnerability · Source |
| CVE-2022-38478 | suse_vex | SUSE CVE CVE-2022-38478 | known affected: 2 recommended: 461 | 2026-10-16T14:44:58+00:00 | Vulnerability · Source |
| CVE-2022-38528 | suse_vex | SUSE CVE CVE-2022-38528 | recommended: 6 | 2026-10-16T14:44:56+00:00 | Vulnerability · Source |
| CVE-2022-38533 | suse_vex | SUSE CVE CVE-2022-38533 | known affected: 394 recommended: 462 | 2026-10-16T14:44:54+00:00 | Vulnerability · Source |
| CVE-2022-38648 | suse_vex | SUSE CVE CVE-2022-38648 | recommended: 132 | 2026-10-16T14:44:51+00:00 | Vulnerability · Source |
| CVE-2022-38749 | suse_vex | SUSE CVE CVE-2022-38749 | known affected: 400 recommended: 51 | 2026-10-16T14:44:49+00:00 | Vulnerability · Source |
| CVE-2022-38750 | suse_vex | SUSE CVE CVE-2022-38750 | known affected: 400 recommended: 51 | 2026-10-16T14:44:47+00:00 | Vulnerability · Source |
| CVE-2022-38752 | suse_vex | SUSE CVE CVE-2022-38752 | known affected: 400 recommended: 61 | 2026-10-16T14:44:44+00:00 | Vulnerability · Source |
| CVE-2022-39188 | suse_vex | SUSE CVE CVE-2022-39188 | known affected: 237 known not affected: 308 recommended: 1825 | 2026-10-16T14:44:41+00:00 | Vulnerability · Source |
| CVE-2022-39190 | suse_vex | SUSE CVE CVE-2022-39190 | known affected: 237 known not affected: 243 recommended: 1036 | 2026-10-16T14:44:39+00:00 | Vulnerability · Source |
| CVE-2022-39253 | suse_vex | SUSE CVE CVE-2022-39253 | known affected: 88 known not affected: 135 recommended: 683 | 2026-10-16T14:44:36+00:00 | Vulnerability · Source |
| CVE-2022-39260 | suse_vex | SUSE CVE CVE-2022-39260 | known affected: 88 known not affected: 135 recommended: 674 | 2026-10-16T14:44:33+00:00 | Vulnerability · Source |
| CVE-2022-39282 | suse_vex | SUSE CVE CVE-2022-39282 | recommended: 224 | 2026-10-16T14:44:31+00:00 | Vulnerability · Source |
| CVE-2022-39318 | suse_vex | SUSE CVE CVE-2022-39318 | recommended: 214 | 2026-10-16T14:44:28+00:00 | Vulnerability · Source |
| CVE-2022-39319 | suse_vex | SUSE CVE CVE-2022-39319 | recommended: 214 | 2026-10-16T14:44:25+00:00 | Vulnerability · Source |
| CVE-2022-39377 | suse_vex | SUSE CVE CVE-2022-39377 | known affected: 394 known not affected: 110 recommended: 41 | 2026-10-16T14:44:23+00:00 | Vulnerability · Source |
| CVE-2022-39842 | suse_vex | SUSE CVE CVE-2022-39842 | known affected: 0 known not affected: 566 | 2026-10-16T14:44:20+00:00 | Vulnerability · Source |
| CVE-2022-40023 | suse_vex | SUSE CVE CVE-2022-40023 | known affected: 24 recommended: 61 | 2026-10-16T14:44:17+00:00 | Vulnerability · Source |
| CVE-2022-40303 | suse_vex | SUSE CVE CVE-2022-40303 | known affected: 254 known not affected: 97 recommended: 586 | 2026-10-16T14:44:15+00:00 | Vulnerability · Source |
| CVE-2022-40304 | suse_vex | SUSE CVE CVE-2022-40304 | known affected: 254 known not affected: 96 recommended: 590 | 2026-10-16T14:44:12+00:00 | Vulnerability · Source |
| CVE-2022-40307 | suse_vex | SUSE CVE CVE-2022-40307 | known affected: 395 known not affected: 39 recommended: 458 | 2026-10-16T14:44:09+00:00 | Vulnerability · Source |