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-49995 | suse_vex | SUSE CVE CVE-2022-49995 | known affected: 344 known not affected: 386 recommended: 280 | 2026-10-16T14:12:14+00:00 | Vulnerability · Source |
| CVE-2022-49998 | suse_vex | SUSE CVE CVE-2022-49998 | known affected: 130 known not affected: 376 recommended: 54 | 2026-10-16T14:12:12+00:00 | Vulnerability · Source |
| CVE-2022-50000 | suse_vex | SUSE CVE CVE-2022-50000 | known affected: 104 known not affected: 402 recommended: 42 | 2026-10-16T14:12:09+00:00 | Vulnerability · Source |
| CVE-2022-50001 | suse_vex | SUSE CVE CVE-2022-50001 | known affected: 130 known not affected: 376 recommended: 42 | 2026-10-16T14:12:06+00:00 | Vulnerability · Source |
| CVE-2022-50002 | suse_vex | SUSE CVE CVE-2022-50002 | known affected: 430 known not affected: 381 recommended: 166 | 2026-10-16T14:12:04+00:00 | Vulnerability · Source |
| CVE-2022-50005 | suse_vex | SUSE CVE CVE-2022-50005 | known affected: 344 known not affected: 385 recommended: 264 | 2026-10-16T14:12:01+00:00 | Vulnerability · Source |
| CVE-2022-50008 | suse_vex | SUSE CVE CVE-2022-50008 | known affected: 534 known not affected: 154 recommended: 243 | 2026-10-16T14:11:59+00:00 | Vulnerability · Source |
| CVE-2022-50014 | suse_vex | SUSE CVE CVE-2022-50014 | known affected: 0 known not affected: 506 recommended: 54 | 2026-10-16T14:11:56+00:00 | Vulnerability · Source |
| CVE-2022-50015 | suse_vex | SUSE CVE CVE-2022-50015 | known affected: 499 known not affected: 311 recommended: 166 | 2026-10-16T14:11:54+00:00 | Vulnerability · Source |
| CVE-2022-50018 | suse_vex | SUSE CVE CVE-2022-50018 | No product status | 2026-10-16T14:11:51+00:00 | Vulnerability · Source |
| CVE-2022-50022 | suse_vex | SUSE CVE CVE-2022-50022 | known affected: 491 known not affected: 244 recommended: 397 | 2026-10-16T14:11:49+00:00 | Vulnerability · Source |
| CVE-2022-50023 | suse_vex | SUSE CVE CVE-2022-50023 | known affected: 413 known not affected: 317 recommended: 206 | 2026-10-16T14:11:46+00:00 | Vulnerability · Source |
| CVE-2022-50025 | suse_vex | SUSE CVE CVE-2022-50025 | known affected: 702 known not affected: 156 recommended: 23 | 2026-10-16T14:11:44+00:00 | Vulnerability · Source |
| CVE-2022-50027 | suse_vex | SUSE CVE CVE-2022-50027 | known affected: 371 known not affected: 312 recommended: 338 | 2026-10-16T14:11:42+00:00 | Vulnerability · Source |
| CVE-2022-50028 | suse_vex | SUSE CVE CVE-2022-50028 | known affected: 497 known not affected: 245 recommended: 327 | 2026-10-16T14:11:39+00:00 | Vulnerability · Source |
| CVE-2022-50029 | suse_vex | SUSE CVE CVE-2022-50029 | known affected: 370 known not affected: 357 recommended: 327 | 2026-10-16T14:11:36+00:00 | Vulnerability · Source |
| CVE-2022-50030 | suse_vex | SUSE CVE CVE-2022-50030 | known affected: 467 known not affected: 217 recommended: 352 | 2026-10-16T14:11:34+00:00 | Vulnerability · Source |
| CVE-2022-50032 | suse_vex | SUSE CVE CVE-2022-50032 | known affected: 344 known not affected: 383 recommended: 327 | 2026-10-16T14:11:32+00:00 | Vulnerability · Source |
| CVE-2022-50035 | suse_vex | SUSE CVE CVE-2022-50035 | known affected: 369 known not affected: 441 recommended: 166 | 2026-10-16T14:11:30+00:00 | Vulnerability · Source |
| CVE-2022-50039 | suse_vex | SUSE CVE CVE-2022-50039 | known affected: 344 known not affected: 385 recommended: 280 | 2026-10-16T14:11:25+00:00 | Vulnerability · Source |
| CVE-2022-50040 | suse_vex | SUSE CVE CVE-2022-50040 | known affected: 344 known not affected: 387 recommended: 206 | 2026-10-16T14:11:23+00:00 | Vulnerability · Source |
| CVE-2022-50041 | suse_vex | SUSE CVE CVE-2022-50041 | known affected: 373 known not affected: 453 recommended: 166 | 2026-10-16T14:11:21+00:00 | Vulnerability · Source |
| CVE-2022-50042 | suse_vex | SUSE CVE CVE-2022-50042 | known affected: 61 known not affected: 445 recommended: 78 | 2026-10-16T14:11:19+00:00 | Vulnerability · Source |
| CVE-2022-50047 | suse_vex | SUSE CVE CVE-2022-50047 | known affected: 413 known not affected: 316 recommended: 206 | 2026-10-16T14:11:16+00:00 | Vulnerability · Source |
| CVE-2022-50049 | suse_vex | SUSE CVE CVE-2022-50049 | known affected: 369 known not affected: 442 recommended: 166 | 2026-10-16T14:11:14+00:00 | Vulnerability · Source |
| CVE-2022-50051 | suse_vex | SUSE CVE CVE-2022-50051 | known affected: 344 known not affected: 383 recommended: 327 | 2026-10-16T14:11:12+00:00 | Vulnerability · Source |
| CVE-2022-50055 | suse_vex | SUSE CVE CVE-2022-50055 | known affected: 544 known not affected: 146 recommended: 317 | 2026-10-16T14:11:09+00:00 | Vulnerability · Source |
| CVE-2022-50059 | suse_vex | SUSE CVE CVE-2022-50059 | known affected: 370 known not affected: 357 recommended: 273 | 2026-10-16T14:11:07+00:00 | Vulnerability · Source |
| CVE-2022-50061 | suse_vex | SUSE CVE CVE-2022-50061 | known affected: 344 known not affected: 398 recommended: 273 | 2026-10-16T14:11:02+00:00 | Vulnerability · Source |
| CVE-2022-50064 | suse_vex | SUSE CVE CVE-2022-50064 | known affected: 0 known not affected: 521 recommended: 29 | 2026-10-16T14:11:00+00:00 | Vulnerability · Source |
| CVE-2022-50065 | suse_vex | SUSE CVE CVE-2022-50065 | known affected: 403 known not affected: 270 recommended: 296 | 2026-10-16T14:10:59+00:00 | Vulnerability · Source |
| CVE-2022-50078 | suse_vex | SUSE CVE CVE-2022-50078 | known affected: 0 known not affected: 506 | 2026-10-16T14:10:54+00:00 | Vulnerability · Source |
| CVE-2022-50079 | suse_vex | SUSE CVE CVE-2022-50079 | known affected: 344 known not affected: 385 recommended: 280 | 2026-10-16T14:10:51+00:00 | Vulnerability · Source |
| CVE-2022-50082 | suse_vex | SUSE CVE CVE-2022-50082 | known affected: 733 known not affected: 122 | 2026-10-16T14:10:49+00:00 | Vulnerability · Source |
| CVE-2022-50084 | suse_vex | SUSE CVE CVE-2022-50084 | known affected: 463 known not affected: 221 recommended: 352 | 2026-10-16T14:10:47+00:00 | Vulnerability · Source |
| CVE-2022-50088 | suse_vex | SUSE CVE CVE-2022-50088 | known affected: 0 known not affected: 506 recommended: 54 | 2026-10-16T14:10:44+00:00 | Vulnerability · Source |
| CVE-2022-50089 | suse_vex | SUSE CVE CVE-2022-50089 | known affected: 61 known not affected: 445 | 2026-10-16T14:10:42+00:00 | Vulnerability · Source |
| CVE-2022-50090 | suse_vex | SUSE CVE CVE-2022-50090 | known affected: 61 known not affected: 445 | 2026-10-16T14:10:40+00:00 | Vulnerability · Source |
| CVE-2022-50093 | suse_vex | SUSE CVE CVE-2022-50093 | known affected: 497 known not affected: 240 recommended: 384 | 2026-10-16T14:10:38+00:00 | Vulnerability · Source |
| CVE-2022-50096 | suse_vex | SUSE CVE CVE-2022-50096 | known affected: 61 known not affected: 445 | 2026-10-16T14:10:36+00:00 | Vulnerability · Source |
| CVE-2022-50098 | suse_vex | SUSE CVE CVE-2022-50098 | known affected: 463 known not affected: 221 recommended: 296 | 2026-10-16T14:10:31+00:00 | Vulnerability · Source |
| CVE-2022-50100 | suse_vex | SUSE CVE CVE-2022-50100 | known affected: 344 known not affected: 385 recommended: 280 | 2026-10-16T14:10:28+00:00 | Vulnerability · Source |
| CVE-2022-50103 | suse_vex | SUSE CVE CVE-2022-50103 | known affected: 558 known not affected: 131 recommended: 243 | 2026-10-16T14:10:26+00:00 | Vulnerability · Source |
| CVE-2022-50104 | suse_vex | SUSE CVE CVE-2022-50104 | known affected: 463 known not affected: 208 recommended: 296 | 2026-10-16T14:10:23+00:00 | Vulnerability · Source |
| CVE-2022-50107 | suse_vex | SUSE CVE CVE-2022-50107 | known affected: 67 known not affected: 454 recommended: 58 | 2026-10-16T14:10:21+00:00 | Vulnerability · Source |
| CVE-2022-50112 | suse_vex | SUSE CVE CVE-2022-50112 | known affected: 506 known not affected: 238 recommended: 292 | 2026-10-16T14:10:18+00:00 | Vulnerability · Source |
| CVE-2022-50114 | suse_vex | SUSE CVE CVE-2022-50114 | known affected: 130 known not affected: 376 | 2026-10-16T14:10:16+00:00 | Vulnerability · Source |
| CVE-2022-50116 | suse_vex | SUSE CVE CVE-2022-50116 | known affected: 344 known not affected: 291 recommended: 435 | 2026-10-16T14:10:13+00:00 | Vulnerability · Source |
| CVE-2022-50118 | suse_vex | SUSE CVE CVE-2022-50118 | known affected: 344 known not affected: 396 recommended: 273 | 2026-10-16T14:10:08+00:00 | Vulnerability · Source |
| CVE-2022-50123 | suse_vex | SUSE CVE CVE-2022-50123 | known affected: 121 known not affected: 398 recommended: 54 | 2026-10-16T14:10:06+00:00 | Vulnerability · Source |