VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50236 | suse_vex | SUSE CVE CVE-2022-50236 | known affected: 604 known not affected: 176 recommended: 23 | 2026-07-25T17:08:08+00:00 | Vulnerability · Source |
| CVE-2022-50240 | suse_vex | SUSE CVE CVE-2022-50240 | known not affected: 416 | 2026-07-25T17:08:07+00:00 | Vulnerability · Source |
| CVE-2022-50243 | suse_vex | SUSE CVE CVE-2022-50243 | known affected: 112 known not affected: 304 recommended: 47 | 2026-07-25T17:08:05+00:00 | Vulnerability · Source |
| CVE-2022-50244 | suse_vex | SUSE CVE CVE-2022-50244 | known affected: 604 known not affected: 176 recommended: 23 | 2026-07-25T17:08:04+00:00 | Vulnerability · Source |
| CVE-2022-50254 | suse_vex | SUSE CVE CVE-2022-50254 | known not affected: 416 | 2026-07-25T17:08:01+00:00 | Vulnerability · Source |
| CVE-2022-50259 | suse_vex | SUSE CVE CVE-2022-50259 | known affected: 163 known not affected: 253 | 2026-07-25T17:08:00+00:00 | Vulnerability · Source |
| CVE-2022-50262 | suse_vex | SUSE CVE CVE-2022-50262 | known not affected: 416 | 2026-07-25T17:07:57+00:00 | Vulnerability · Source |
| CVE-2022-50269 | suse_vex | SUSE CVE CVE-2022-50269 | known affected: 344 known not affected: 304 recommended: 255 | 2026-07-25T17:07:55+00:00 | Vulnerability · Source |
| CVE-2022-50273 | suse_vex | SUSE CVE CVE-2022-50273 | known affected: 169 known not affected: 286 | 2026-07-25T17:07:51+00:00 | Vulnerability · Source |
| CVE-2022-50285 | suse_vex | SUSE CVE CVE-2022-50285 | known affected: 567 known not affected: 244 recommended: 64 | 2026-07-25T17:07:47+00:00 | Vulnerability · Source |
| CVE-2022-50287 | suse_vex | SUSE CVE CVE-2022-50287 | known affected: 369 known not affected: 359 recommended: 141 | 2026-07-25T17:07:45+00:00 | Vulnerability · Source |
| CVE-2022-50295 | suse_vex | SUSE CVE CVE-2022-50295 | known not affected: 416 recommended: 29 | 2026-07-25T17:07:41+00:00 | Vulnerability · Source |
| CVE-2022-50302 | suse_vex | SUSE CVE CVE-2022-50302 | known not affected: 416 recommended: 27 | 2026-07-25T17:07:40+00:00 | Vulnerability · Source |
| CVE-2022-50305 | suse_vex | SUSE CVE CVE-2022-50305 | known not affected: 416 | 2026-07-25T17:07:38+00:00 | Vulnerability · Source |
| CVE-2022-50306 | suse_vex | SUSE CVE CVE-2022-50306 | known not affected: 416 recommended: 27 | 2026-07-25T17:07:37+00:00 | Vulnerability · Source |
| CVE-2022-50332 | suse_vex | SUSE CVE CVE-2022-50332 | known not affected: 416 | 2026-07-25T17:07:24+00:00 | Vulnerability · Source |
| CVE-2022-50336 | suse_vex | SUSE CVE CVE-2022-50336 | known not affected: 416 | 2026-07-25T17:07:21+00:00 | Vulnerability · Source |
| 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 |