VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
100563 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-28282 | suse_vex | SUSE CVE CVE-2022-28282 | known affected: 3 known not affected: 126 recommended: 405 | 2026-10-16T14:49:08+00:00 | Vulnerability · Source |
| CVE-2022-28284 | suse_vex | SUSE CVE CVE-2022-28284 | known affected: 3 known not affected: 126 recommended: 9 | 2026-10-16T14:49:04+00:00 | Vulnerability · Source |
| CVE-2022-28286 | suse_vex | SUSE CVE CVE-2022-28286 | known affected: 3 known not affected: 126 recommended: 405 | 2026-10-16T14:49:02+00:00 | Vulnerability · Source |
| CVE-2022-28287 | suse_vex | SUSE CVE CVE-2022-28287 | known affected: 3 known not affected: 126 recommended: 9 | 2026-10-16T14:49:00+00:00 | Vulnerability · Source |
| CVE-2022-28289 | suse_vex | SUSE CVE CVE-2022-28289 | known affected: 3 known not affected: 126 recommended: 405 | 2026-10-16T14:48:58+00:00 | Vulnerability · Source |
| CVE-2022-28321 | suse_vex | SUSE CVE CVE-2022-28321 | known affected: 0 known not affected: 273 | 2026-10-16T14:48:56+00:00 | Vulnerability · Source |
| CVE-2022-28330 | suse_vex | SUSE CVE CVE-2022-28330 | known affected: 0 known not affected: 337 recommended: 54 | 2026-10-16T14:48:54+00:00 | Vulnerability · Source |
| CVE-2022-28349 | suse_vex | SUSE CVE CVE-2022-28349 | known affected: 0 known not affected: 418 | 2026-10-16T14:48:52+00:00 | Vulnerability · Source |
| CVE-2022-28390 | suse_vex | SUSE CVE CVE-2022-28390 | known affected: 216 known not affected: 4 recommended: 1536 | 2026-10-16T14:48:49+00:00 | Vulnerability · Source |
| CVE-2022-28463 | suse_vex | SUSE CVE CVE-2022-28463 | known affected: 1 recommended: 581 | 2026-10-16T14:48:47+00:00 | Vulnerability · Source |
| CVE-2022-28506 | suse_vex | SUSE CVE CVE-2022-28506 | known affected: 0 known not affected: 177 recommended: 100 | 2026-10-16T14:48:45+00:00 | Vulnerability · Source |
| CVE-2022-28614 | suse_vex | SUSE CVE CVE-2022-28614 | known affected: 395 recommended: 560 | 2026-10-16T14:48:44+00:00 | Vulnerability · Source |
| CVE-2022-28615 | suse_vex | SUSE CVE CVE-2022-28615 | known affected: 395 recommended: 560 | 2026-10-16T14:48:42+00:00 | Vulnerability · Source |
| CVE-2022-28737 | suse_vex | SUSE CVE CVE-2022-28737 | known affected: 294 recommended: 187 | 2026-10-16T14:48:40+00:00 | Vulnerability · Source |
| CVE-2022-28893 | suse_vex | SUSE CVE CVE-2022-28893 | known affected: 357 known not affected: 300 recommended: 928 | 2026-10-16T14:48:38+00:00 | Vulnerability · Source |
| CVE-2022-29154 | suse_vex | SUSE CVE CVE-2022-29154 | known affected: 395 recommended: 97 | 2026-10-16T14:48:36+00:00 | Vulnerability · Source |
| CVE-2022-29155 | suse_vex | SUSE CVE CVE-2022-29155 | known affected: 350 recommended: 718 | 2026-10-16T14:48:34+00:00 | Vulnerability · Source |
| CVE-2022-29156 | suse_vex | SUSE CVE CVE-2022-29156 | known affected: 219 known not affected: 304 recommended: 733 | 2026-10-16T14:48:32+00:00 | Vulnerability · Source |
| CVE-2022-29162 | suse_vex | SUSE CVE CVE-2022-29162 | known affected: 216 known not affected: 49 recommended: 638 | 2026-10-16T14:48:29+00:00 | Vulnerability · Source |
| CVE-2022-29177 | suse_vex | SUSE CVE CVE-2022-29177 | recommended: 5 | 2026-10-16T14:48:27+00:00 | Vulnerability · Source |
| CVE-2022-29217 | suse_vex | SUSE CVE CVE-2022-29217 | known affected: 282 known not affected: 1 recommended: 236 | 2026-10-16T14:48:25+00:00 | Vulnerability · Source |
| CVE-2022-29527 | suse_vex | SUSE CVE CVE-2022-29527 | known affected: 394 recommended: 64 | 2026-10-16T14:48:22+00:00 | Vulnerability · Source |
| CVE-2022-29581 | suse_vex | SUSE CVE CVE-2022-29581 | known affected: 236 known not affected: 168 recommended: 1557 | 2026-10-16T14:48:19+00:00 | Vulnerability · Source |
| CVE-2022-29824 | suse_vex | SUSE CVE CVE-2022-29824 | known affected: 216 known not affected: 62 recommended: 704 | 2026-10-16T14:48:17+00:00 | Vulnerability · Source |
| CVE-2022-29901 | suse_vex | SUSE CVE CVE-2022-29901 | known affected: 219 recommended: 1804 | 2026-10-16T14:48:15+00:00 | Vulnerability · Source |
| CVE-2022-29909 | suse_vex | SUSE CVE CVE-2022-29909 | known affected: 0 known not affected: 4 recommended: 407 | 2026-10-16T14:48:14+00:00 | Vulnerability · Source |
| CVE-2022-29914 | suse_vex | SUSE CVE CVE-2022-29914 | known affected: 0 known not affected: 4 recommended: 407 | 2026-10-16T14:48:12+00:00 | Vulnerability · Source |
| CVE-2022-29916 | suse_vex | SUSE CVE CVE-2022-29916 | known affected: 0 known not affected: 4 recommended: 407 | 2026-10-16T14:48:11+00:00 | Vulnerability · Source |
| CVE-2022-29917 | suse_vex | SUSE CVE CVE-2022-29917 | known affected: 0 known not affected: 4 recommended: 407 | 2026-10-16T14:48:09+00:00 | Vulnerability · Source |
| CVE-2022-30115 | suse_vex | SUSE CVE CVE-2022-30115 | known affected: 304 known not affected: 221 recommended: 179 | 2026-10-16T14:48:07+00:00 | Vulnerability · Source |
| CVE-2022-30786 | suse_vex | SUSE CVE CVE-2022-30786 | recommended: 250 | 2026-10-16T14:48:05+00:00 | Vulnerability · Source |
| CVE-2022-30788 | suse_vex | SUSE CVE CVE-2022-30788 | recommended: 255 | 2026-10-16T14:48:02+00:00 | Vulnerability · Source |
| CVE-2022-30789 | suse_vex | SUSE CVE CVE-2022-30789 | recommended: 250 | 2026-10-16T14:47:59+00:00 | Vulnerability · Source |
| CVE-2022-31015 | suse_vex | SUSE CVE CVE-2022-31015 | known affected: 0 known not affected: 83 recommended: 22 | 2026-10-16T14:47:57+00:00 | Vulnerability · Source |
| CVE-2022-31022 | suse_vex | SUSE CVE CVE-2022-31022 | recommended: 5 | 2026-10-16T14:47:54+00:00 | Vulnerability · Source |
| CVE-2022-31081 | suse_vex | SUSE CVE CVE-2022-31081 | known affected: 424 recommended: 43 | 2026-10-16T14:47:52+00:00 | Vulnerability · Source |
| CVE-2022-31197 | suse_vex | SUSE CVE CVE-2022-31197 | known affected: 395 known not affected: 23 recommended: 63 | 2026-10-16T14:47:49+00:00 | Vulnerability · Source |
| CVE-2022-31629 | suse_vex | SUSE CVE CVE-2022-31629 | recommended: 4876 | 2026-10-16T14:47:46+00:00 | Vulnerability · Source |
| CVE-2022-31737 | suse_vex | SUSE CVE CVE-2022-31737 | known affected: 0 known not affected: 1 recommended: 407 | 2026-10-16T14:47:43+00:00 | Vulnerability · Source |
| CVE-2022-31740 | suse_vex | SUSE CVE CVE-2022-31740 | known affected: 0 known not affected: 1 recommended: 407 | 2026-10-16T14:47:40+00:00 | Vulnerability · Source |
| CVE-2022-31741 | suse_vex | SUSE CVE CVE-2022-31741 | recommended: 1694 | 2026-10-16T14:47:37+00:00 | Vulnerability · Source |
| CVE-2022-31747 | suse_vex | SUSE CVE CVE-2022-31747 | known affected: 0 known not affected: 1 recommended: 407 | 2026-10-16T14:47:35+00:00 | Vulnerability · Source |
| CVE-2022-31799 | suse_vex | SUSE CVE CVE-2022-31799 | recommended: 102 | 2026-10-16T14:47:32+00:00 | Vulnerability · Source |
| CVE-2022-31813 | suse_vex | SUSE CVE CVE-2022-31813 | known affected: 394 recommended: 560 | 2026-10-16T14:47:29+00:00 | Vulnerability · Source |
| CVE-2022-32082 | suse_vex | SUSE CVE CVE-2022-32082 | known affected: 0 known not affected: 272 recommended: 247 | 2026-10-16T14:47:27+00:00 | Vulnerability · Source |
| CVE-2022-32083 | suse_vex | SUSE CVE CVE-2022-32083 | known affected: 0 known not affected: 231 recommended: 386 | 2026-10-16T14:47:26+00:00 | Vulnerability · Source |
| CVE-2022-32084 | suse_vex | SUSE CVE CVE-2022-32084 | known affected: 0 known not affected: 96 recommended: 478 | 2026-10-16T14:47:24+00:00 | Vulnerability · Source |
| CVE-2022-32085 | suse_vex | SUSE CVE CVE-2022-32085 | known affected: 9 known not affected: 96 recommended: 386 | 2026-10-16T14:47:21+00:00 | Vulnerability · Source |
| CVE-2022-32087 | suse_vex | SUSE CVE CVE-2022-32087 | known affected: 0 known not affected: 96 recommended: 386 | 2026-10-16T14:47:19+00:00 | Vulnerability · Source |
| CVE-2022-32088 | suse_vex | SUSE CVE CVE-2022-32088 | known affected: 0 known not affected: 96 recommended: 386 | 2026-10-16T14:47:17+00:00 | Vulnerability · Source |