VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50125 | suse_vex | SUSE CVE CVE-2022-50125 | known affected: 344 known not affected: 385 recommended: 260 | 2026-10-16T14:10:04+00:00 | Vulnerability · Source |
| CVE-2022-50126 | suse_vex | SUSE CVE CVE-2022-50126 | known affected: 497 known not affected: 189 recommended: 384 | 2026-10-16T14:10:02+00:00 | Vulnerability · Source |
| CVE-2022-50127 | suse_vex | SUSE CVE CVE-2022-50127 | known affected: 467 known not affected: 268 recommended: 388 | 2026-10-16T14:10:00+00:00 | Vulnerability · Source |
| CVE-2022-50130 | suse_vex | SUSE CVE CVE-2022-50130 | known affected: 67 known not affected: 454 recommended: 20 | 2026-10-16T14:09:57+00:00 | Vulnerability · Source |
| CVE-2022-50134 | suse_vex | SUSE CVE CVE-2022-50134 | known affected: 510 known not affected: 180 recommended: 229 | 2026-10-16T14:09:55+00:00 | Vulnerability · Source |
| CVE-2022-50136 | suse_vex | SUSE CVE CVE-2022-50136 | known affected: 370 known not affected: 357 recommended: 347 | 2026-10-16T14:09:53+00:00 | Vulnerability · Source |
| CVE-2022-50137 | suse_vex | SUSE CVE CVE-2022-50137 | known affected: 344 known not affected: 385 recommended: 280 | 2026-10-16T14:09:50+00:00 | Vulnerability · Source |
| CVE-2022-50140 | suse_vex | SUSE CVE CVE-2022-50140 | known affected: 491 known not affected: 251 recommended: 273 | 2026-10-16T14:09:48+00:00 | Vulnerability · Source |
| CVE-2022-50141 | suse_vex | SUSE CVE CVE-2022-50141 | known affected: 464 known not affected: 233 recommended: 296 | 2026-10-16T14:09:46+00:00 | Vulnerability · Source |
| CVE-2022-50142 | suse_vex | SUSE CVE CVE-2022-50142 | known affected: 370 known not affected: 357 recommended: 273 | 2026-10-16T14:09:44+00:00 | Vulnerability · Source |
| CVE-2022-50143 | suse_vex | SUSE CVE CVE-2022-50143 | known affected: 370 known not affected: 355 recommended: 314 | 2026-10-16T14:09:41+00:00 | Vulnerability · Source |
| CVE-2022-50146 | suse_vex | SUSE CVE CVE-2022-50146 | known affected: 403 known not affected: 268 recommended: 350 | 2026-10-16T14:09:39+00:00 | Vulnerability · Source |
| CVE-2022-50147 | suse_vex | SUSE CVE CVE-2022-50147 | known affected: 0 known not affected: 521 recommended: 54 | 2026-10-16T14:09:37+00:00 | Vulnerability · Source |
| CVE-2022-50151 | suse_vex | SUSE CVE CVE-2022-50151 | known affected: 344 known not affected: 385 recommended: 260 | 2026-10-16T14:09:35+00:00 | Vulnerability · Source |
| CVE-2022-50154 | suse_vex | SUSE CVE CVE-2022-50154 | known affected: 344 known not affected: 386 recommended: 260 | 2026-10-16T14:09:32+00:00 | Vulnerability · Source |
| CVE-2022-50156 | suse_vex | SUSE CVE CVE-2022-50156 | known affected: 370 known not affected: 357 recommended: 327 | 2026-10-16T14:09:29+00:00 | Vulnerability · Source |
| CVE-2022-50157 | suse_vex | SUSE CVE CVE-2022-50157 | known affected: 344 known not affected: 385 recommended: 260 | 2026-10-16T14:09:27+00:00 | Vulnerability · Source |
| CVE-2022-50158 | suse_vex | SUSE CVE CVE-2022-50158 | known affected: 370 known not affected: 355 recommended: 273 | 2026-10-16T14:09:24+00:00 | Vulnerability · Source |
| CVE-2022-50160 | suse_vex | SUSE CVE CVE-2022-50160 | known affected: 463 known not affected: 278 recommended: 273 | 2026-10-16T14:09:21+00:00 | Vulnerability · Source |
| CVE-2022-50162 | suse_vex | SUSE CVE CVE-2022-50162 | known affected: 495 known not affected: 242 recommended: 310 | 2026-10-16T14:09:18+00:00 | Vulnerability · Source |
| CVE-2022-50165 | suse_vex | SUSE CVE CVE-2022-50165 | known affected: 465 known not affected: 273 recommended: 273 | 2026-10-16T14:09:16+00:00 | Vulnerability · Source |
| CVE-2022-50167 | suse_vex | SUSE CVE CVE-2022-50167 | known affected: 130 known not affected: 376 | 2026-10-16T14:09:14+00:00 | Vulnerability · Source |
| CVE-2022-50168 | suse_vex | SUSE CVE CVE-2022-50168 | known affected: 67 known not affected: 454 recommended: 54 | 2026-10-16T14:09:12+00:00 | Vulnerability · Source |
| CVE-2022-50169 | suse_vex | SUSE CVE CVE-2022-50169 | known affected: 491 known not affected: 251 recommended: 273 | 2026-10-16T14:09:10+00:00 | Vulnerability · Source |
| CVE-2022-50170 | suse_vex | SUSE CVE CVE-2022-50170 | known affected: 0 known not affected: 506 | 2026-10-16T14:09:08+00:00 | Vulnerability · Source |
| CVE-2022-50174 | suse_vex | SUSE CVE CVE-2022-50174 | known affected: 130 known not affected: 376 | 2026-10-16T14:09:07+00:00 | Vulnerability · Source |
| CVE-2022-50177 | suse_vex | SUSE CVE CVE-2022-50177 | known affected: 61 known not affected: 445 recommended: 20 | 2026-10-16T14:09:05+00:00 | Vulnerability · Source |
| CVE-2022-50178 | suse_vex | SUSE CVE CVE-2022-50178 | known affected: 344 known not affected: 387 recommended: 248 | 2026-10-16T14:09:03+00:00 | Vulnerability · Source |
| CVE-2022-50181 | suse_vex | SUSE CVE CVE-2022-50181 | known affected: 491 known not affected: 244 recommended: 384 | 2026-10-16T14:09:00+00:00 | Vulnerability · Source |
| CVE-2022-50182 | suse_vex | SUSE CVE CVE-2022-50182 | known affected: 61 known not affected: 445 | 2026-10-16T14:08:58+00:00 | Vulnerability · Source |
| CVE-2022-50184 | suse_vex | SUSE CVE CVE-2022-50184 | known affected: 430 known not affected: 381 recommended: 92 | 2026-10-16T14:08:55+00:00 | Vulnerability · Source |
| CVE-2022-50187 | suse_vex | SUSE CVE CVE-2022-50187 | known affected: 344 known not affected: 387 recommended: 248 | 2026-10-16T14:08:51+00:00 | Vulnerability · Source |
| CVE-2022-50188 | suse_vex | SUSE CVE CVE-2022-50188 | known affected: 369 known not affected: 441 recommended: 92 | 2026-10-16T14:08:49+00:00 | Vulnerability · Source |
| CVE-2022-50189 | suse_vex | SUSE CVE CVE-2022-50189 | known affected: 0 known not affected: 506 recommended: 74 | 2026-10-16T14:08:46+00:00 | Vulnerability · Source |
| CVE-2022-50190 | suse_vex | SUSE CVE CVE-2022-50190 | known affected: 344 known not affected: 387 recommended: 260 | 2026-10-16T14:08:43+00:00 | Vulnerability · Source |
| CVE-2022-50191 | suse_vex | SUSE CVE CVE-2022-50191 | known affected: 495 known not affected: 207 recommended: 354 | 2026-10-16T14:08:40+00:00 | Vulnerability · Source |
| CVE-2022-50192 | suse_vex | SUSE CVE CVE-2022-50192 | known affected: 344 known not affected: 385 recommended: 206 | 2026-10-16T14:08:37+00:00 | Vulnerability · Source |
| CVE-2022-50194 | suse_vex | SUSE CVE CVE-2022-50194 | known affected: 344 known not affected: 387 recommended: 260 | 2026-10-16T14:08:34+00:00 | Vulnerability · Source |
| CVE-2022-50195 | suse_vex | SUSE CVE CVE-2022-50195 | known affected: 61 known not affected: 445 | 2026-10-16T14:08:32+00:00 | Vulnerability · Source |
| CVE-2022-50199 | suse_vex | SUSE CVE CVE-2022-50199 | known affected: 413 known not affected: 316 recommended: 206 | 2026-10-16T14:08:28+00:00 | Vulnerability · Source |
| CVE-2022-50200 | suse_vex | SUSE CVE CVE-2022-50200 | known affected: 491 known not affected: 130 recommended: 394 | 2026-10-16T14:08:26+00:00 | Vulnerability · Source |
| CVE-2022-50201 | suse_vex | SUSE CVE CVE-2022-50201 | known affected: 344 known not affected: 385 recommended: 264 | 2026-10-16T14:08:23+00:00 | Vulnerability · Source |
| CVE-2022-50203 | suse_vex | SUSE CVE CVE-2022-50203 | known affected: 348 known not affected: 396 recommended: 206 | 2026-10-16T14:08:18+00:00 | Vulnerability · Source |
| CVE-2022-50204 | suse_vex | SUSE CVE CVE-2022-50204 | known affected: 344 known not affected: 387 recommended: 206 | 2026-10-16T14:08:15+00:00 | Vulnerability · Source |
| CVE-2022-50209 | suse_vex | SUSE CVE CVE-2022-50209 | known affected: 370 known not affected: 355 recommended: 273 | 2026-10-16T14:08:12+00:00 | Vulnerability · Source |
| CVE-2022-50210 | suse_vex | SUSE CVE CVE-2022-50210 | known affected: 0 known not affected: 521 | 2026-10-16T14:08:09+00:00 | Vulnerability · Source |
| CVE-2022-50215 | suse_vex | SUSE CVE CVE-2022-50215 | known affected: 497 known not affected: 239 recommended: 364 | 2026-10-16T14:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50217 | suse_vex | SUSE CVE CVE-2022-50217 | known affected: 0 known not affected: 506 | 2026-10-16T14:08:05+00:00 | Vulnerability · Source |
| CVE-2022-50218 | suse_vex | SUSE CVE CVE-2022-50218 | known affected: 463 known not affected: 279 recommended: 273 | 2026-10-16T14:08:03+00:00 | Vulnerability · Source |
| CVE-2022-50219 | suse_vex | SUSE CVE CVE-2022-50219 | known affected: 104 known not affected: 402 recommended: 74 | 2026-10-16T14:08:00+00:00 | Vulnerability · Source |