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-49838 | suse_vex | SUSE CVE CVE-2022-49838 | known not affected: 402 | 2026-07-25T17:10:55+00:00 | Vulnerability · Source |
| CVE-2022-49851 | suse_vex | SUSE CVE CVE-2022-49851 | known not affected: 402 | 2026-07-25T17:10:52+00:00 | Vulnerability · Source |
| CVE-2022-49873 | suse_vex | SUSE CVE CVE-2022-49873 | known affected: 106 known not affected: 291 recommended: 29 | 2026-07-25T17:10:46+00:00 | Vulnerability · Source |
| CVE-2022-49896 | suse_vex | SUSE CVE CVE-2022-49896 | known not affected: 397 | 2026-07-25T17:10:39+00:00 | Vulnerability · Source |
| CVE-2022-49899 | suse_vex | SUSE CVE CVE-2022-49899 | known affected: 55 known not affected: 342 | 2026-07-25T17:10:36+00:00 | Vulnerability · Source |
| CVE-2022-49903 | suse_vex | SUSE CVE CVE-2022-49903 | known affected: 245 known not affected: 131 recommended: 47 | 2026-07-25T17:10:35+00:00 | Vulnerability · Source |
| CVE-2022-49929 | suse_vex | SUSE CVE CVE-2022-49929 | known affected: 369 known not affected: 343 recommended: 92 | 2026-07-25T17:10:29+00:00 | Vulnerability · Source |
| CVE-2022-49937 | suse_vex | SUSE CVE CVE-2022-49937 | known not affected: 260 recommended: 286 | 2026-07-25T17:10:24+00:00 | Vulnerability · Source |
| CVE-2022-49947 | suse_vex | SUSE CVE CVE-2022-49947 | known not affected: 401 | 2026-07-25T17:10:21+00:00 | Vulnerability · Source |
| CVE-2022-49976 | suse_vex | SUSE CVE CVE-2022-49976 | known not affected: 401 | 2026-07-25T17:10:07+00:00 | Vulnerability · Source |
| CVE-2022-50000 | suse_vex | SUSE CVE CVE-2022-50000 | known affected: 92 known not affected: 309 recommended: 42 | 2026-07-25T17:10:02+00:00 | Vulnerability · Source |
| CVE-2022-50025 | suse_vex | SUSE CVE CVE-2022-50025 | known affected: 623 known not affected: 161 recommended: 23 | 2026-07-25T17:09:54+00:00 | Vulnerability · Source |
| CVE-2022-50048 | suse_vex | SUSE CVE CVE-2022-50048 | known affected: 55 known not affected: 346 recommended: 42 | 2026-07-25T17:09:47+00:00 | Vulnerability · Source |
| CVE-2022-50071 | suse_vex | SUSE CVE CVE-2022-50071 | known affected: 70 known not affected: 346 | 2026-07-25T17:09:39+00:00 | Vulnerability · Source |
| CVE-2022-50081 | suse_vex | SUSE CVE CVE-2022-50081 | known not affected: 401 recommended: 47 | 2026-07-25T17:09:34+00:00 | Vulnerability · Source |
| CVE-2022-50088 | suse_vex | SUSE CVE CVE-2022-50088 | known not affected: 401 recommended: 27 | 2026-07-25T17:09:33+00:00 | Vulnerability · Source |
| CVE-2022-50089 | suse_vex | SUSE CVE CVE-2022-50089 | known affected: 55 known not affected: 346 | 2026-07-25T17:09:32+00:00 | Vulnerability · Source |
| CVE-2022-50105 | suse_vex | SUSE CVE CVE-2022-50105 | known not affected: 416 | 2026-07-25T17:09:24+00:00 | Vulnerability · Source |
| CVE-2022-50107 | suse_vex | SUSE CVE CVE-2022-50107 | known affected: 57 known not affected: 359 recommended: 29 | 2026-07-25T17:09:23+00:00 | Vulnerability · Source |
| CVE-2022-50114 | suse_vex | SUSE CVE CVE-2022-50114 | known affected: 106 known not affected: 295 | 2026-07-25T17:09:20+00:00 | Vulnerability · Source |
| CVE-2022-50122 | suse_vex | SUSE CVE CVE-2022-50122 | known affected: 47 known not affected: 369 recommended: 27 | 2026-07-25T17:09:14+00:00 | Vulnerability · Source |
| CVE-2022-50126 | suse_vex | SUSE CVE CVE-2022-50126 | known affected: 425 known not affected: 200 recommended: 357 | 2026-07-25T17:09:11+00:00 | Vulnerability · Source |
| CVE-2022-50142 | suse_vex | SUSE CVE CVE-2022-50142 | known affected: 358 known not affected: 280 recommended: 273 | 2026-07-25T17:09:03+00:00 | Vulnerability · Source |
| CVE-2022-50147 | suse_vex | SUSE CVE CVE-2022-50147 | known not affected: 416 recommended: 27 | 2026-07-25T17:09:00+00:00 | Vulnerability · Source |
| CVE-2022-50148 | suse_vex | SUSE CVE CVE-2022-50148 | known not affected: 401 recommended: 47 | 2026-07-25T17:08:59+00:00 | Vulnerability · Source |
| CVE-2022-50159 | suse_vex | SUSE CVE CVE-2022-50159 | known affected: 619 known not affected: 161 recommended: 43 | 2026-07-25T17:08:54+00:00 | Vulnerability · Source |
| CVE-2022-50163 | suse_vex | SUSE CVE CVE-2022-50163 | known affected: 92 known not affected: 309 | 2026-07-25T17:08:51+00:00 | Vulnerability · Source |
| CVE-2022-50174 | suse_vex | SUSE CVE CVE-2022-50174 | known affected: 106 known not affected: 295 | 2026-07-25T17:08:47+00:00 | Vulnerability · Source |
| CVE-2022-50195 | suse_vex | SUSE CVE CVE-2022-50195 | known affected: 55 known not affected: 346 | 2026-07-25T17:08:38+00:00 | Vulnerability · Source |
| CVE-2022-50205 | suse_vex | SUSE CVE CVE-2022-50205 | known affected: 245 known not affected: 171 | 2026-07-25T17:08:30+00:00 | Vulnerability · Source |
| CVE-2022-50219 | suse_vex | SUSE CVE CVE-2022-50219 | known affected: 92 known not affected: 309 recommended: 47 | 2026-07-25T17:08:21+00:00 | Vulnerability · Source |
| CVE-2022-50223 | suse_vex | SUSE CVE CVE-2022-50223 | known not affected: 401 | 2026-07-25T17:08:17+00:00 | Vulnerability · Source |
| CVE-2022-50230 | suse_vex | SUSE CVE CVE-2022-50230 | known not affected: 401 | 2026-07-25T17:08:12+00:00 | Vulnerability · Source |
| 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 |