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-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 |
| CVE-2022-32149 | suse_vex | SUSE CVE CVE-2022-32149 | known affected: 0 known not affected: 197 recommended: 314 | 2026-10-16T14:47:14+00:00 | Vulnerability · Source |
| CVE-2022-32205 | suse_vex | SUSE CVE CVE-2022-32205 | known affected: 254 known not affected: 183 recommended: 275 | 2026-10-16T14:47:12+00:00 | Vulnerability · Source |
| CVE-2022-32206 | suse_vex | SUSE CVE CVE-2022-32206 | known affected: 216 known not affected: 35 recommended: 493 | 2026-10-16T14:47:09+00:00 | Vulnerability · Source |
| CVE-2022-32207 | suse_vex | SUSE CVE CVE-2022-32207 | known affected: 254 known not affected: 183 recommended: 285 | 2026-10-16T14:47:07+00:00 | Vulnerability · Source |
| CVE-2022-32208 | suse_vex | SUSE CVE CVE-2022-32208 | known affected: 216 recommended: 518 | 2026-10-16T14:47:06+00:00 | Vulnerability · Source |
| CVE-2022-32221 | suse_vex | SUSE CVE CVE-2022-32221 | known affected: 319 known not affected: 22 recommended: 480 | 2026-10-16T14:47:04+00:00 | Vulnerability · Source |
| CVE-2022-32250 | suse_vex | SUSE CVE CVE-2022-32250 | known affected: 237 recommended: 1371 | 2026-10-16T14:47:02+00:00 | Vulnerability · Source |
| CVE-2022-32296 | suse_vex | SUSE CVE CVE-2022-32296 | known affected: 274 known not affected: 116 recommended: 830 | 2026-10-16T14:47:00+00:00 | Vulnerability · Source |
| CVE-2022-32546 | suse_vex | SUSE CVE CVE-2022-32546 | recommended: 521 | 2026-10-16T14:46:58+00:00 | Vulnerability · Source |
| CVE-2022-32742 | suse_vex | SUSE CVE CVE-2022-32742 | known affected: 231 known not affected: 403 recommended: 3270 | 2026-10-16T14:46:56+00:00 | Vulnerability · Source |
| CVE-2022-32744 | suse_vex | SUSE CVE CVE-2022-32744 | known affected: 231 known not affected: 1073 recommended: 1290 | 2026-10-16T14:46:53+00:00 | Vulnerability · Source |
| CVE-2022-32745 | suse_vex | SUSE CVE CVE-2022-32745 | known affected: 231 known not affected: 2018 recommended: 1290 | 2026-10-16T14:46:50+00:00 | Vulnerability · Source |
| CVE-2022-32816 | suse_vex | SUSE CVE CVE-2022-32816 | known affected: 1 recommended: 969 | 2026-10-16T14:46:48+00:00 | Vulnerability · Source |
| CVE-2022-32885 | suse_vex | SUSE CVE CVE-2022-32885 | known affected: 12 recommended: 843 | 2026-10-16T14:46:45+00:00 | Vulnerability · Source |
| 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 |