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-50223 | suse_vex | SUSE CVE CVE-2022-50223 | known affected: 0 known not affected: 506 | 2026-10-16T14:07:58+00:00 | Vulnerability · Source |
| CVE-2022-50224 | suse_vex | SUSE CVE CVE-2022-50224 | known affected: 324 known not affected: 122 recommended: 27 | 2026-10-16T14:07:55+00:00 | Vulnerability · Source |
| CVE-2022-50227 | suse_vex | SUSE CVE CVE-2022-50227 | known affected: 0 known not affected: 506 recommended: 54 | 2026-10-16T14:07:50+00:00 | Vulnerability · Source |
| CVE-2022-50228 | suse_vex | SUSE CVE CVE-2022-50228 | known affected: 550 known not affected: 191 recommended: 317 | 2026-10-16T14:07:48+00:00 | Vulnerability · Source |
| CVE-2022-50233 | suse_vex | SUSE CVE CVE-2022-50233 | known affected: 377 known not affected: 226 recommended: 329 | 2026-10-16T14:07:45+00:00 | Vulnerability · Source |
| CVE-2022-50241 | suse_vex | SUSE CVE CVE-2022-50241 | known affected: 348 known not affected: 566 recommended: 260 | 2026-10-16T14:07:42+00:00 | Vulnerability · Source |
| CVE-2022-50243 | suse_vex | SUSE CVE CVE-2022-50243 | known affected: 128 known not affected: 392 recommended: 74 | 2026-10-16T14:07:39+00:00 | Vulnerability · Source |
| CVE-2022-50245 | suse_vex | SUSE CVE CVE-2022-50245 | known affected: 8 known not affected: 512 | 2026-10-16T14:07:37+00:00 | Vulnerability · Source |
| CVE-2022-50247 | suse_vex | SUSE CVE CVE-2022-50247 | known affected: 344 known not affected: 392 recommended: 255 | 2026-10-16T14:07:34+00:00 | Vulnerability · Source |
| CVE-2022-50252 | suse_vex | SUSE CVE CVE-2022-50252 | known affected: 465 known not affected: 132 recommended: 385 | 2026-10-16T14:07:31+00:00 | Vulnerability · Source |
| CVE-2022-50255 | suse_vex | SUSE CVE CVE-2022-50255 | known affected: 344 known not affected: 392 recommended: 206 | 2026-10-16T14:07:25+00:00 | Vulnerability · Source |
| CVE-2022-50259 | suse_vex | SUSE CVE CVE-2022-50259 | known affected: 197 known not affected: 323 | 2026-10-16T14:07:24+00:00 | Vulnerability · Source |
| CVE-2022-50262 | suse_vex | SUSE CVE CVE-2022-50262 | known affected: 0 known not affected: 520 | 2026-10-16T14:07:22+00:00 | Vulnerability · Source |
| CVE-2022-50269 | suse_vex | SUSE CVE CVE-2022-50269 | known affected: 344 known not affected: 392 recommended: 284 | 2026-10-16T14:07:19+00:00 | Vulnerability · Source |
| CVE-2022-50273 | suse_vex | SUSE CVE CVE-2022-50273 | known affected: 203 known not affected: 356 | 2026-10-16T14:07:17+00:00 | Vulnerability · Source |
| CVE-2022-50275 | suse_vex | SUSE CVE CVE-2022-50275 | known affected: 540 known not affected: 136 recommended: 284 | 2026-10-16T14:07:14+00:00 | Vulnerability · Source |
| CVE-2022-50282 | suse_vex | SUSE CVE CVE-2022-50282 | known affected: 505 known not affected: 203 recommended: 233 | 2026-10-16T14:07:12+00:00 | Vulnerability · Source |
| CVE-2022-50284 | suse_vex | SUSE CVE CVE-2022-50284 | known affected: 0 known not affected: 520 | 2026-10-16T14:07:09+00:00 | Vulnerability · Source |
| CVE-2022-50294 | suse_vex | SUSE CVE CVE-2022-50294 | known affected: 546 known not affected: 167 recommended: 243 | 2026-10-16T14:07:07+00:00 | Vulnerability · Source |
| CVE-2022-50295 | suse_vex | SUSE CVE CVE-2022-50295 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-16T14:07:05+00:00 | Vulnerability · Source |
| CVE-2022-50296 | suse_vex | SUSE CVE CVE-2022-50296 | known affected: 10 known not affected: 510 | 2026-10-16T14:07:02+00:00 | Vulnerability · Source |
| CVE-2022-50298 | suse_vex | SUSE CVE CVE-2022-50298 | known affected: 344 known not affected: 392 recommended: 206 | 2026-10-16T14:07:00+00:00 | Vulnerability · Source |
| CVE-2022-50303 | suse_vex | SUSE CVE CVE-2022-50303 | known affected: 686 known not affected: 178 recommended: 170 | 2026-10-16T14:06:57+00:00 | Vulnerability · Source |
| CVE-2022-50304 | suse_vex | SUSE CVE CVE-2022-50304 | known affected: 684 known not affected: 172 recommended: 23 | 2026-10-16T14:06:55+00:00 | Vulnerability · Source |
| CVE-2022-50305 | suse_vex | SUSE CVE CVE-2022-50305 | known affected: 0 known not affected: 520 | 2026-10-16T14:06:52+00:00 | Vulnerability · Source |
| CVE-2022-50307 | suse_vex | SUSE CVE CVE-2022-50307 | known affected: 0 known not affected: 520 | 2026-10-16T14:06:49+00:00 | Vulnerability · Source |
| CVE-2022-50313 | suse_vex | SUSE CVE CVE-2022-50313 | known affected: 130 known not affected: 390 recommended: 58 | 2026-10-16T14:06:47+00:00 | Vulnerability · Source |
| CVE-2022-50315 | suse_vex | SUSE CVE CVE-2022-50315 | known affected: 390 known not affected: 172 | 2026-10-16T14:06:44+00:00 | Vulnerability · Source |
| CVE-2022-50322 | suse_vex | SUSE CVE CVE-2022-50322 | known affected: 0 known not affected: 520 recommended: 29 | 2026-10-16T14:06:42+00:00 | Vulnerability · Source |
| CVE-2022-50324 | suse_vex | SUSE CVE CVE-2022-50324 | known affected: 465 known not affected: 271 recommended: 206 | 2026-10-16T14:06:39+00:00 | Vulnerability · Source |
| CVE-2022-50328 | suse_vex | SUSE CVE CVE-2022-50328 | known affected: 344 known not affected: 392 recommended: 206 | 2026-10-16T14:06:37+00:00 | Vulnerability · Source |
| CVE-2022-50329 | suse_vex | SUSE CVE CVE-2022-50329 | known affected: 344 known not affected: 386 recommended: 239 | 2026-10-16T14:06:35+00:00 | Vulnerability · Source |
| CVE-2022-50332 | suse_vex | SUSE CVE CVE-2022-50332 | known affected: 0 known not affected: 520 | 2026-10-16T14:06:33+00:00 | Vulnerability · Source |
| CVE-2022-50338 | suse_vex | SUSE CVE CVE-2022-50338 | known affected: 130 known not affected: 390 | 2026-10-16T14:06:31+00:00 | Vulnerability · Source |
| CVE-2022-50343 | suse_vex | SUSE CVE CVE-2022-50343 | known affected: 8 known not affected: 512 | 2026-10-16T14:06:28+00:00 | Vulnerability · Source |
| CVE-2022-50348 | suse_vex | SUSE CVE CVE-2022-50348 | known affected: 344 known not affected: 392 recommended: 280 | 2026-10-16T14:06:25+00:00 | Vulnerability · Source |
| CVE-2022-50350 | suse_vex | SUSE CVE CVE-2022-50350 | known affected: 724 known not affected: 167 recommended: 111 | 2026-10-16T14:06:23+00:00 | Vulnerability · Source |
| CVE-2022-50355 | suse_vex | SUSE CVE CVE-2022-50355 | known affected: 370 known not affected: 323 recommended: 273 | 2026-10-16T14:06:20+00:00 | Vulnerability · Source |
| CVE-2022-50361 | suse_vex | SUSE CVE CVE-2022-50361 | known affected: 0 known not affected: 520 recommended: 58 | 2026-10-16T14:06:18+00:00 | Vulnerability · Source |
| CVE-2022-50363 | suse_vex | SUSE CVE CVE-2022-50363 | known affected: 0 known not affected: 520 recommended: 54 | 2026-10-16T14:06:16+00:00 | Vulnerability · Source |
| CVE-2022-50365 | suse_vex | SUSE CVE CVE-2022-50365 | known affected: 617 known not affected: 239 recommended: 43 | 2026-10-16T14:06:15+00:00 | Vulnerability · Source |
| CVE-2022-50368 | suse_vex | SUSE CVE CVE-2022-50368 | known affected: 491 known not affected: 142 recommended: 296 | 2026-10-16T14:06:13+00:00 | Vulnerability · Source |
| CVE-2022-50378 | suse_vex | SUSE CVE CVE-2022-50378 | known affected: 505 known not affected: 356 recommended: 92 | 2026-10-16T14:06:10+00:00 | Vulnerability · Source |
| CVE-2022-50380 | suse_vex | SUSE CVE CVE-2022-50380 | known affected: 0 known not affected: 520 | 2026-10-16T14:06:08+00:00 | Vulnerability · Source |
| CVE-2022-50383 | suse_vex | SUSE CVE CVE-2022-50383 | known affected: 0 known not affected: 520 | 2026-10-16T14:06:06+00:00 | Vulnerability · Source |
| CVE-2022-50390 | suse_vex | SUSE CVE CVE-2022-50390 | known affected: 430 known not affected: 392 recommended: 141 | 2026-10-16T14:06:04+00:00 | Vulnerability · Source |
| CVE-2022-50391 | suse_vex | SUSE CVE CVE-2022-50391 | known affected: 344 known not affected: 392 recommended: 264 | 2026-10-16T14:06:02+00:00 | Vulnerability · Source |
| CVE-2022-50394 | suse_vex | SUSE CVE CVE-2022-50394 | known affected: 546 known not affected: 167 recommended: 243 | 2026-10-16T14:06:01+00:00 | Vulnerability · Source |
| CVE-2022-50395 | suse_vex | SUSE CVE CVE-2022-50395 | known affected: 506 known not affected: 172 recommended: 229 | 2026-10-16T14:05:59+00:00 | Vulnerability · Source |
| CVE-2022-50400 | suse_vex | SUSE CVE CVE-2022-50400 | known affected: 128 known not affected: 392 | 2026-10-16T14:05:57+00:00 | Vulnerability · Source |