VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104719 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49650 | suse_vex | SUSE CVE CVE-2022-49650 | known affected: 334 known not affected: 350 recommended: 222 | 2026-10-16T14:18:37+00:00 | Vulnerability · Source |
| CVE-2022-49651 | suse_vex | SUSE CVE CVE-2022-49651 | known affected: 0 known not affected: 297 recommended: 54 | 2026-10-16T14:18:35+00:00 | Vulnerability · Source |
| CVE-2022-49654 | suse_vex | SUSE CVE CVE-2022-49654 | known affected: 61 known not affected: 401 | 2026-10-16T14:18:33+00:00 | Vulnerability · Source |
| CVE-2022-49655 | suse_vex | SUSE CVE CVE-2022-49655 | known affected: 364 known not affected: 398 recommended: 154 | 2026-10-16T14:18:30+00:00 | Vulnerability · Source |
| CVE-2022-49656 | suse_vex | SUSE CVE CVE-2022-49656 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:18:28+00:00 | Vulnerability · Source |
| CVE-2022-49657 | suse_vex | SUSE CVE CVE-2022-49657 | known affected: 481 known not affected: 165 recommended: 374 | 2026-10-16T14:18:25+00:00 | Vulnerability · Source |
| CVE-2022-49659 | suse_vex | SUSE CVE CVE-2022-49659 | known affected: 61 known not affected: 401 recommended: 54 | 2026-10-16T14:18:23+00:00 | Vulnerability · Source |
| CVE-2022-49660 | suse_vex | SUSE CVE CVE-2022-49660 | No product status | 2026-10-16T14:18:20+00:00 | Vulnerability · Source |
| CVE-2022-49661 | suse_vex | SUSE CVE CVE-2022-49661 | known affected: 493 known not affected: 153 recommended: 333 | 2026-10-16T14:18:17+00:00 | Vulnerability · Source |
| CVE-2022-49662 | suse_vex | SUSE CVE CVE-2022-49662 | known affected: 61 known not affected: 401 | 2026-10-16T14:18:15+00:00 | Vulnerability · Source |
| CVE-2022-49665 | suse_vex | SUSE CVE CVE-2022-49665 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:18:13+00:00 | Vulnerability · Source |
| CVE-2022-49666 | suse_vex | SUSE CVE CVE-2022-49666 | known affected: 0 known not affected: 462 recommended: 54 | 2026-10-16T14:18:11+00:00 | Vulnerability · Source |
| CVE-2022-49670 | suse_vex | SUSE CVE CVE-2022-49670 | known affected: 420 known not affected: 276 recommended: 334 | 2026-10-16T14:18:09+00:00 | Vulnerability · Source |
| CVE-2022-49672 | suse_vex | SUSE CVE CVE-2022-49672 | known affected: 448 known not affected: 234 recommended: 290 | 2026-10-16T14:18:07+00:00 | Vulnerability · Source |
| CVE-2022-49673 | suse_vex | SUSE CVE CVE-2022-49673 | known affected: 487 known not affected: 158 recommended: 375 | 2026-10-16T14:18:04+00:00 | Vulnerability · Source |
| CVE-2022-49674 | suse_vex | SUSE CVE CVE-2022-49674 | known affected: 453 known not affected: 418 recommended: 353 | 2026-10-16T14:18:02+00:00 | Vulnerability · Source |
| CVE-2022-49676 | suse_vex | SUSE CVE CVE-2022-49676 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:18:00+00:00 | Vulnerability · Source |
| CVE-2022-49677 | suse_vex | SUSE CVE CVE-2022-49677 | known affected: 528 known not affected: 238 recommended: 223 | 2026-10-16T14:17:58+00:00 | Vulnerability · Source |
| CVE-2022-49682 | suse_vex | SUSE CVE CVE-2022-49682 | known affected: 0 known not affected: 462 | 2026-10-16T14:17:53+00:00 | Vulnerability · Source |
| CVE-2022-49683 | suse_vex | SUSE CVE CVE-2022-49683 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:17:51+00:00 | Vulnerability · Source |
| CVE-2022-49684 | suse_vex | SUSE CVE CVE-2022-49684 | known affected: 0 known not affected: 462 | 2026-10-16T14:17:48+00:00 | Vulnerability · Source |
| CVE-2022-49685 | suse_vex | SUSE CVE CVE-2022-49685 | known affected: 429 known not affected: 302 recommended: 293 | 2026-10-16T14:17:45+00:00 | Vulnerability · Source |
| CVE-2022-49690 | suse_vex | SUSE CVE CVE-2022-49690 | No product status | 2026-10-16T14:17:43+00:00 | Vulnerability · Source |
| CVE-2022-49694 | suse_vex | SUSE CVE CVE-2022-49694 | known affected: 364 known not affected: 401 recommended: 100 | 2026-10-16T14:17:40+00:00 | Vulnerability · Source |
| CVE-2022-49697 | suse_vex | SUSE CVE CVE-2022-49697 | known affected: 494 known not affected: 268 recommended: 142 | 2026-10-16T14:17:38+00:00 | Vulnerability · Source |
| CVE-2022-49698 | suse_vex | SUSE CVE CVE-2022-49698 | known affected: 0 known not affected: 460 recommended: 42 | 2026-10-16T14:17:36+00:00 | Vulnerability · Source |
| CVE-2022-49700 | suse_vex | SUSE CVE CVE-2022-49700 | known affected: 485 known not affected: 246 recommended: 367 | 2026-10-16T14:17:34+00:00 | Vulnerability · Source |
| CVE-2022-49702 | suse_vex | SUSE CVE CVE-2022-49702 | known affected: 61 known not affected: 401 | 2026-10-16T14:17:31+00:00 | Vulnerability · Source |
| CVE-2022-49705 | suse_vex | SUSE CVE CVE-2022-49705 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-16T14:17:29+00:00 | Vulnerability · Source |
| CVE-2022-49707 | suse_vex | SUSE CVE CVE-2022-49707 | known affected: 427 known not affected: 404 recommended: 387 | 2026-10-16T14:17:27+00:00 | Vulnerability · Source |
| CVE-2022-49709 | suse_vex | SUSE CVE CVE-2022-49709 | known affected: 61 known not affected: 401 | 2026-10-16T14:17:25+00:00 | Vulnerability · Source |
| CVE-2022-49710 | suse_vex | SUSE CVE CVE-2022-49710 | known affected: 487 known not affected: 159 recommended: 375 | 2026-10-16T14:17:22+00:00 | Vulnerability · Source |
| CVE-2022-49711 | suse_vex | SUSE CVE CVE-2022-49711 | known affected: 465 known not affected: 179 recommended: 333 | 2026-10-16T14:17:20+00:00 | Vulnerability · Source |
| CVE-2022-49714 | suse_vex | SUSE CVE CVE-2022-49714 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:17:18+00:00 | Vulnerability · Source |
| CVE-2022-49716 | suse_vex | SUSE CVE CVE-2022-49716 | known affected: 377 known not affected: 351 recommended: 281 | 2026-10-16T14:17:16+00:00 | Vulnerability · Source |
| CVE-2022-49718 | suse_vex | SUSE CVE CVE-2022-49718 | known affected: 0 known not affected: 462 | 2026-10-16T14:17:14+00:00 | Vulnerability · Source |
| CVE-2022-49720 | suse_vex | SUSE CVE CVE-2022-49720 | known affected: 392 known not affected: 392 recommended: 293 | 2026-10-16T14:17:11+00:00 | Vulnerability · Source |
| CVE-2022-49722 | suse_vex | SUSE CVE CVE-2022-49722 | known affected: 403 known not affected: 325 recommended: 265 | 2026-10-16T14:17:09+00:00 | Vulnerability · Source |
| CVE-2022-49723 | suse_vex | SUSE CVE CVE-2022-49723 | known affected: 360 known not affected: 337 recommended: 367 | 2026-10-16T14:17:07+00:00 | Vulnerability · Source |
| CVE-2022-49728 | suse_vex | SUSE CVE CVE-2022-49728 | known affected: 728 known not affected: 98 recommended: 40 | 2026-10-16T14:17:03+00:00 | Vulnerability · Source |
| CVE-2022-49729 | suse_vex | SUSE CVE CVE-2022-49729 | known affected: 499 known not affected: 192 recommended: 330 | 2026-10-16T14:17:00+00:00 | Vulnerability · Source |
| CVE-2022-49731 | suse_vex | SUSE CVE CVE-2022-49731 | known affected: 499 known not affected: 192 recommended: 388 | 2026-10-16T14:16:57+00:00 | Vulnerability · Source |
| CVE-2022-49732 | suse_vex | SUSE CVE CVE-2022-49732 | known affected: 425 known not affected: 337 recommended: 142 | 2026-10-16T14:16:55+00:00 | Vulnerability · Source |
| CVE-2022-49738 | suse_vex | SUSE CVE CVE-2022-49738 | known affected: 0 known not affected: 460 | 2026-10-16T14:16:53+00:00 | Vulnerability · Source |
| CVE-2022-49739 | suse_vex | SUSE CVE CVE-2022-49739 | known affected: 442 known not affected: 231 recommended: 358 | 2026-10-16T14:16:50+00:00 | Vulnerability · Source |
| CVE-2022-49740 | suse_vex | SUSE CVE CVE-2022-49740 | known affected: 394 known not affected: 403 recommended: 26 | 2026-10-16T14:16:48+00:00 | Vulnerability · Source |
| CVE-2022-49742 | suse_vex | SUSE CVE CVE-2022-49742 | known affected: 0 known not affected: 502 | 2026-10-16T14:16:46+00:00 | Vulnerability · Source |
| CVE-2022-49743 | suse_vex | SUSE CVE CVE-2022-49743 | known affected: 128 known not affected: 364 | 2026-10-16T14:16:44+00:00 | Vulnerability · Source |
| CVE-2022-49744 | suse_vex | SUSE CVE CVE-2022-49744 | known affected: 0 known not affected: 456 recommended: 58 | 2026-10-16T14:16:42+00:00 | Vulnerability · Source |
| CVE-2022-49746 | suse_vex | SUSE CVE CVE-2022-49746 | known affected: 403 known not affected: 274 recommended: 280 | 2026-10-16T14:16:39+00:00 | Vulnerability · Source |