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-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 |
| CVE-2022-49925 | suse_vex | SUSE CVE CVE-2022-49925 | known affected: 533 known not affected: 131 recommended: 325 | 2026-10-16T14:13:33+00:00 | Vulnerability · Source |
| CVE-2022-49926 | suse_vex | SUSE CVE CVE-2022-49926 | known affected: 212 known not affected: 305 | 2026-10-16T14:13:30+00:00 | Vulnerability · Source |
| CVE-2022-49930 | suse_vex | SUSE CVE CVE-2022-49930 | known affected: 0 known not affected: 507 | 2026-10-16T14:13:28+00:00 | Vulnerability · Source |
| CVE-2022-49933 | suse_vex | SUSE CVE CVE-2022-49933 | No product status | 2026-10-16T14:13:25+00:00 | Vulnerability · Source |
| CVE-2022-49937 | suse_vex | SUSE CVE CVE-2022-49937 | known affected: 0 known not affected: 321 recommended: 286 | 2026-10-16T14:13:23+00:00 | Vulnerability · Source |
| CVE-2022-49938 | suse_vex | SUSE CVE CVE-2022-49938 | known affected: 506 known not affected: 171 recommended: 287 | 2026-10-16T14:13:20+00:00 | Vulnerability · Source |
| CVE-2022-49941 | suse_vex | SUSE CVE CVE-2022-49941 | No product status | 2026-10-16T14:13:18+00:00 | Vulnerability · Source |
| CVE-2022-49943 | suse_vex | SUSE CVE CVE-2022-49943 | known affected: 369 known not affected: 329 recommended: 262 | 2026-10-16T14:13:15+00:00 | Vulnerability · Source |
| CVE-2022-49946 | suse_vex | SUSE CVE CVE-2022-49946 | known affected: 387 known not affected: 343 recommended: 206 | 2026-10-16T14:13:13+00:00 | Vulnerability · Source |
| CVE-2022-49948 | suse_vex | SUSE CVE CVE-2022-49948 | known affected: 501 known not affected: 185 recommended: 310 | 2026-10-16T14:13:10+00:00 | Vulnerability · Source |
| CVE-2022-49951 | suse_vex | SUSE CVE CVE-2022-49951 | known affected: 369 known not affected: 442 recommended: 166 | 2026-10-16T14:13:07+00:00 | Vulnerability · Source |
| CVE-2022-49956 | suse_vex | SUSE CVE CVE-2022-49956 | known affected: 0 known not affected: 325 recommended: 272 | 2026-10-16T14:13:04+00:00 | Vulnerability · Source |
| CVE-2022-49957 | suse_vex | SUSE CVE CVE-2022-49957 | known affected: 413 known not affected: 263 recommended: 229 | 2026-10-16T14:13:01+00:00 | Vulnerability · Source |
| CVE-2022-49958 | suse_vex | SUSE CVE CVE-2022-49958 | known affected: 387 known not affected: 344 recommended: 280 | 2026-10-16T14:12:58+00:00 | Vulnerability · Source |
| CVE-2022-49959 | suse_vex | SUSE CVE CVE-2022-49959 | known affected: 0 known not affected: 506 recommended: 74 | 2026-10-16T14:12:55+00:00 | Vulnerability · Source |
| CVE-2022-49961 | suse_vex | SUSE CVE CVE-2022-49961 | known affected: 171 known not affected: 335 recommended: 54 | 2026-10-16T14:12:53+00:00 | Vulnerability · Source |
| CVE-2022-49963 | suse_vex | SUSE CVE CVE-2022-49963 | known affected: 369 known not affected: 442 recommended: 92 | 2026-10-16T14:12:50+00:00 | Vulnerability · Source |
| CVE-2022-49964 | suse_vex | SUSE CVE CVE-2022-49964 | known affected: 348 known not affected: 382 recommended: 280 | 2026-10-16T14:12:48+00:00 | Vulnerability · Source |
| CVE-2022-49965 | suse_vex | SUSE CVE CVE-2022-49965 | known affected: 369 known not affected: 441 recommended: 166 | 2026-10-16T14:12:46+00:00 | Vulnerability · Source |
| CVE-2022-49970 | suse_vex | SUSE CVE CVE-2022-49970 | known affected: 0 known not affected: 506 recommended: 54 | 2026-10-16T14:12:44+00:00 | Vulnerability · Source |
| CVE-2022-49972 | suse_vex | SUSE CVE CVE-2022-49972 | known affected: 369 known not affected: 441 recommended: 92 | 2026-10-16T14:12:41+00:00 | Vulnerability · Source |
| CVE-2022-49974 | suse_vex | SUSE CVE CVE-2022-49974 | known affected: 0 known not affected: 506 recommended: 54 | 2026-10-16T14:12:39+00:00 | Vulnerability · Source |
| CVE-2022-49976 | suse_vex | SUSE CVE CVE-2022-49976 | known affected: 0 known not affected: 506 | 2026-10-16T14:12:37+00:00 | Vulnerability · Source |
| CVE-2022-49978 | suse_vex | SUSE CVE CVE-2022-49978 | known affected: 344 known not affected: 329 recommended: 296 | 2026-10-16T14:12:32+00:00 | Vulnerability · Source |
| CVE-2022-49979 | suse_vex | SUSE CVE CVE-2022-49979 | known affected: 552 known not affected: 327 recommended: 122 | 2026-10-16T14:12:30+00:00 | Vulnerability · Source |
| CVE-2022-49989 | suse_vex | SUSE CVE CVE-2022-49989 | known affected: 463 known not affected: 279 recommended: 273 | 2026-10-16T14:12:27+00:00 | Vulnerability · Source |
| CVE-2022-49990 | suse_vex | SUSE CVE CVE-2022-49990 | known affected: 465 known not affected: 221 recommended: 350 | 2026-10-16T14:12:25+00:00 | Vulnerability · Source |
| CVE-2022-49991 | suse_vex | SUSE CVE CVE-2022-49991 | known affected: 61 known not affected: 445 recommended: 54 | 2026-10-16T14:12:22+00:00 | Vulnerability · Source |
| CVE-2022-49992 | suse_vex | SUSE CVE CVE-2022-49992 | known affected: 0 known not affected: 506 recommended: 27 | 2026-10-16T14:12:20+00:00 | Vulnerability · Source |