VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291717 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50422 | suse_vex | SUSE CVE CVE-2022-50422 | known affected: 425 known not affected: 181 recommended: 310 | 2026-08-13T02:19:55+00:00 | Vulnerability · Source |
| CVE-2022-50438 | suse_vex | SUSE CVE CVE-2022-50438 | known affected: 92 known not affected: 324 | 2026-08-13T02:19:53+00:00 | Vulnerability · Source |
| CVE-2022-50465 | suse_vex | SUSE CVE CVE-2022-50465 | known affected: 344 known not affected: 304 recommended: 233 | 2026-08-13T02:19:50+00:00 | Vulnerability · Source |
| CVE-2022-50469 | suse_vex | SUSE CVE CVE-2022-50469 | known affected: 442 known not affected: 176 recommended: 206 | 2026-08-13T02:19:48+00:00 | Vulnerability · Source |
| CVE-2022-50470 | suse_vex | SUSE CVE CVE-2022-50470 | known affected: 435 known not affected: 183 recommended: 345 | 2026-08-13T02:19:47+00:00 | Vulnerability · Source |
| CVE-2022-50471 | suse_vex | SUSE CVE CVE-2022-50471 | known affected: 478 known not affected: 185 recommended: 196 | 2026-08-13T02:19:46+00:00 | Vulnerability · Source |
| CVE-2022-50473 | suse_vex | SUSE CVE CVE-2022-50473 | known affected: 106 known not affected: 310 recommended: 50 | 2026-08-13T02:19:44+00:00 | Vulnerability · Source |
| CVE-2022-50478 | suse_vex | SUSE CVE CVE-2022-50478 | known affected: 413 known not affected: 245 recommended: 196 | 2026-08-13T02:19:42+00:00 | Vulnerability · Source |
| CVE-2022-50482 | suse_vex | SUSE CVE CVE-2022-50482 | known affected: 466 known not affected: 160 recommended: 245 | 2026-08-13T02:19:41+00:00 | Vulnerability · Source |
| CVE-2022-50485 | suse_vex | SUSE CVE CVE-2022-50485 | known affected: 478 known not affected: 181 recommended: 282 | 2026-08-13T02:19:39+00:00 | Vulnerability · Source |
| CVE-2022-50494 | suse_vex | SUSE CVE CVE-2022-50494 | known affected: 429 known not affected: 194 recommended: 325 | 2026-08-13T02:19:37+00:00 | Vulnerability · Source |
| CVE-2022-50504 | suse_vex | SUSE CVE CVE-2022-50504 | known affected: 421 known not affected: 173 recommended: 323 | 2026-08-13T02:19:35+00:00 | Vulnerability · Source |
| CVE-2022-50506 | suse_vex | SUSE CVE CVE-2022-50506 | known not affected: 416 recommended: 27 | 2026-08-13T02:19:33+00:00 | Vulnerability · Source |
| CVE-2022-50516 | suse_vex | SUSE CVE CVE-2022-50516 | known affected: 440 known not affected: 187 recommended: 329 | 2026-08-13T02:19:31+00:00 | Vulnerability · Source |
| CVE-2022-50522 | suse_vex | SUSE CVE CVE-2022-50522 | known not affected: 416 | 2026-08-13T02:19:29+00:00 | Vulnerability · Source |
| CVE-2022-50524 | suse_vex | SUSE CVE CVE-2022-50524 | known affected: 374 known not affected: 359 recommended: 87 | 2026-08-13T02:19:27+00:00 | Vulnerability · Source |
| CVE-2022-50531 | suse_vex | SUSE CVE CVE-2022-50531 | known affected: 106 known not affected: 310 recommended: 47 | 2026-08-13T02:19:25+00:00 | Vulnerability · Source |
| CVE-2022-50541 | suse_vex | SUSE CVE CVE-2022-50541 | known affected: 354 known not affected: 304 recommended: 196 | 2026-08-13T02:19:20+00:00 | Vulnerability · Source |
| CVE-2022-50545 | suse_vex | SUSE CVE CVE-2022-50545 | known affected: 478 known not affected: 181 recommended: 233 | 2026-08-13T02:19:19+00:00 | Vulnerability · Source |
| CVE-2022-50549 | suse_vex | SUSE CVE CVE-2022-50549 | known affected: 435 known not affected: 183 recommended: 343 | 2026-08-13T02:19:18+00:00 | Vulnerability · Source |
| CVE-2022-50551 | suse_vex | SUSE CVE CVE-2022-50551 | known affected: 428 known not affected: 226 recommended: 219 | 2026-08-13T02:19:17+00:00 | Vulnerability · Source |
| CVE-2022-50557 | suse_vex | SUSE CVE CVE-2022-50557 | known not affected: 407 | 2026-08-13T02:19:15+00:00 | Vulnerability · Source |
| CVE-2022-50560 | suse_vex | SUSE CVE CVE-2022-50560 | known affected: 452 known not affected: 197 recommended: 196 | 2026-08-13T02:19:14+00:00 | Vulnerability · Source |
| CVE-2022-50566 | suse_vex | SUSE CVE CVE-2022-50566 | known affected: 478 known not affected: 165 recommended: 196 | 2026-08-13T02:19:12+00:00 | Vulnerability · Source |
| CVE-2022-50574 | suse_vex | SUSE CVE CVE-2022-50574 | known affected: 354 known not affected: 263 recommended: 259 | 2026-08-13T02:19:10+00:00 | Vulnerability · Source |
| CVE-2022-50575 | suse_vex | SUSE CVE CVE-2022-50575 | known affected: 358 known not affected: 291 recommended: 196 | 2026-08-13T02:19:09+00:00 | Vulnerability · Source |
| CVE-2022-50576 | suse_vex | SUSE CVE CVE-2022-50576 | known affected: 354 known not affected: 295 recommended: 196 | 2026-08-13T02:19:08+00:00 | Vulnerability · Source |
| CVE-2022-50625 | suse_vex | SUSE CVE CVE-2022-50625 | known affected: 478 known not affected: 184 recommended: 219 | 2026-08-13T02:19:04+00:00 | Vulnerability · Source |
| CVE-2022-50626 | suse_vex | SUSE CVE CVE-2022-50626 | known affected: 354 known not affected: 341 recommended: 245 | 2026-08-13T02:19:03+00:00 | Vulnerability · Source |
| CVE-2022-50633 | suse_vex | SUSE CVE CVE-2022-50633 | known affected: 354 known not affected: 296 recommended: 225 | 2026-08-13T02:19:01+00:00 | Vulnerability · Source |
| CVE-2022-50642 | suse_vex | SUSE CVE CVE-2022-50642 | known not affected: 408 recommended: 29 | 2026-08-13T02:18:59+00:00 | Vulnerability · Source |
| CVE-2022-50644 | suse_vex | SUSE CVE CVE-2022-50644 | known affected: 354 known not affected: 289 recommended: 200 | 2026-08-13T02:18:58+00:00 | Vulnerability · Source |
| CVE-2022-50646 | suse_vex | SUSE CVE CVE-2022-50646 | known affected: 385 known not affected: 228 recommended: 223 | 2026-08-13T02:18:56+00:00 | Vulnerability · Source |
| CVE-2022-50647 | suse_vex | SUSE CVE CVE-2022-50647 | known not affected: 408 | 2026-08-13T02:18:54+00:00 | Vulnerability · Source |
| CVE-2022-50649 | suse_vex | SUSE CVE CVE-2022-50649 | known affected: 368 known not affected: 317 recommended: 200 | 2026-08-13T02:18:52+00:00 | Vulnerability · Source |
| CVE-2022-50653 | suse_vex | SUSE CVE CVE-2022-50653 | known affected: 354 known not affected: 296 recommended: 196 | 2026-08-13T02:18:50+00:00 | Vulnerability · Source |
| CVE-2022-50660 | suse_vex | SUSE CVE CVE-2022-50660 | known affected: 506 known not affected: 184 recommended: 210 | 2026-08-13T02:18:47+00:00 | Vulnerability · Source |
| CVE-2022-50662 | suse_vex | SUSE CVE CVE-2022-50662 | known affected: 389 known not affected: 261 recommended: 196 | 2026-08-13T02:18:45+00:00 | Vulnerability · Source |
| CVE-2022-50664 | suse_vex | SUSE CVE CVE-2022-50664 | known affected: 360 known not affected: 314 recommended: 196 | 2026-08-13T02:18:43+00:00 | Vulnerability · Source |
| CVE-2022-50672 | suse_vex | SUSE CVE CVE-2022-50672 | known affected: 403 known not affected: 247 recommended: 196 | 2026-08-13T02:18:41+00:00 | Vulnerability · Source |
| CVE-2022-50678 | suse_vex | SUSE CVE CVE-2022-50678 | known affected: 371 known not affected: 282 recommended: 270 | 2026-08-13T02:18:39+00:00 | Vulnerability · Source |
| CVE-2022-50679 | suse_vex | SUSE CVE CVE-2022-50679 | known affected: 389 known not affected: 261 recommended: 223 | 2026-08-13T02:18:37+00:00 | Vulnerability · Source |
| CVE-2022-50702 | suse_vex | SUSE CVE CVE-2022-50702 | known affected: 354 known not affected: 341 recommended: 223 | 2026-08-13T02:18:35+00:00 | Vulnerability · Source |
| CVE-2022-50710 | suse_vex | SUSE CVE CVE-2022-50710 | known affected: 374 known not affected: 396 recommended: 136 | 2026-08-13T02:18:34+00:00 | Vulnerability · Source |
| CVE-2022-50714 | suse_vex | SUSE CVE CVE-2022-50714 | known affected: 384 known not affected: 386 recommended: 134 | 2026-08-13T02:18:32+00:00 | Vulnerability · Source |
| CVE-2022-50721 | suse_vex | SUSE CVE CVE-2022-50721 | known not affected: 453 recommended: 29 | 2026-08-13T02:18:31+00:00 | Vulnerability · Source |
| CVE-2022-50741 | suse_vex | SUSE CVE CVE-2022-50741 | known affected: 112 known not affected: 341 | 2026-08-13T02:18:27+00:00 | Vulnerability · Source |
| CVE-2022-50751 | suse_vex | SUSE CVE CVE-2022-50751 | known affected: 476 known not affected: 187 recommended: 233 | 2026-08-13T02:18:26+00:00 | Vulnerability · Source |
| CVE-2022-50776 | suse_vex | SUSE CVE CVE-2022-50776 | known affected: 354 known not affected: 336 recommended: 196 | 2026-08-13T02:18:23+00:00 | Vulnerability · Source |
| CVE-2022-50777 | suse_vex | SUSE CVE CVE-2022-50777 | known affected: 440 known not affected: 193 recommended: 248 | 2026-08-13T02:18:22+00:00 | Vulnerability · Source |