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-3821 | suse_vex | SUSE CVE CVE-2022-3821 | known affected: 254 known not affected: 121 recommended: 976 | 2026-10-16T14:56:26+00:00 | Vulnerability · Source |
| CVE-2022-3872 | suse_vex | SUSE CVE CVE-2022-3872 | known affected: 2198 | 2026-10-16T14:56:24+00:00 | Vulnerability · Source |
| CVE-2022-3924 | suse_vex | SUSE CVE CVE-2022-3924 | known affected: 284 known not affected: 424 recommended: 250 | 2026-10-16T14:56:22+00:00 | Vulnerability · Source |
| CVE-2022-3977 | suse_vex | SUSE CVE CVE-2022-3977 | known affected: 0 known not affected: 384 | 2026-10-16T14:56:20+00:00 | Vulnerability · Source |
| CVE-2022-3996 | suse_vex | SUSE CVE CVE-2022-3996 | known affected: 0 known not affected: 713 recommended: 138 | 2026-10-16T14:56:18+00:00 | Vulnerability · Source |
| CVE-2022-4055 | suse_vex | SUSE CVE CVE-2022-4055 | recommended: 2 | 2026-10-16T14:56:16+00:00 | Vulnerability · Source |
| CVE-2022-4095 | suse_vex | SUSE CVE CVE-2022-4095 | known affected: 242 known not affected: 2 recommended: 1749 | 2026-10-16T14:56:14+00:00 | Vulnerability · Source |
| CVE-2022-4129 | suse_vex | SUSE CVE CVE-2022-4129 | known affected: 273 known not affected: 108 recommended: 1472 | 2026-10-16T14:56:11+00:00 | Vulnerability · Source |
| CVE-2022-4132 | suse_vex | SUSE CVE CVE-2022-4132 | known affected: 0 known not affected: 469 | 2026-10-16T14:56:09+00:00 | Vulnerability · Source |
| CVE-2022-4139 | suse_vex | SUSE CVE CVE-2022-4139 | known affected: 267 known not affected: 199 recommended: 1420 | 2026-10-16T14:56:07+00:00 | Vulnerability · Source |
| CVE-2022-4141 | suse_vex | SUSE CVE CVE-2022-4141 | known affected: 267 recommended: 407 | 2026-10-16T14:56:04+00:00 | Vulnerability · Source |
| CVE-2022-4269 | suse_vex | SUSE CVE CVE-2022-4269 | known affected: 194 known not affected: 174 recommended: 1119 | 2026-10-16T14:56:01+00:00 | Vulnerability · Source |
| CVE-2022-4285 | suse_vex | SUSE CVE CVE-2022-4285 | known affected: 480 known not affected: 1 recommended: 338 | 2026-10-16T14:56:00+00:00 | Vulnerability · Source |
| CVE-2022-4303 | suse_vex | SUSE CVE CVE-2022-4303 | recommended: 164 | 2026-10-16T14:55:58+00:00 | Vulnerability · Source |
| CVE-2022-4304 | suse_vex | SUSE CVE CVE-2022-4304 | known affected: 132 known not affected: 107 recommended: 1112 | 2026-10-16T14:55:56+00:00 | Vulnerability · Source |
| CVE-2022-4382 | suse_vex | SUSE CVE CVE-2022-4382 | known affected: 235 known not affected: 578 recommended: 798 | 2026-10-16T14:55:54+00:00 | Vulnerability · Source |
| CVE-2022-4415 | suse_vex | SUSE CVE CVE-2022-4415 | known affected: 268 recommended: 1057 | 2026-10-16T14:55:52+00:00 | Vulnerability · Source |
| CVE-2022-4450 | suse_vex | SUSE CVE CVE-2022-4450 | known affected: 273 known not affected: 407 recommended: 591 | 2026-10-16T14:55:49+00:00 | Vulnerability · Source |
| CVE-2022-4515 | suse_vex | SUSE CVE CVE-2022-4515 | known affected: 1 recommended: 60 | 2026-10-16T14:55:47+00:00 | Vulnerability · Source |
| CVE-2022-4603 | suse_vex | SUSE CVE CVE-2022-4603 | known affected: 103 recommended: 63 | 2026-10-16T14:55:44+00:00 | Vulnerability · Source |
| CVE-2022-4662 | suse_vex | SUSE CVE CVE-2022-4662 | known affected: 255 known not affected: 98 recommended: 1367 | 2026-10-16T14:55:41+00:00 | Vulnerability · Source |
| CVE-2022-4696 | suse_vex | SUSE CVE CVE-2022-4696 | known affected: 0 known not affected: 392 | 2026-10-16T14:55:39+00:00 | Vulnerability · Source |
| CVE-2022-4744 | suse_vex | SUSE CVE CVE-2022-4744 | known affected: 201 known not affected: 141 recommended: 1289 | 2026-10-16T14:55:37+00:00 | Vulnerability · Source |
| CVE-2022-4806 | suse_vex | SUSE CVE CVE-2022-4806 | recommended: 26 | 2026-10-16T14:55:35+00:00 | Vulnerability · Source |
| CVE-2022-4842 | suse_vex | SUSE CVE CVE-2022-4842 | known affected: 0 known not affected: 392 | 2026-10-16T14:55:33+00:00 | Vulnerability · Source |
| CVE-2022-4994 | suse_vex | SUSE CVE CVE-2022-4994 | known affected: 394 known not affected: 278 recommended: 161 | 2026-10-16T14:55:31+00:00 | Vulnerability · Source |
| CVE-2022-20001 | suse_vex | SUSE CVE CVE-2022-20001 | known affected: 0 known not affected: 16 recommended: 14 | 2026-10-16T14:55:27+00:00 | Vulnerability · Source |
| CVE-2022-20118 | suse_vex | SUSE CVE CVE-2022-20118 | known affected: 0 known not affected: 418 | 2026-10-16T14:55:24+00:00 | Vulnerability · Source |
| CVE-2022-20119 | suse_vex | SUSE CVE CVE-2022-20119 | known affected: 0 known not affected: 418 | 2026-10-16T14:55:23+00:00 | Vulnerability · Source |
| CVE-2022-20132 | suse_vex | SUSE CVE CVE-2022-20132 | known affected: 219 recommended: 1529 | 2026-10-16T14:55:21+00:00 | Vulnerability · Source |
| CVE-2022-20148 | suse_vex | SUSE CVE CVE-2022-20148 | known affected: 0 known not affected: 405 | 2026-10-16T14:55:19+00:00 | Vulnerability · Source |
| CVE-2022-20154 | suse_vex | SUSE CVE CVE-2022-20154 | known affected: 130 known not affected: 204 recommended: 1894 | 2026-10-16T14:55:17+00:00 | Vulnerability · Source |
| CVE-2022-20368 | suse_vex | SUSE CVE CVE-2022-20368 | known affected: 173 recommended: 1749 | 2026-10-16T14:55:15+00:00 | Vulnerability · Source |
| CVE-2022-20421 | suse_vex | SUSE CVE CVE-2022-20421 | known affected: 0 known not affected: 216 | 2026-10-16T14:55:13+00:00 | Vulnerability · Source |
| CVE-2022-20567 | suse_vex | SUSE CVE CVE-2022-20567 | known affected: 394 known not affected: 202 recommended: 204 | 2026-10-16T14:55:11+00:00 | Vulnerability · Source |
| CVE-2022-20572 | suse_vex | SUSE CVE CVE-2022-20572 | known affected: 0 known not affected: 350 recommended: 42 | 2026-10-16T14:55:09+00:00 | Vulnerability · Source |
| CVE-2022-20698 | suse_vex | SUSE CVE CVE-2022-20698 | known affected: 1 recommended: 282 | 2026-10-16T14:55:08+00:00 | Vulnerability · Source |
| CVE-2022-20785 | suse_vex | SUSE CVE CVE-2022-20785 | known affected: 59 recommended: 186 | 2026-10-16T14:55:05+00:00 | Vulnerability · Source |
| CVE-2022-21123 | suse_vex | SUSE CVE CVE-2022-21123 | known affected: 225 recommended: 1976 | 2026-10-16T14:55:02+00:00 | Vulnerability · Source |
| CVE-2022-21125 | suse_vex | SUSE CVE CVE-2022-21125 | known affected: 254 recommended: 1938 | 2026-10-16T14:54:59+00:00 | Vulnerability · Source |
| CVE-2022-21127 | suse_vex | SUSE CVE CVE-2022-21127 | recommended: 1352 | 2026-10-16T14:54:57+00:00 | Vulnerability · Source |
| CVE-2022-21131 | suse_vex | SUSE CVE CVE-2022-21131 | known affected: 0 known not affected: 91 | 2026-10-16T14:54:54+00:00 | Vulnerability · Source |
| CVE-2022-21151 | suse_vex | SUSE CVE CVE-2022-21151 | recommended: 87 | 2026-10-16T14:54:52+00:00 | Vulnerability · Source |
| CVE-2022-21166 | suse_vex | SUSE CVE CVE-2022-21166 | known affected: 216 recommended: 1977 | 2026-10-16T14:54:49+00:00 | Vulnerability · Source |
| CVE-2022-21216 | suse_vex | SUSE CVE CVE-2022-21216 | recommended: 71 | 2026-10-16T14:54:47+00:00 | Vulnerability · Source |
| CVE-2022-21233 | suse_vex | SUSE CVE CVE-2022-21233 | recommended: 81 | 2026-10-16T14:54:45+00:00 | Vulnerability · Source |
| CVE-2022-21277 | suse_vex | SUSE CVE CVE-2022-21277 | known affected: 475 known not affected: 32 recommended: 769 | 2026-10-16T14:54:43+00:00 | Vulnerability · Source |
| CVE-2022-21283 | suse_vex | SUSE CVE CVE-2022-21283 | known affected: 474 known not affected: 32 recommended: 1002 | 2026-10-16T14:54:40+00:00 | Vulnerability · Source |
| CVE-2022-21293 | suse_vex | SUSE CVE CVE-2022-21293 | known affected: 406 known not affected: 32 recommended: 1062 | 2026-10-16T14:54:37+00:00 | Vulnerability · Source |
| CVE-2022-21299 | suse_vex | SUSE CVE CVE-2022-21299 | known affected: 406 known not affected: 32 recommended: 1085 | 2026-10-16T14:54:34+00:00 | Vulnerability · Source |