VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100569 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-32886 | suse_vex | SUSE CVE CVE-2022-32886 | known affected: 1 recommended: 1033 | 2026-10-16T14:46:43+00:00 | Vulnerability · Source |
| CVE-2022-32893 | suse_vex | SUSE CVE CVE-2022-32893 | known affected: 47 recommended: 895 | 2026-10-16T14:46:41+00:00 | Vulnerability · Source |
| CVE-2022-32981 | suse_vex | SUSE CVE CVE-2022-32981 | known affected: 0 known not affected: 409 | 2026-10-16T14:46:39+00:00 | Vulnerability · Source |
| CVE-2022-33065 | suse_vex | SUSE CVE CVE-2022-33065 | known affected: 57 recommended: 125 | 2026-10-16T14:46:37+00:00 | Vulnerability · Source |
| CVE-2022-33068 | suse_vex | SUSE CVE CVE-2022-33068 | known affected: 394 known not affected: 149 recommended: 472 | 2026-10-16T14:46:35+00:00 | Vulnerability · Source |
| CVE-2022-33196 | suse_vex | SUSE CVE CVE-2022-33196 | recommended: 71 | 2026-10-16T14:46:33+00:00 | Vulnerability · Source |
| CVE-2022-33740 | suse_vex | SUSE CVE CVE-2022-33740 | known affected: 249 known not affected: 227 recommended: 1546 | 2026-10-16T14:46:30+00:00 | Vulnerability · Source |
| CVE-2022-33743 | suse_vex | SUSE CVE CVE-2022-33743 | known affected: 259 known not affected: 683 recommended: 644 | 2026-10-16T14:46:28+00:00 | Vulnerability · Source |
| CVE-2022-33972 | suse_vex | SUSE CVE CVE-2022-33972 | known affected: 0 known not affected: 1 recommended: 69 | 2026-10-16T14:46:26+00:00 | Vulnerability · Source |
| CVE-2022-34266 | suse_vex | SUSE CVE CVE-2022-34266 | known affected: 394 known not affected: 2 recommended: 261 | 2026-10-16T14:46:24+00:00 | Vulnerability · Source |
| CVE-2022-34469 | suse_vex | SUSE CVE CVE-2022-34469 | known affected: 1 recommended: 363 | 2026-10-16T14:46:21+00:00 | Vulnerability · Source |
| CVE-2022-34470 | suse_vex | SUSE CVE CVE-2022-34470 | known affected: 1 recommended: 482 | 2026-10-16T14:46:18+00:00 | Vulnerability · Source |
| CVE-2022-34473 | suse_vex | SUSE CVE CVE-2022-34473 | known affected: 1 recommended: 363 | 2026-10-16T14:46:17+00:00 | Vulnerability · Source |
| CVE-2022-34474 | suse_vex | SUSE CVE CVE-2022-34474 | known affected: 1 recommended: 363 | 2026-10-16T14:46:15+00:00 | Vulnerability · Source |
| CVE-2022-34475 | suse_vex | SUSE CVE CVE-2022-34475 | known affected: 1 recommended: 363 | 2026-10-16T14:46:13+00:00 | Vulnerability · Source |
| CVE-2022-34478 | suse_vex | SUSE CVE CVE-2022-34478 | known affected: 1 recommended: 474 | 2026-10-16T14:46:11+00:00 | Vulnerability · Source |
| CVE-2022-34479 | suse_vex | SUSE CVE CVE-2022-34479 | known affected: 1 recommended: 482 | 2026-10-16T14:46:09+00:00 | Vulnerability · Source |
| CVE-2022-34481 | suse_vex | SUSE CVE CVE-2022-34481 | known affected: 1 recommended: 482 | 2026-10-16T14:46:06+00:00 | Vulnerability · Source |
| CVE-2022-34484 | suse_vex | SUSE CVE CVE-2022-34484 | known affected: 1 recommended: 482 | 2026-10-16T14:46:04+00:00 | Vulnerability · Source |
| CVE-2022-34749 | suse_vex | SUSE CVE CVE-2022-34749 | recommended: 17 | 2026-10-16T14:46:02+00:00 | Vulnerability · Source |
| CVE-2022-34903 | suse_vex | SUSE CVE CVE-2022-34903 | known affected: 231 recommended: 368 | 2026-10-16T14:46:01+00:00 | Vulnerability · Source |
| 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 |