VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50338 | suse_vex | SUSE CVE CVE-2022-50338 | known affected: 106 known not affected: 310 | 2026-07-25T17:07:20+00:00 | Vulnerability · Source |
| CVE-2022-50341 | suse_vex | SUSE CVE CVE-2022-50341 | known affected: 98 known not affected: 318 recommended: 62 | 2026-07-25T17:07:19+00:00 | Vulnerability · Source |
| CVE-2022-50371 | suse_vex | SUSE CVE CVE-2022-50371 | known not affected: 416 | 2026-07-25T17:07:11+00:00 | Vulnerability · Source |
| CVE-2022-50384 | suse_vex | SUSE CVE CVE-2022-50384 | known affected: 224 known not affected: 192 | 2026-07-25T17:07:08+00:00 | Vulnerability · Source |
| CVE-2022-50389 | suse_vex | SUSE CVE CVE-2022-50389 | known affected: 456 known not affected: 160 recommended: 278 | 2026-07-25T17:07:05+00:00 | Vulnerability · Source |
| CVE-2022-50403 | suse_vex | SUSE CVE CVE-2022-50403 | recommended: 60 | 2026-07-25T17:06:58+00:00 | Vulnerability · Source |
| CVE-2022-50415 | suse_vex | SUSE CVE CVE-2022-50415 | known not affected: 416 | 2026-07-25T17:06:52+00:00 | Vulnerability · Source |
| CVE-2022-50416 | suse_vex | SUSE CVE CVE-2022-50416 | known affected: 112 known not affected: 304 recommended: 29 | 2026-07-25T17:06:51+00:00 | Vulnerability · Source |
| CVE-2022-50420 | suse_vex | SUSE CVE CVE-2022-50420 | known affected: 149 known not affected: 267 | 2026-07-25T17:06:48+00:00 | Vulnerability · Source |
| CVE-2022-50421 | suse_vex | SUSE CVE CVE-2022-50421 | known not affected: 416 recommended: 43 | 2026-07-25T17:06:47+00:00 | Vulnerability · Source |
| CVE-2022-50445 | suse_vex | SUSE CVE CVE-2022-50445 | known affected: 210 known not affected: 176 | 2026-07-25T17:06:38+00:00 | Vulnerability · Source |
| CVE-2022-50446 | suse_vex | SUSE CVE CVE-2022-50446 | known not affected: 416 | 2026-07-25T17:06:37+00:00 | Vulnerability · Source |
| CVE-2022-50457 | suse_vex | SUSE CVE CVE-2022-50457 | known not affected: 416 | 2026-07-25T17:06:31+00:00 | Vulnerability · Source |
| CVE-2022-50477 | suse_vex | SUSE CVE CVE-2022-50477 | known not affected: 416 recommended: 29 | 2026-07-25T17:06:27+00:00 | Vulnerability · Source |
| CVE-2022-50498 | suse_vex | SUSE CVE CVE-2022-50498 | known affected: 354 known not affected: 304 recommended: 196 | 2026-07-25T17:06:21+00:00 | Vulnerability · Source |
| CVE-2022-50500 | suse_vex | SUSE CVE CVE-2022-50500 | known affected: 123 known not affected: 263 | 2026-07-25T17:06:19+00:00 | Vulnerability · Source |
| CVE-2022-50510 | suse_vex | SUSE CVE CVE-2022-50510 | known affected: 106 known not affected: 310 recommended: 49 | 2026-07-25T17:06:17+00:00 | Vulnerability · Source |
| CVE-2022-50550 | suse_vex | SUSE CVE CVE-2022-50550 | known affected: 106 known not affected: 310 recommended: 29 | 2026-07-25T17:06:10+00:00 | Vulnerability · Source |
| CVE-2022-50559 | suse_vex | SUSE CVE CVE-2022-50559 | known affected: 354 known not affected: 295 recommended: 196 | 2026-07-25T17:06:07+00:00 | Vulnerability · Source |
| CVE-2022-50569 | suse_vex | SUSE CVE CVE-2022-50569 | known affected: 630 known not affected: 161 recommended: 84 | 2026-07-25T17:06:00+00:00 | Vulnerability · Source |
| CVE-2022-50573 | suse_vex | SUSE CVE CVE-2022-50573 | known not affected: 407 | 2026-07-25T17:05:57+00:00 | Vulnerability · Source |
| CVE-2022-50583 | suse_vex | SUSE CVE CVE-2022-50583 | known affected: 244 known not affected: 206 recommended: 47 | 2026-07-25T17:05:52+00:00 | Vulnerability · Source |
| CVE-2022-50651 | suse_vex | SUSE CVE CVE-2022-50651 | known affected: 112 known not affected: 296 | 2026-07-25T17:05:42+00:00 | Vulnerability · Source |
| CVE-2022-50657 | suse_vex | SUSE CVE CVE-2022-50657 | known not affected: 408 | 2026-07-25T17:05:39+00:00 | Vulnerability · Source |
| CVE-2022-50658 | suse_vex | SUSE CVE CVE-2022-50658 | known affected: 354 known not affected: 296 recommended: 225 | 2026-07-25T17:05:37+00:00 | Vulnerability · Source |
| CVE-2022-50659 | suse_vex | SUSE CVE CVE-2022-50659 | known affected: 6 known not affected: 402 | 2026-07-25T17:05:36+00:00 | Vulnerability · Source |
| CVE-2022-50707 | suse_vex | SUSE CVE CVE-2022-50707 | known not affected: 453 | 2026-07-25T17:05:22+00:00 | Vulnerability · Source |
| CVE-2022-50708 | suse_vex | SUSE CVE CVE-2022-50708 | known affected: 67 known not affected: 386 | 2026-07-25T17:05:20+00:00 | Vulnerability · Source |
| CVE-2022-50725 | suse_vex | SUSE CVE CVE-2022-50725 | known not affected: 453 | 2026-07-25T17:05:17+00:00 | Vulnerability · Source |
| CVE-2022-50729 | suse_vex | SUSE CVE CVE-2022-50729 | known not affected: 453 | 2026-07-25T17:05:13+00:00 | Vulnerability · Source |
| CVE-2022-50734 | suse_vex | SUSE CVE CVE-2022-50734 | known affected: 112 known not affected: 341 | 2026-07-25T17:05:09+00:00 | Vulnerability · Source |
| CVE-2022-50737 | suse_vex | SUSE CVE CVE-2022-50737 | known not affected: 453 | 2026-07-25T17:05:08+00:00 | Vulnerability · Source |
| CVE-2022-50748 | suse_vex | SUSE CVE CVE-2022-50748 | known not affected: 448 | 2026-07-25T17:05:02+00:00 | Vulnerability · Source |
| CVE-2022-50753 | suse_vex | SUSE CVE CVE-2022-50753 | known affected: 61 known not affected: 392 | 2026-07-25T17:04:59+00:00 | Vulnerability · Source |
| CVE-2022-50765 | suse_vex | SUSE CVE CVE-2022-50765 | known not affected: 453 | 2026-07-25T17:04:55+00:00 | Vulnerability · Source |
| CVE-2022-50772 | suse_vex | SUSE CVE CVE-2022-50772 | known affected: 167 known not affected: 286 recommended: 29 | 2026-07-25T17:04:54+00:00 | Vulnerability · Source |
| CVE-2022-50780 | suse_vex | SUSE CVE CVE-2022-50780 | known affected: 394 known not affected: 411 recommended: 66 | 2026-07-25T17:04:47+00:00 | Vulnerability · Source |
| CVE-2022-50785 | suse_vex | SUSE CVE CVE-2022-50785 | known not affected: 453 | 2026-07-25T17:04:45+00:00 | Vulnerability · Source |
| CVE-2022-50786 | suse_vex | SUSE CVE CVE-2022-50786 | known affected: 622 known not affected: 193 recommended: 37 | 2026-07-25T17:04:44+00:00 | Vulnerability · Source |
| CVE-2022-50810 | suse_vex | SUSE CVE CVE-2022-50810 | known not affected: 453 | 2026-07-25T17:04:43+00:00 | Vulnerability · Source |
| CVE-2022-50812 | suse_vex | SUSE CVE CVE-2022-50812 | known not affected: 453 | 2026-07-25T17:04:41+00:00 | Vulnerability · Source |
| CVE-2022-50820 | suse_vex | SUSE CVE CVE-2022-50820 | known affected: 112 known not affected: 341 recommended: 29 | 2026-07-25T17:04:39+00:00 | Vulnerability · Source |
| CVE-2022-50841 | suse_vex | SUSE CVE CVE-2022-50841 | known not affected: 453 | 2026-07-25T17:04:27+00:00 | Vulnerability · Source |
| CVE-2022-50857 | suse_vex | SUSE CVE CVE-2022-50857 | known affected: 61 known not affected: 193 | 2026-07-25T17:04:21+00:00 | Vulnerability · Source |
| CVE-2022-50865 | suse_vex | SUSE CVE CVE-2022-50865 | known affected: 608 known not affected: 209 recommended: 72 | 2026-07-25T17:04:17+00:00 | Vulnerability · Source |
| CVE-2022-50879 | suse_vex | SUSE CVE CVE-2022-50879 | known not affected: 423 recommended: 52 | 2026-07-25T17:04:10+00:00 | Vulnerability · Source |
| CVE-2022-50888 | suse_vex | SUSE CVE CVE-2022-50888 | known affected: 354 known not affected: 341 recommended: 196 | 2026-07-25T17:04:07+00:00 | Vulnerability · Source |
| CVE-2023-0051 | suse_vex | SUSE CVE CVE-2023-0051 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:04+00:00 | Vulnerability · Source |
| CVE-2023-0054 | suse_vex | SUSE CVE CVE-2023-0054 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:02+00:00 | Vulnerability · Source |
| CVE-2023-0288 | suse_vex | SUSE CVE CVE-2023-0288 | known affected: 358 known not affected: 1 recommended: 322 | 2026-07-25T17:04:01+00:00 | Vulnerability · Source |