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-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 |
| CVE-2022-49748 | suse_vex | SUSE CVE CVE-2022-49748 | known affected: 334 known not affected: 157 recommended: 280 | 2026-10-16T14:16:37+00:00 | Vulnerability · Source |
| CVE-2022-49752 | suse_vex | SUSE CVE CVE-2022-49752 | known affected: 0 known not affected: 456 recommended: 78 | 2026-10-16T14:16:34+00:00 | Vulnerability · Source |
| CVE-2022-49754 | suse_vex | SUSE CVE CVE-2022-49754 | known affected: 0 known not affected: 456 recommended: 58 | 2026-10-16T14:16:32+00:00 | Vulnerability · Source |
| CVE-2022-49755 | suse_vex | SUSE CVE CVE-2022-49755 | known affected: 530 known not affected: 147 recommended: 222 | 2026-10-16T14:16:29+00:00 | Vulnerability · Source |
| CVE-2022-49757 | suse_vex | SUSE CVE CVE-2022-49757 | known affected: 318 known not affected: 138 | 2026-10-16T14:16:27+00:00 | Vulnerability · Source |
| CVE-2022-49758 | suse_vex | SUSE CVE CVE-2022-49758 | known affected: 197 known not affected: 259 | 2026-10-16T14:16:24+00:00 | Vulnerability · Source |
| CVE-2022-49759 | suse_vex | SUSE CVE CVE-2022-49759 | known affected: 377 known not affected: 300 recommended: 300 | 2026-10-16T14:16:22+00:00 | Vulnerability · Source |
| CVE-2022-49760 | suse_vex | SUSE CVE CVE-2022-49760 | known affected: 0 known not affected: 456 recommended: 58 | 2026-10-16T14:16:20+00:00 | Vulnerability · Source |
| CVE-2022-49766 | suse_vex | SUSE CVE CVE-2022-49766 | known affected: 10 known not affected: 118 | 2026-10-16T14:16:17+00:00 | Vulnerability · Source |
| CVE-2022-49768 | suse_vex | SUSE CVE CVE-2022-49768 | known affected: 737 known not affected: 134 recommended: 23 | 2026-10-16T14:16:15+00:00 | Vulnerability · Source |
| CVE-2022-49770 | suse_vex | SUSE CVE CVE-2022-49770 | known affected: 490 known not affected: 194 recommended: 313 | 2026-10-16T14:16:10+00:00 | Vulnerability · Source |
| CVE-2022-49771 | suse_vex | SUSE CVE CVE-2022-49771 | known affected: 460 known not affected: 169 recommended: 318 | 2026-10-16T14:16:08+00:00 | Vulnerability · Source |
| CVE-2022-49772 | suse_vex | SUSE CVE CVE-2022-49772 | known affected: 496 known not affected: 148 recommended: 318 | 2026-10-16T14:16:06+00:00 | Vulnerability · Source |
| CVE-2022-49775 | suse_vex | SUSE CVE CVE-2022-49775 | known affected: 518 known not affected: 124 recommended: 330 | 2026-10-16T14:16:03+00:00 | Vulnerability · Source |
| CVE-2022-49777 | suse_vex | SUSE CVE CVE-2022-49777 | known affected: 343 known not affected: 349 recommended: 281 | 2026-10-16T14:16:01+00:00 | Vulnerability · Source |
| CVE-2022-49781 | suse_vex | SUSE CVE CVE-2022-49781 | known affected: 369 known not affected: 437 recommended: 92 | 2026-10-16T14:15:56+00:00 | Vulnerability · Source |
| CVE-2022-49783 | suse_vex | SUSE CVE CVE-2022-49783 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-16T14:15:53+00:00 | Vulnerability · Source |
| CVE-2022-49784 | suse_vex | SUSE CVE CVE-2022-49784 | known affected: 369 known not affected: 437 recommended: 92 | 2026-10-16T14:15:51+00:00 | Vulnerability · Source |
| CVE-2022-49788 | suse_vex | SUSE CVE CVE-2022-49788 | known affected: 490 known not affected: 156 recommended: 437 | 2026-10-16T14:15:48+00:00 | Vulnerability · Source |
| CVE-2022-49791 | suse_vex | SUSE CVE CVE-2022-49791 | known affected: 67 known not affected: 444 | 2026-10-16T14:15:46+00:00 | Vulnerability · Source |
| CVE-2022-49792 | suse_vex | SUSE CVE CVE-2022-49792 | known affected: 339 known not affected: 383 recommended: 214 | 2026-10-16T14:15:44+00:00 | Vulnerability · Source |