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-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 |
| CVE-2022-49796 | suse_vex | SUSE CVE CVE-2022-49796 | known affected: 339 known not affected: 383 recommended: 214 | 2026-10-16T14:15:41+00:00 | Vulnerability · Source |
| CVE-2022-49799 | suse_vex | SUSE CVE CVE-2022-49799 | known affected: 365 known not affected: 321 recommended: 281 | 2026-10-16T14:15:37+00:00 | Vulnerability · Source |
| CVE-2022-49804 | suse_vex | SUSE CVE CVE-2022-49804 | known affected: 0 known not affected: 507 recommended: 86 | 2026-10-16T14:15:34+00:00 | Vulnerability · Source |
| CVE-2022-49807 | suse_vex | SUSE CVE CVE-2022-49807 | known affected: 339 known not affected: 387 recommended: 214 | 2026-10-16T14:15:31+00:00 | Vulnerability · Source |
| CVE-2022-49808 | suse_vex | SUSE CVE CVE-2022-49808 | known affected: 197 known not affected: 310 | 2026-10-16T14:15:29+00:00 | Vulnerability · Source |
| CVE-2022-49815 | suse_vex | SUSE CVE CVE-2022-49815 | known affected: 0 known not affected: 502 recommended: 86 | 2026-10-16T14:15:24+00:00 | Vulnerability · Source |
| CVE-2022-49816 | suse_vex | SUSE CVE CVE-2022-49816 | No product status | 2026-10-16T14:15:22+00:00 | Vulnerability · Source |
| CVE-2022-49819 | suse_vex | SUSE CVE CVE-2022-49819 | known affected: 0 known not affected: 502 | 2026-10-16T14:15:20+00:00 | Vulnerability · Source |
| CVE-2022-49823 | suse_vex | SUSE CVE CVE-2022-49823 | known affected: 339 known not affected: 362 recommended: 281 | 2026-10-16T14:15:15+00:00 | Vulnerability · Source |
| CVE-2022-49825 | suse_vex | SUSE CVE CVE-2022-49825 | known affected: 496 known not affected: 147 recommended: 318 | 2026-10-16T14:15:12+00:00 | Vulnerability · Source |
| CVE-2022-49826 | suse_vex | SUSE CVE CVE-2022-49826 | known affected: 462 known not affected: 169 recommended: 304 | 2026-10-16T14:15:10+00:00 | Vulnerability · Source |
| CVE-2022-49827 | suse_vex | SUSE CVE CVE-2022-49827 | known affected: 339 known not affected: 347 recommended: 359 | 2026-10-16T14:15:07+00:00 | Vulnerability · Source |
| CVE-2022-49831 | suse_vex | SUSE CVE CVE-2022-49831 | known affected: 290 known not affected: 154 | 2026-10-16T14:15:05+00:00 | Vulnerability · Source |
| CVE-2022-49832 | suse_vex | SUSE CVE CVE-2022-49832 | known affected: 490 known not affected: 142 recommended: 304 | 2026-10-16T14:15:03+00:00 | Vulnerability · Source |
| CVE-2022-49833 | suse_vex | SUSE CVE CVE-2022-49833 | known affected: 339 known not affected: 118 | 2026-10-16T14:15:01+00:00 | Vulnerability · Source |
| CVE-2022-49846 | suse_vex | SUSE CVE CVE-2022-49846 | known affected: 458 known not affected: 173 recommended: 410 | 2026-10-16T14:14:56+00:00 | Vulnerability · Source |
| CVE-2022-49847 | suse_vex | SUSE CVE CVE-2022-49847 | known affected: 0 known not affected: 502 | 2026-10-16T14:14:54+00:00 | Vulnerability · Source |
| CVE-2022-49851 | suse_vex | SUSE CVE CVE-2022-49851 | known affected: 0 known not affected: 507 | 2026-10-16T14:14:52+00:00 | Vulnerability · Source |
| CVE-2022-49852 | suse_vex | SUSE CVE CVE-2022-49852 | known affected: 0 known not affected: 507 | 2026-10-16T14:14:50+00:00 | Vulnerability · Source |
| CVE-2022-49856 | suse_vex | SUSE CVE CVE-2022-49856 | known affected: 0 known not affected: 502 | 2026-10-16T14:14:47+00:00 | Vulnerability · Source |
| CVE-2022-49858 | suse_vex | SUSE CVE CVE-2022-49858 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-16T14:14:45+00:00 | Vulnerability · Source |
| CVE-2022-49859 | suse_vex | SUSE CVE CVE-2022-49859 | known affected: 61 known not affected: 441 | 2026-10-16T14:14:43+00:00 | Vulnerability · Source |
| CVE-2022-49862 | suse_vex | SUSE CVE CVE-2022-49862 | known affected: 621 known not affected: 221 recommended: 97 | 2026-10-16T14:14:41+00:00 | Vulnerability · Source |
| CVE-2022-49863 | suse_vex | SUSE CVE CVE-2022-49863 | known affected: 339 known not affected: 388 recommended: 214 | 2026-10-16T14:14:39+00:00 | Vulnerability · Source |
| CVE-2022-49865 | suse_vex | SUSE CVE CVE-2022-49865 | known affected: 539 known not affected: 141 recommended: 251 | 2026-10-16T14:14:36+00:00 | Vulnerability · Source |
| CVE-2022-49870 | suse_vex | SUSE CVE CVE-2022-49870 | known affected: 550 known not affected: 148 recommended: 281 | 2026-10-16T14:14:32+00:00 | Vulnerability · Source |
| CVE-2022-49873 | suse_vex | SUSE CVE CVE-2022-49873 | known affected: 130 known not affected: 372 recommended: 58 | 2026-10-16T14:14:30+00:00 | Vulnerability · Source |
| CVE-2022-49874 | suse_vex | SUSE CVE CVE-2022-49874 | known affected: 533 known not affected: 148 recommended: 251 | 2026-10-16T14:14:27+00:00 | Vulnerability · Source |
| CVE-2022-49879 | suse_vex | SUSE CVE CVE-2022-49879 | known affected: 496 known not affected: 149 recommended: 318 | 2026-10-16T14:14:25+00:00 | Vulnerability · Source |