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-50407 | suse_vex | SUSE CVE CVE-2022-50407 | known affected: 0 known not affected: 520 | 2026-10-16T14:05:56+00:00 | Vulnerability · Source |
| CVE-2022-50410 | suse_vex | SUSE CVE CVE-2022-50410 | known affected: 0 known not affected: 287 recommended: 359 | 2026-10-16T14:05:54+00:00 | Vulnerability · Source |
| CVE-2022-50411 | suse_vex | SUSE CVE CVE-2022-50411 | known affected: 540 known not affected: 173 recommended: 243 | 2026-10-16T14:05:52+00:00 | Vulnerability · Source |
| CVE-2022-50412 | suse_vex | SUSE CVE CVE-2022-50412 | known affected: 493 known not affected: 232 recommended: 237 | 2026-10-16T14:05:50+00:00 | Vulnerability · Source |
| CVE-2022-50419 | suse_vex | SUSE CVE CVE-2022-50419 | known affected: 491 known not affected: 173 recommended: 310 | 2026-10-16T14:05:48+00:00 | Vulnerability · Source |
| CVE-2022-50421 | suse_vex | SUSE CVE CVE-2022-50421 | known affected: 0 known not affected: 520 recommended: 86 | 2026-10-16T14:05:46+00:00 | Vulnerability · Source |
| CVE-2022-50422 | suse_vex | SUSE CVE CVE-2022-50422 | known affected: 497 known not affected: 167 recommended: 310 | 2026-10-16T14:05:44+00:00 | Vulnerability · Source |
| CVE-2022-50423 | suse_vex | SUSE CVE CVE-2022-50423 | known affected: 491 known not affected: 173 recommended: 376 | 2026-10-16T14:05:42+00:00 | Vulnerability · Source |
| CVE-2022-50427 | suse_vex | SUSE CVE CVE-2022-50427 | known affected: 497 known not affected: 136 recommended: 320 | 2026-10-16T14:05:40+00:00 | Vulnerability · Source |
| CVE-2022-50431 | suse_vex | SUSE CVE CVE-2022-50431 | known affected: 465 known not affected: 228 recommended: 320 | 2026-10-16T14:05:38+00:00 | Vulnerability · Source |
| CVE-2022-50432 | suse_vex | SUSE CVE CVE-2022-50432 | known affected: 492 known not affected: 173 recommended: 330 | 2026-10-16T14:05:37+00:00 | Vulnerability · Source |
| CVE-2022-50434 | suse_vex | SUSE CVE CVE-2022-50434 | known affected: 534 known not affected: 142 recommended: 229 | 2026-10-16T14:05:35+00:00 | Vulnerability · Source |
| CVE-2022-50436 | suse_vex | SUSE CVE CVE-2022-50436 | known affected: 344 known not affected: 392 recommended: 260 | 2026-10-16T14:05:33+00:00 | Vulnerability · Source |
| CVE-2022-50437 | suse_vex | SUSE CVE CVE-2022-50437 | known affected: 344 known not affected: 349 recommended: 273 | 2026-10-16T14:05:31+00:00 | Vulnerability · Source |
| CVE-2022-50440 | suse_vex | SUSE CVE CVE-2022-50440 | known affected: 6 known not affected: 281 recommended: 321 | 2026-10-16T14:05:29+00:00 | Vulnerability · Source |
| CVE-2022-50441 | suse_vex | SUSE CVE CVE-2022-50441 | known affected: 369 known not affected: 453 recommended: 92 | 2026-10-16T14:05:28+00:00 | Vulnerability · Source |
| CVE-2022-50443 | suse_vex | SUSE CVE CVE-2022-50443 | known affected: 506 known not affected: 172 recommended: 229 | 2026-10-16T14:05:26+00:00 | Vulnerability · Source |
| CVE-2022-50448 | suse_vex | SUSE CVE CVE-2022-50448 | known affected: 0 known not affected: 520 | 2026-10-16T14:05:24+00:00 | Vulnerability · Source |
| CVE-2022-50449 | suse_vex | SUSE CVE CVE-2022-50449 | known affected: 534 known not affected: 142 recommended: 206 | 2026-10-16T14:05:22+00:00 | Vulnerability · Source |
| CVE-2022-50452 | suse_vex | SUSE CVE CVE-2022-50452 | known affected: 499 known not affected: 323 recommended: 166 | 2026-10-16T14:05:20+00:00 | Vulnerability · Source |
| CVE-2022-50453 | suse_vex | SUSE CVE CVE-2022-50453 | known affected: 512 known not affected: 203 recommended: 287 | 2026-10-16T14:05:17+00:00 | Vulnerability · Source |
| CVE-2022-50455 | suse_vex | SUSE CVE CVE-2022-50455 | No product status | 2026-10-16T14:05:15+00:00 | Vulnerability · Source |
| CVE-2022-50457 | suse_vex | SUSE CVE CVE-2022-50457 | known affected: 0 known not affected: 520 | 2026-10-16T14:05:13+00:00 | Vulnerability · Source |
| CVE-2022-50458 | suse_vex | SUSE CVE CVE-2022-50458 | known affected: 463 known not affected: 172 recommended: 302 | 2026-10-16T14:05:10+00:00 | Vulnerability · Source |
| CVE-2022-50462 | suse_vex | SUSE CVE CVE-2022-50462 | known affected: 0 known not affected: 520 | 2026-10-16T14:05:08+00:00 | Vulnerability · Source |
| CVE-2022-50463 | suse_vex | SUSE CVE CVE-2022-50463 | known affected: 0 known not affected: 520 | 2026-10-16T14:05:05+00:00 | Vulnerability · Source |
| CVE-2022-50464 | suse_vex | SUSE CVE CVE-2022-50464 | known affected: 430 known not affected: 392 recommended: 170 | 2026-10-16T14:05:04+00:00 | Vulnerability · Source |
| CVE-2022-50465 | suse_vex | SUSE CVE CVE-2022-50465 | known affected: 344 known not affected: 392 recommended: 233 | 2026-10-16T14:05:02+00:00 | Vulnerability · Source |
| CVE-2022-50468 | suse_vex | SUSE CVE CVE-2022-50468 | known affected: 344 known not affected: 392 recommended: 206 | 2026-10-16T14:05:00+00:00 | Vulnerability · Source |
| CVE-2022-50472 | suse_vex | SUSE CVE CVE-2022-50472 | known affected: 423 known not affected: 323 recommended: 274 | 2026-10-16T14:04:57+00:00 | Vulnerability · Source |
| CVE-2022-50475 | suse_vex | SUSE CVE CVE-2022-50475 | known affected: 354 known not affected: 392 recommended: 274 | 2026-10-16T14:04:55+00:00 | Vulnerability · Source |
| CVE-2022-50478 | suse_vex | SUSE CVE CVE-2022-50478 | known affected: 435 known not affected: 311 recommended: 196 | 2026-10-16T14:04:52+00:00 | Vulnerability · Source |
| CVE-2022-50481 | suse_vex | SUSE CVE CVE-2022-50481 | known affected: 712 known not affected: 144 recommended: 23 | 2026-10-16T14:04:49+00:00 | Vulnerability · Source |
| CVE-2022-50484 | suse_vex | SUSE CVE CVE-2022-50484 | known affected: 354 known not affected: 352 recommended: 333 | 2026-10-16T14:04:47+00:00 | Vulnerability · Source |
| CVE-2022-50486 | suse_vex | SUSE CVE CVE-2022-50486 | known affected: 0 known not affected: 520 | 2026-10-16T14:04:45+00:00 | Vulnerability · Source |
| CVE-2022-50488 | suse_vex | SUSE CVE CVE-2022-50488 | known affected: 357 known not affected: 349 recommended: 317 | 2026-10-16T14:04:43+00:00 | Vulnerability · Source |
| CVE-2022-50489 | suse_vex | SUSE CVE CVE-2022-50489 | known affected: 501 known not affected: 144 recommended: 337 | 2026-10-16T14:04:41+00:00 | Vulnerability · Source |
| CVE-2022-50490 | suse_vex | SUSE CVE CVE-2022-50490 | known affected: 354 known not affected: 392 recommended: 219 | 2026-10-16T14:04:38+00:00 | Vulnerability · Source |
| CVE-2022-50492 | suse_vex | SUSE CVE CVE-2022-50492 | known affected: 544 known not affected: 144 recommended: 196 | 2026-10-16T14:04:36+00:00 | Vulnerability · Source |
| CVE-2022-50493 | suse_vex | SUSE CVE CVE-2022-50493 | known affected: 473 known not affected: 175 recommended: 302 | 2026-10-16T14:04:34+00:00 | Vulnerability · Source |
| CVE-2022-50497 | suse_vex | SUSE CVE CVE-2022-50497 | known affected: 544 known not affected: 142 recommended: 196 | 2026-10-16T14:04:29+00:00 | Vulnerability · Source |
| CVE-2022-50513 | suse_vex | SUSE CVE CVE-2022-50513 | known affected: 380 known not affected: 326 recommended: 259 | 2026-10-16T14:04:27+00:00 | Vulnerability · Source |
| CVE-2022-50515 | suse_vex | SUSE CVE CVE-2022-50515 | known affected: 374 known not affected: 453 recommended: 165 | 2026-10-16T14:04:25+00:00 | Vulnerability · Source |
| CVE-2022-50522 | suse_vex | SUSE CVE CVE-2022-50522 | known affected: 0 known not affected: 520 | 2026-10-16T14:04:22+00:00 | Vulnerability · Source |
| CVE-2022-50528 | suse_vex | SUSE CVE CVE-2022-50528 | known affected: 354 known not affected: 392 recommended: 274 | 2026-10-16T14:04:20+00:00 | Vulnerability · Source |
| CVE-2022-50533 | suse_vex | SUSE CVE CVE-2022-50533 | known affected: 0 known not affected: 520 | 2026-10-16T14:04:17+00:00 | Vulnerability · Source |
| CVE-2022-50538 | suse_vex | SUSE CVE CVE-2022-50538 | known affected: 8 known not affected: 514 | 2026-10-16T14:04:15+00:00 | Vulnerability · Source |
| CVE-2022-50544 | suse_vex | SUSE CVE CVE-2022-50544 | known affected: 507 known not affected: 169 recommended: 374 | 2026-10-16T14:04:13+00:00 | Vulnerability · Source |
| CVE-2022-50546 | suse_vex | SUSE CVE CVE-2022-50546 | known affected: 354 known not affected: 352 recommended: 333 | 2026-10-16T14:04:10+00:00 | Vulnerability · Source |
| CVE-2022-50559 | suse_vex | SUSE CVE CVE-2022-50559 | known affected: 354 known not affected: 383 recommended: 196 | 2026-10-16T14:04:09+00:00 | Vulnerability · Source |