VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291704 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-50312 | suse_vex | SUSE CVE CVE-2022-50312 | known affected: 419 known not affected: 187 recommended: 310 | 2026-08-14T01:17:27+00:00 | Vulnerability · Source |
| CVE-2022-50320 | suse_vex | SUSE CVE CVE-2022-50320 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-14T01:17:25+00:00 | Vulnerability · Source |
| CVE-2022-50321 | suse_vex | SUSE CVE CVE-2022-50321 | known affected: 398 known not affected: 220 recommended: 229 | 2026-08-14T01:17:24+00:00 | Vulnerability · Source |
| CVE-2022-50329 | suse_vex | SUSE CVE CVE-2022-50329 | known affected: 344 known not affected: 298 recommended: 239 | 2026-08-14T01:17:22+00:00 | Vulnerability · Source |
| CVE-2022-50337 | suse_vex | SUSE CVE CVE-2022-50337 | known affected: 55 known not affected: 361 | 2026-08-14T01:17:19+00:00 | Vulnerability · Source |
| CVE-2022-50344 | suse_vex | SUSE CVE CVE-2022-50344 | known affected: 425 known not affected: 181 recommended: 357 | 2026-08-14T01:17:17+00:00 | Vulnerability · Source |
| CVE-2022-50360 | suse_vex | SUSE CVE CVE-2022-50360 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-14T01:17:16+00:00 | Vulnerability · Source |
| CVE-2022-50368 | suse_vex | SUSE CVE CVE-2022-50368 | known affected: 419 known not affected: 160 recommended: 296 | 2026-08-14T01:17:14+00:00 | Vulnerability · Source |
| CVE-2022-50370 | suse_vex | SUSE CVE CVE-2022-50370 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-14T01:17:12+00:00 | Vulnerability · Source |
| CVE-2022-50391 | suse_vex | SUSE CVE CVE-2022-50391 | known affected: 344 known not affected: 304 recommended: 235 | 2026-08-14T01:17:08+00:00 | Vulnerability · Source |
| CVE-2022-50392 | suse_vex | SUSE CVE CVE-2022-50392 | known affected: 395 known not affected: 253 recommended: 233 | 2026-08-14T01:17:07+00:00 | Vulnerability · Source |
| CVE-2022-50414 | suse_vex | SUSE CVE CVE-2022-50414 | known affected: 425 known not affected: 154 recommended: 296 | 2026-08-14T01:17:05+00:00 | Vulnerability · Source |
| CVE-2022-50417 | suse_vex | SUSE CVE CVE-2022-50417 | known affected: 395 known not affected: 253 recommended: 206 | 2026-08-14T01:17:04+00:00 | Vulnerability · Source |
| CVE-2022-50423 | suse_vex | SUSE CVE CVE-2022-50423 | known affected: 419 known not affected: 187 recommended: 356 | 2026-08-14T01:17:02+00:00 | Vulnerability · Source |
| CVE-2022-50433 | suse_vex | SUSE CVE CVE-2022-50433 | known affected: 369 known not affected: 359 recommended: 92 | 2026-08-14T01:17:00+00:00 | Vulnerability · Source |
| CVE-2022-50443 | suse_vex | SUSE CVE CVE-2022-50443 | known affected: 442 known not affected: 176 recommended: 229 | 2026-08-14T01:16:59+00:00 | Vulnerability · Source |
| CVE-2022-50444 | suse_vex | SUSE CVE CVE-2022-50444 | known affected: 344 known not affected: 267 recommended: 302 | 2026-08-14T01:16:58+00:00 | Vulnerability · Source |
| CVE-2022-50447 | suse_vex | SUSE CVE CVE-2022-50447 | known affected: 369 known not affected: 359 recommended: 121 | 2026-08-14T01:16:56+00:00 | Vulnerability · Source |
| CVE-2022-50452 | suse_vex | SUSE CVE CVE-2022-50452 | known affected: 475 known not affected: 253 recommended: 139 | 2026-08-14T01:16:55+00:00 | Vulnerability · Source |
| CVE-2022-50453 | suse_vex | SUSE CVE CVE-2022-50453 | known affected: 448 known not affected: 207 recommended: 258 | 2026-08-14T01:16:53+00:00 | Vulnerability · Source |
| CVE-2022-50456 | suse_vex | SUSE CVE CVE-2022-50456 | known affected: 468 known not affected: 185 recommended: 229 | 2026-08-14T01:16:52+00:00 | Vulnerability · Source |
| CVE-2022-50458 | suse_vex | SUSE CVE CVE-2022-50458 | known affected: 405 known not affected: 176 recommended: 302 | 2026-08-14T01:16:50+00:00 | Vulnerability · Source |
| CVE-2022-50460 | suse_vex | SUSE CVE CVE-2022-50460 | known affected: 442 known not affected: 176 recommended: 258 | 2026-08-14T01:16:48+00:00 | Vulnerability · Source |
| CVE-2022-50464 | suse_vex | SUSE CVE CVE-2022-50464 | known affected: 424 known not affected: 304 recommended: 141 | 2026-08-14T01:16:46+00:00 | Vulnerability · Source |
| CVE-2022-50466 | suse_vex | SUSE CVE CVE-2022-50466 | known affected: 344 known not affected: 304 recommended: 206 | 2026-08-14T01:16:45+00:00 | Vulnerability · Source |
| CVE-2022-50480 | suse_vex | SUSE CVE CVE-2022-50480 | known affected: 368 known not affected: 256 recommended: 259 | 2026-08-14T01:16:41+00:00 | Vulnerability · Source |
| CVE-2022-50493 | suse_vex | SUSE CVE CVE-2022-50493 | known affected: 415 known not affected: 179 recommended: 302 | 2026-08-14T01:16:38+00:00 | Vulnerability · Source |
| CVE-2022-50497 | suse_vex | SUSE CVE CVE-2022-50497 | known affected: 466 known not affected: 160 recommended: 196 | 2026-08-14T01:16:36+00:00 | Vulnerability · Source |
| CVE-2022-50499 | suse_vex | SUSE CVE CVE-2022-50499 | known affected: 354 known not affected: 300 recommended: 196 | 2026-08-14T01:16:34+00:00 | Vulnerability · Source |
| CVE-2022-50511 | suse_vex | SUSE CVE CVE-2022-50511 | known affected: 478 known not affected: 185 recommended: 239 | 2026-08-14T01:16:32+00:00 | Vulnerability · Source |
| CVE-2022-50529 | suse_vex | SUSE CVE CVE-2022-50529 | known affected: 452 known not affected: 206 recommended: 196 | 2026-08-14T01:16:24+00:00 | Vulnerability · Source |
| CVE-2022-50543 | suse_vex | SUSE CVE CVE-2022-50543 | known affected: 374 known not affected: 359 recommended: 136 | 2026-08-14T01:16:21+00:00 | Vulnerability · Source |
| CVE-2022-50553 | suse_vex | SUSE CVE CVE-2022-50553 | known affected: 405 known not affected: 253 recommended: 196 | 2026-08-14T01:16:17+00:00 | Vulnerability · Source |
| CVE-2022-50565 | suse_vex | SUSE CVE CVE-2022-50565 | known not affected: 407 | 2026-08-14T01:16:14+00:00 | Vulnerability · Source |
| CVE-2022-50582 | suse_vex | SUSE CVE CVE-2022-50582 | known affected: 354 known not affected: 295 recommended: 225 | 2026-08-14T01:16:08+00:00 | Vulnerability · Source |
| CVE-2022-50634 | suse_vex | SUSE CVE CVE-2022-50634 | known affected: 112 known not affected: 296 | 2026-08-14T01:16:03+00:00 | Vulnerability · Source |
| CVE-2022-50640 | suse_vex | SUSE CVE CVE-2022-50640 | known affected: 435 known not affected: 218 recommended: 237 | 2026-08-14T01:16:01+00:00 | Vulnerability · Source |
| CVE-2022-50668 | suse_vex | SUSE CVE CVE-2022-50668 | known affected: 429 known not affected: 222 recommended: 284 | 2026-08-14T01:15:58+00:00 | Vulnerability · Source |
| CVE-2022-50698 | suse_vex | SUSE CVE CVE-2022-50698 | known affected: 354 known not affected: 341 recommended: 243 | 2026-08-14T01:15:56+00:00 | Vulnerability · Source |
| CVE-2022-50711 | suse_vex | SUSE CVE CVE-2022-50711 | known not affected: 453 | 2026-08-14T01:15:51+00:00 | Vulnerability · Source |
| CVE-2022-50712 | suse_vex | SUSE CVE CVE-2022-50712 | known affected: 374 known not affected: 396 recommended: 116 | 2026-08-14T01:15:49+00:00 | Vulnerability · Source |
| CVE-2022-50715 | suse_vex | SUSE CVE CVE-2022-50715 | known affected: 354 known not affected: 311 recommended: 266 | 2026-08-14T01:15:46+00:00 | Vulnerability · Source |
| CVE-2022-50722 | suse_vex | SUSE CVE CVE-2022-50722 | known affected: 409 known not affected: 288 recommended: 196 | 2026-08-14T01:15:42+00:00 | Vulnerability · Source |
| CVE-2022-50759 | suse_vex | SUSE CVE CVE-2022-50759 | known affected: 110 known not affected: 343 | 2026-08-14T01:15:33+00:00 | Vulnerability · Source |
| CVE-2022-50766 | suse_vex | SUSE CVE CVE-2022-50766 | known affected: 167 known not affected: 254 | 2026-08-14T01:15:31+00:00 | Vulnerability · Source |
| CVE-2022-50784 | suse_vex | SUSE CVE CVE-2022-50784 | known not affected: 453 recommended: 49 | 2026-08-14T01:15:30+00:00 | Vulnerability · Source |
| CVE-2022-50815 | suse_vex | SUSE CVE CVE-2022-50815 | known not affected: 421 | 2026-08-14T01:15:28+00:00 | Vulnerability · Source |
| CVE-2022-50818 | suse_vex | SUSE CVE CVE-2022-50818 | known affected: 374 known not affected: 396 recommended: 87 | 2026-08-14T01:15:27+00:00 | Vulnerability · Source |
| CVE-2022-50825 | suse_vex | SUSE CVE CVE-2022-50825 | known not affected: 453 recommended: 29 | 2026-08-14T01:15:25+00:00 | Vulnerability · Source |
| CVE-2022-50833 | suse_vex | SUSE CVE CVE-2022-50833 | known affected: 374 known not affected: 396 recommended: 114 | 2026-08-14T01:15:23+00:00 | Vulnerability · Source |