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-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 |
| CVE-2022-49882 | suse_vex | SUSE CVE CVE-2022-49882 | known affected: 0 known not affected: 502 recommended: 58 | 2026-10-16T14:14:23+00:00 | Vulnerability · Source |
| CVE-2022-49883 | suse_vex | SUSE CVE CVE-2022-49883 | known affected: 0 known not affected: 502 | 2026-10-16T14:14:21+00:00 | Vulnerability · Source |
| CVE-2022-49887 | suse_vex | SUSE CVE CVE-2022-49887 | known affected: 365 known not affected: 320 recommended: 281 | 2026-10-16T14:14:16+00:00 | Vulnerability · Source |
| CVE-2022-49889 | suse_vex | SUSE CVE CVE-2022-49889 | known affected: 339 known not affected: 293 recommended: 304 | 2026-10-16T14:14:13+00:00 | Vulnerability · Source |
| CVE-2022-49892 | suse_vex | SUSE CVE CVE-2022-49892 | known affected: 486 known not affected: 160 recommended: 318 | 2026-10-16T14:14:11+00:00 | Vulnerability · Source |
| CVE-2022-49894 | suse_vex | SUSE CVE CVE-2022-49894 | known affected: 0 known not affected: 502 | 2026-10-16T14:14:08+00:00 | Vulnerability · Source |
| CVE-2022-49897 | suse_vex | SUSE CVE CVE-2022-49897 | known affected: 67 known not affected: 444 | 2026-10-16T14:14:06+00:00 | Vulnerability · Source |
| CVE-2022-49898 | suse_vex | SUSE CVE CVE-2022-49898 | known affected: 646 known not affected: 191 recommended: 37 | 2026-10-16T14:14:03+00:00 | Vulnerability · Source |
| CVE-2022-49900 | suse_vex | SUSE CVE CVE-2022-49900 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-16T14:14:01+00:00 | Vulnerability · Source |
| CVE-2022-49903 | suse_vex | SUSE CVE CVE-2022-49903 | known affected: 339 known not affected: 114 recommended: 74 | 2026-10-16T14:13:59+00:00 | Vulnerability · Source |
| CVE-2022-49905 | suse_vex | SUSE CVE CVE-2022-49905 | known affected: 339 known not affected: 383 recommended: 214 | 2026-10-16T14:13:57+00:00 | Vulnerability · Source |
| CVE-2022-49909 | suse_vex | SUSE CVE CVE-2022-49909 | known affected: 0 known not affected: 325 recommended: 196 | 2026-10-16T14:13:55+00:00 | Vulnerability · Source |
| CVE-2022-49910 | suse_vex | SUSE CVE CVE-2022-49910 | known affected: 0 known not affected: 289 recommended: 317 | 2026-10-16T14:13:53+00:00 | Vulnerability · Source |
| CVE-2022-49911 | suse_vex | SUSE CVE CVE-2022-49911 | known affected: 61 known not affected: 441 recommended: 54 | 2026-10-16T14:13:51+00:00 | Vulnerability · Source |
| CVE-2022-49913 | suse_vex | SUSE CVE CVE-2022-49913 | known affected: 646 known not affected: 191 recommended: 37 | 2026-10-16T14:13:48+00:00 | Vulnerability · Source |
| CVE-2022-49916 | suse_vex | SUSE CVE CVE-2022-49916 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-16T14:13:46+00:00 | Vulnerability · Source |
| CVE-2022-49917 | suse_vex | SUSE CVE CVE-2022-49917 | known affected: 645 known not affected: 121 recommended: 129 | 2026-10-16T14:13:44+00:00 | Vulnerability · Source |
| CVE-2022-49918 | suse_vex | SUSE CVE CVE-2022-49918 | known affected: 369 known not affected: 443 recommended: 92 | 2026-10-16T14:13:42+00:00 | Vulnerability · Source |
| CVE-2022-49919 | suse_vex | SUSE CVE CVE-2022-49919 | known affected: 0 known not affected: 502 | 2026-10-16T14:13:39+00:00 | Vulnerability · Source |
| CVE-2022-49920 | suse_vex | SUSE CVE CVE-2022-49920 | known affected: 61 known not affected: 441 recommended: 27 | 2026-10-16T14:13:37+00:00 | Vulnerability · Source |
| CVE-2022-49921 | suse_vex | SUSE CVE CVE-2022-49921 | known affected: 611 known not affected: 157 recommended: 115 | 2026-10-16T14:13:35+00:00 | Vulnerability · Source |