VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
99436 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-48626 | suse_vex | SUSE CVE CVE-2022-48626 | known not affected: 176 recommended: 566 | 2026-10-16T14:39:41+00:00 | Vulnerability · Source |
| CVE-2022-48627 | suse_vex | SUSE CVE CVE-2022-48627 | known affected: 478 known not affected: 66 recommended: 682 | 2026-10-16T14:39:38+00:00 | Vulnerability · Source |
| CVE-2022-48630 | suse_vex | SUSE CVE CVE-2022-48630 | known affected: 260 known not affected: 264 recommended: 471 | 2026-10-16T14:39:35+00:00 | Vulnerability · Source |
| CVE-2022-48631 | suse_vex | SUSE CVE CVE-2022-48631 | known affected: 402 known not affected: 72 recommended: 648 | 2026-10-16T14:39:32+00:00 | Vulnerability · Source |
| CVE-2022-48634 | suse_vex | SUSE CVE CVE-2022-48634 | known affected: 270 known not affected: 251 recommended: 457 | 2026-10-16T14:39:30+00:00 | Vulnerability · Source |
| CVE-2022-48639 | suse_vex | SUSE CVE CVE-2022-48639 | known affected: 459 known not affected: 232 recommended: 318 | 2026-10-16T14:39:27+00:00 | Vulnerability · Source |
| CVE-2022-48640 | suse_vex | SUSE CVE CVE-2022-48640 | known affected: 379 known not affected: 312 recommended: 318 | 2026-10-16T14:39:24+00:00 | Vulnerability · Source |
| CVE-2022-48642 | suse_vex | SUSE CVE CVE-2022-48642 | known affected: 471 known not affected: 224 recommended: 318 | 2026-10-16T14:39:21+00:00 | Vulnerability · Source |
| CVE-2022-48645 | suse_vex | SUSE CVE CVE-2022-48645 | known affected: 373 known not affected: 218 recommended: 288 | 2026-10-16T14:39:19+00:00 | Vulnerability · Source |
| CVE-2022-48653 | suse_vex | SUSE CVE CVE-2022-48653 | known affected: 265 known not affected: 251 recommended: 462 | 2026-10-16T14:39:16+00:00 | Vulnerability · Source |
| CVE-2022-48655 | suse_vex | SUSE CVE CVE-2022-48655 | known affected: 265 known not affected: 274 recommended: 462 | 2026-10-16T14:39:13+00:00 | Vulnerability · Source |
| CVE-2022-48658 | suse_vex | SUSE CVE CVE-2022-48658 | known affected: 383 known not affected: 312 recommended: 318 | 2026-10-16T14:39:10+00:00 | Vulnerability · Source |
| CVE-2022-48659 | suse_vex | SUSE CVE CVE-2022-48659 | known affected: 331 known not affected: 414 recommended: 318 | 2026-10-16T14:39:08+00:00 | Vulnerability · Source |
| CVE-2022-48663 | suse_vex | SUSE CVE CVE-2022-48663 | known affected: 265 known not affected: 251 recommended: 462 | 2026-10-16T14:39:05+00:00 | Vulnerability · Source |
| CVE-2022-48668 | suse_vex | SUSE CVE CVE-2022-48668 | known affected: 332 known not affected: 182 recommended: 532 | 2026-10-16T14:39:02+00:00 | Vulnerability · Source |
| CVE-2022-48669 | suse_vex | SUSE CVE CVE-2022-48669 | known affected: 431 known not affected: 251 recommended: 542 | 2026-10-16T14:38:59+00:00 | Vulnerability · Source |
| CVE-2022-48670 | suse_vex | SUSE CVE CVE-2022-48670 | known not affected: 641 | 2026-10-16T14:38:56+00:00 | Vulnerability · Source |
| CVE-2022-48673 | suse_vex | SUSE CVE CVE-2022-48673 | known affected: 296 known not affected: 178 recommended: 592 | 2026-10-16T14:38:54+00:00 | Vulnerability · Source |
| CVE-2022-48687 | suse_vex | SUSE CVE CVE-2022-48687 | known affected: 32 known not affected: 161 recommended: 536 | 2026-10-16T14:38:51+00:00 | Vulnerability · Source |
| CVE-2022-48698 | suse_vex | SUSE CVE CVE-2022-48698 | known affected: 591 known not affected: 108 recommended: 318 | 2026-10-16T14:38:45+00:00 | Vulnerability · Source |
| CVE-2022-48699 | suse_vex | SUSE CVE CVE-2022-48699 | known affected: 358 known not affected: 338 recommended: 373 | 2026-10-16T14:38:42+00:00 | Vulnerability · Source |
| CVE-2022-48704 | suse_vex | SUSE CVE CVE-2022-48704 | known affected: 408 known not affected: 67 recommended: 632 | 2026-10-16T14:38:39+00:00 | Vulnerability · Source |
| CVE-2022-48705 | suse_vex | SUSE CVE CVE-2022-48705 | known affected: 315 known not affected: 323 recommended: 313 | 2026-10-16T14:38:37+00:00 | Vulnerability · Source |
| CVE-2022-48706 | suse_vex | SUSE CVE CVE-2022-48706 | known affected: 340 known not affected: 332 recommended: 288 | 2026-10-16T14:38:34+00:00 | Vulnerability · Source |
| CVE-2022-48707 | suse_vex | SUSE CVE CVE-2022-48707 | known not affected: 385 | 2026-10-16T14:38:31+00:00 | Vulnerability · Source |
| CVE-2022-48708 | suse_vex | SUSE CVE CVE-2022-48708 | known affected: 449 known not affected: 67 recommended: 522 | 2026-10-16T14:38:29+00:00 | Vulnerability · Source |
| CVE-2022-48712 | suse_vex | SUSE CVE CVE-2022-48712 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:38:24+00:00 | Vulnerability · Source |
| CVE-2022-48713 | suse_vex | SUSE CVE CVE-2022-48713 | known affected: 295 known not affected: 254 recommended: 428 | 2026-10-16T14:38:21+00:00 | Vulnerability · Source |
| CVE-2022-48714 | suse_vex | SUSE CVE CVE-2022-48714 | known affected: 421 known not affected: 212 recommended: 298 | 2026-10-16T14:38:19+00:00 | Vulnerability · Source |
| CVE-2022-48715 | suse_vex | SUSE CVE CVE-2022-48715 | known affected: 460 known not affected: 70 recommended: 566 | 2026-10-16T14:38:16+00:00 | Vulnerability · Source |
| CVE-2022-48717 | suse_vex | SUSE CVE CVE-2022-48717 | known affected: 353 known not affected: 183 recommended: 482 | 2026-10-16T14:38:11+00:00 | Vulnerability · Source |
| CVE-2022-48719 | suse_vex | SUSE CVE CVE-2022-48719 | known not affected: 373 | 2026-10-16T14:38:09+00:00 | Vulnerability · Source |
| CVE-2022-48722 | suse_vex | SUSE CVE CVE-2022-48722 | known affected: 446 known not affected: 83 recommended: 552 | 2026-10-16T14:38:06+00:00 | Vulnerability · Source |
| CVE-2022-48724 | suse_vex | SUSE CVE CVE-2022-48724 | known affected: 353 known not affected: 183 recommended: 482 | 2026-10-16T14:38:01+00:00 | Vulnerability · Source |
| CVE-2022-48725 | suse_vex | SUSE CVE CVE-2022-48725 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:58+00:00 | Vulnerability · Source |
| CVE-2022-48727 | suse_vex | SUSE CVE CVE-2022-48727 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:56+00:00 | Vulnerability · Source |
| CVE-2022-48730 | suse_vex | SUSE CVE CVE-2022-48730 | known affected: 324 known not affected: 212 recommended: 484 | 2026-10-16T14:37:48+00:00 | Vulnerability · Source |
| CVE-2022-48731 | suse_vex | SUSE CVE CVE-2022-48731 | known not affected: 318 | 2026-10-16T14:37:46+00:00 | Vulnerability · Source |
| CVE-2022-48734 | suse_vex | SUSE CVE CVE-2022-48734 | known affected: 555 known not affected: 114 recommended: 391 | 2026-10-16T14:37:43+00:00 | Vulnerability · Source |
| CVE-2022-48735 | suse_vex | SUSE CVE CVE-2022-48735 | known affected: 362 known not affected: 118 recommended: 433 | 2026-10-16T14:37:41+00:00 | Vulnerability · Source |
| CVE-2022-48738 | suse_vex | SUSE CVE CVE-2022-48738 | known affected: 500 known not affected: 114 recommended: 524 | 2026-10-16T14:37:36+00:00 | Vulnerability · Source |
| CVE-2022-48745 | suse_vex | SUSE CVE CVE-2022-48745 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-16T14:37:31+00:00 | Vulnerability · Source |
| CVE-2022-48746 | suse_vex | SUSE CVE CVE-2022-48746 | known affected: 324 known not affected: 212 recommended: 482 | 2026-10-16T14:37:29+00:00 | Vulnerability · Source |
| CVE-2022-48747 | suse_vex | SUSE CVE CVE-2022-48747 | known affected: 324 known not affected: 212 recommended: 502 | 2026-10-16T14:37:27+00:00 | Vulnerability · Source |
| CVE-2022-48749 | suse_vex | SUSE CVE CVE-2022-48749 | known affected: 324 known not affected: 212 recommended: 484 | 2026-10-16T14:37:25+00:00 | Vulnerability · Source |
| CVE-2022-48751 | suse_vex | SUSE CVE CVE-2022-48751 | known affected: 473 known not affected: 110 recommended: 461 | 2026-10-16T14:37:22+00:00 | Vulnerability · Source |
| CVE-2022-48756 | suse_vex | SUSE CVE CVE-2022-48756 | known affected: 470 known not affected: 59 recommended: 568 | 2026-10-16T14:37:20+00:00 | Vulnerability · Source |
| CVE-2022-48757 | suse_vex | SUSE CVE CVE-2022-48757 | known affected: 433 known not affected: 125 recommended: 20 | 2026-10-16T14:37:17+00:00 | Vulnerability · Source |
| CVE-2022-48759 | suse_vex | SUSE CVE CVE-2022-48759 | known affected: 462 known not affected: 67 recommended: 552 | 2026-10-16T14:37:14+00:00 | Vulnerability · Source |
| CVE-2022-48761 | suse_vex | SUSE CVE CVE-2022-48761 | known affected: 520 known not affected: 53 recommended: 475 | 2026-10-16T14:37:12+00:00 | Vulnerability · Source |