VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283955 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50065 | suse_vex | SUSE CVE CVE-2022-50065 | known affected: 375 known not affected: 237 recommended: 296 | 2026-07-25T17:09:42+00:00 | Vulnerability · Source |
| CVE-2022-50066 | suse_vex | SUSE CVE CVE-2022-50066 | known affected: 446 known not affected: 200 recommended: 291 | 2026-07-25T17:09:41+00:00 | Vulnerability · Source |
| CVE-2022-50067 | suse_vex | SUSE CVE CVE-2022-50067 | known not affected: 418 recommended: 286 | 2026-07-25T17:09:40+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-50079 | suse_vex | SUSE CVE CVE-2022-50079 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-25T17:09:37+00:00 | Vulnerability · Source |
| CVE-2022-50080 | suse_vex | SUSE CVE CVE-2022-50080 | known affected: 536 known not affected: 263 recommended: 52 | 2026-07-25T17:09:36+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-50092 | suse_vex | SUSE CVE CVE-2022-50092 | known affected: 419 known not affected: 254 recommended: 352 | 2026-07-25T17:09:30+00:00 | Vulnerability · Source |
| CVE-2022-50094 | suse_vex | SUSE CVE CVE-2022-50094 | known affected: 419 known not affected: 206 recommended: 310 | 2026-07-25T17:09:29+00:00 | Vulnerability · Source |
| CVE-2022-50099 | suse_vex | SUSE CVE CVE-2022-50099 | known affected: 344 known not affected: 283 recommended: 296 | 2026-07-25T17:09:27+00:00 | Vulnerability · Source |
| CVE-2022-50102 | suse_vex | SUSE CVE CVE-2022-50102 | known affected: 344 known not affected: 283 recommended: 296 | 2026-07-25T17:09:25+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-50110 | suse_vex | SUSE CVE CVE-2022-50110 | known affected: 344 known not affected: 298 recommended: 255 | 2026-07-25T17:09:21+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-50115 | suse_vex | SUSE CVE CVE-2022-50115 | known affected: 369 known not affected: 347 recommended: 134 | 2026-07-25T17:09:19+00:00 | Vulnerability · Source |
| CVE-2022-50117 | suse_vex | SUSE CVE CVE-2022-50117 | known affected: 369 known not affected: 347 recommended: 121 | 2026-07-25T17:09:17+00:00 | Vulnerability · Source |
| CVE-2022-50120 | suse_vex | SUSE CVE CVE-2022-50120 | known affected: 395 known not affected: 247 recommended: 233 | 2026-07-25T17:09:16+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-50125 | suse_vex | SUSE CVE CVE-2022-50125 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:09:13+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-50133 | suse_vex | SUSE CVE CVE-2022-50133 | known affected: 369 known not affected: 347 recommended: 139 | 2026-07-25T17:09:10+00:00 | Vulnerability · Source |
| CVE-2022-50137 | suse_vex | SUSE CVE CVE-2022-50137 | known affected: 344 known not affected: 298 recommended: 253 | 2026-07-25T17:09:09+00:00 | Vulnerability · Source |
| CVE-2022-50138 | suse_vex | SUSE CVE CVE-2022-50138 | known affected: 409 known not affected: 264 recommended: 357 | 2026-07-25T17:09:07+00:00 | Vulnerability · Source |
| CVE-2022-50139 | suse_vex | SUSE CVE CVE-2022-50139 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:09:06+00:00 | Vulnerability · Source |
| CVE-2022-50141 | suse_vex | SUSE CVE CVE-2022-50141 | known affected: 409 known not affected: 233 recommended: 296 | 2026-07-25T17:09:04+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-50144 | suse_vex | SUSE CVE CVE-2022-50144 | known affected: 475 known not affected: 241 recommended: 92 | 2026-07-25T17:09:01+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-50151 | suse_vex | SUSE CVE CVE-2022-50151 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:57+00:00 | Vulnerability · Source |
| CVE-2022-50157 | suse_vex | SUSE CVE CVE-2022-50157 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:56+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-50160 | suse_vex | SUSE CVE CVE-2022-50160 | known affected: 405 known not affected: 248 recommended: 273 | 2026-07-25T17:08:53+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-50165 | suse_vex | SUSE CVE CVE-2022-50165 | known affected: 405 known not affected: 246 recommended: 273 | 2026-07-25T17:08:50+00:00 | Vulnerability · Source |
| CVE-2022-50172 | suse_vex | SUSE CVE CVE-2022-50172 | known affected: 358 known not affected: 280 recommended: 320 | 2026-07-25T17:08:48+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-50175 | suse_vex | SUSE CVE CVE-2022-50175 | known affected: 442 known not affected: 215 recommended: 206 | 2026-07-25T17:08:46+00:00 | Vulnerability · Source |
| CVE-2022-50184 | suse_vex | SUSE CVE CVE-2022-50184 | known affected: 424 known not affected: 292 recommended: 92 | 2026-07-25T17:08:44+00:00 | Vulnerability · Source |
| CVE-2022-50186 | suse_vex | SUSE CVE CVE-2022-50186 | known affected: 369 known not affected: 347 recommended: 92 | 2026-07-25T17:08:43+00:00 | Vulnerability · Source |
| CVE-2022-50187 | suse_vex | SUSE CVE CVE-2022-50187 | known affected: 344 known not affected: 298 recommended: 248 | 2026-07-25T17:08:41+00:00 | Vulnerability · Source |
| CVE-2022-50194 | suse_vex | SUSE CVE CVE-2022-50194 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:39+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-50196 | suse_vex | SUSE CVE CVE-2022-50196 | known affected: 344 known not affected: 298 recommended: 233 | 2026-07-25T17:08:37+00:00 | Vulnerability · Source |
| CVE-2022-50198 | suse_vex | SUSE CVE CVE-2022-50198 | known affected: 348 known not affected: 309 recommended: 206 | 2026-07-25T17:08:35+00:00 | Vulnerability · Source |
| CVE-2022-50201 | suse_vex | SUSE CVE CVE-2022-50201 | known affected: 344 known not affected: 298 recommended: 235 | 2026-07-25T17:08:34+00:00 | Vulnerability · Source |
| CVE-2022-50203 | suse_vex | SUSE CVE CVE-2022-50203 | known affected: 348 known not affected: 309 recommended: 206 | 2026-07-25T17:08:32+00:00 | Vulnerability · Source |