VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292114 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49456 | suse_vex | SUSE CVE CVE-2022-49456 | known not affected: 352 | 2026-07-25T17:13:38+00:00 | Vulnerability · Source |
| CVE-2022-49457 | suse_vex | SUSE CVE CVE-2022-49457 | known not affected: 348 | 2026-07-25T17:13:37+00:00 | Vulnerability · Source |
| CVE-2022-49468 | suse_vex | SUSE CVE CVE-2022-49468 | known affected: 385 known not affected: 247 recommended: 223 | 2026-07-25T17:13:32+00:00 | Vulnerability · Source |
| CVE-2022-49475 | suse_vex | SUSE CVE CVE-2022-49475 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:13:27+00:00 | Vulnerability · Source |
| CVE-2022-49522 | suse_vex | SUSE CVE CVE-2022-49522 | known affected: 365 known not affected: 235 recommended: 293 | 2026-07-25T17:13:09+00:00 | Vulnerability · Source |
| CVE-2022-49553 | suse_vex | SUSE CVE CVE-2022-49553 | known not affected: 352 | 2026-07-25T17:13:00+00:00 | Vulnerability · Source |
| CVE-2022-49561 | suse_vex | SUSE CVE CVE-2022-49561 | known affected: 551 known not affected: 199 recommended: 68 | 2026-07-25T17:12:58+00:00 | Vulnerability · Source |
| CVE-2022-49566 | suse_vex | SUSE CVE CVE-2022-49566 | known affected: 395 known not affected: 128 recommended: 333 | 2026-07-25T17:12:54+00:00 | Vulnerability · Source |
| CVE-2022-49576 | suse_vex | SUSE CVE CVE-2022-49576 | known affected: 55 known not affected: 297 | 2026-07-25T17:12:50+00:00 | Vulnerability · Source |
| CVE-2022-49578 | suse_vex | SUSE CVE CVE-2022-49578 | known affected: 618 known not affected: 104 recommended: 53 | 2026-07-25T17:12:48+00:00 | Vulnerability · Source |
| CVE-2022-49584 | suse_vex | SUSE CVE CVE-2022-49584 | known affected: 452 known not affected: 154 recommended: 305 | 2026-07-25T17:12:45+00:00 | Vulnerability · Source |
| CVE-2022-49586 | suse_vex | SUSE CVE CVE-2022-49586 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:44+00:00 | Vulnerability · Source |
| CVE-2022-49587 | suse_vex | SUSE CVE CVE-2022-49587 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:42+00:00 | Vulnerability · Source |
| CVE-2022-49590 | suse_vex | SUSE CVE CVE-2022-49590 | known affected: 632 known not affected: 124 recommended: 67 | 2026-07-25T17:12:39+00:00 | Vulnerability · Source |
| CVE-2022-49596 | suse_vex | SUSE CVE CVE-2022-49596 | known not affected: 141 recommended: 27 | 2026-07-25T17:12:37+00:00 | Vulnerability · Source |
| CVE-2022-49598 | suse_vex | SUSE CVE CVE-2022-49598 | known not affected: 141 recommended: 27 | 2026-07-25T17:12:35+00:00 | Vulnerability · Source |
| CVE-2022-49601 | suse_vex | SUSE CVE CVE-2022-49601 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:34+00:00 | Vulnerability · Source |
| CVE-2022-49602 | suse_vex | SUSE CVE CVE-2022-49602 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:32+00:00 | Vulnerability · Source |
| CVE-2022-49608 | suse_vex | SUSE CVE CVE-2022-49608 | known affected: 106 known not affected: 246 | 2026-07-25T17:12:30+00:00 | Vulnerability · Source |
| CVE-2022-49629 | suse_vex | SUSE CVE CVE-2022-49629 | known affected: 149 known not affected: 203 recommended: 27 | 2026-07-25T17:12:22+00:00 | Vulnerability · Source |
| CVE-2022-49630 | suse_vex | SUSE CVE CVE-2022-49630 | known not affected: 147 recommended: 27 | 2026-07-25T17:12:21+00:00 | Vulnerability · Source |
| CVE-2022-49636 | suse_vex | SUSE CVE CVE-2022-49636 | known not affected: 352 recommended: 47 | 2026-07-25T17:12:18+00:00 | Vulnerability · Source |
| CVE-2022-49639 | suse_vex | SUSE CVE CVE-2022-49639 | known not affected: 30 recommended: 47 | 2026-07-25T17:12:17+00:00 | Vulnerability · Source |
| CVE-2022-49654 | suse_vex | SUSE CVE CVE-2022-49654 | known affected: 55 known not affected: 297 | 2026-07-25T17:12:12+00:00 | Vulnerability · Source |
| CVE-2022-49659 | suse_vex | SUSE CVE CVE-2022-49659 | known affected: 55 known not affected: 297 recommended: 27 | 2026-07-25T17:12:11+00:00 | Vulnerability · Source |
| CVE-2022-49662 | suse_vex | SUSE CVE CVE-2022-49662 | known affected: 55 known not affected: 297 | 2026-07-25T17:12:09+00:00 | Vulnerability · Source |
| CVE-2022-49664 | suse_vex | SUSE CVE CVE-2022-49664 | known affected: 55 known not affected: 297 recommended: 42 | 2026-07-25T17:12:08+00:00 | Vulnerability · Source |
| CVE-2022-49666 | suse_vex | SUSE CVE CVE-2022-49666 | known not affected: 352 recommended: 27 | 2026-07-25T17:12:05+00:00 | Vulnerability · Source |
| CVE-2022-49680 | suse_vex | SUSE CVE CVE-2022-49680 | known affected: 450 known not affected: 220 recommended: 223 | 2026-07-25T17:12:00+00:00 | Vulnerability · Source |
| CVE-2022-49684 | suse_vex | SUSE CVE CVE-2022-49684 | known not affected: 352 | 2026-07-25T17:11:59+00:00 | Vulnerability · Source |
| CVE-2022-49685 | suse_vex | SUSE CVE CVE-2022-49685 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:11:56+00:00 | Vulnerability · Source |
| CVE-2022-49692 | suse_vex | SUSE CVE CVE-2022-49692 | known not affected: 352 | 2026-07-25T17:11:55+00:00 | Vulnerability · Source |
| CVE-2022-49693 | suse_vex | SUSE CVE CVE-2022-49693 | known affected: 407 known not affected: 209 recommended: 319 | 2026-07-25T17:11:53+00:00 | Vulnerability · Source |
| CVE-2022-49702 | suse_vex | SUSE CVE CVE-2022-49702 | known affected: 55 known not affected: 297 | 2026-07-25T17:11:52+00:00 | Vulnerability · Source |
| CVE-2022-49704 | suse_vex | SUSE CVE CVE-2022-49704 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:11:49+00:00 | Vulnerability · Source |
| CVE-2022-49709 | suse_vex | SUSE CVE CVE-2022-49709 | known affected: 55 known not affected: 297 | 2026-07-25T17:11:46+00:00 | Vulnerability · Source |
| CVE-2022-49712 | suse_vex | SUSE CVE CVE-2022-49712 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:11:43+00:00 | Vulnerability · Source |
| CVE-2022-49714 | suse_vex | SUSE CVE CVE-2022-49714 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:11:41+00:00 | Vulnerability · Source |
| CVE-2022-49717 | suse_vex | SUSE CVE CVE-2022-49717 | known not affected: 352 | 2026-07-25T17:11:40+00:00 | Vulnerability · Source |
| CVE-2022-49718 | suse_vex | SUSE CVE CVE-2022-49718 | known not affected: 352 | 2026-07-25T17:11:39+00:00 | Vulnerability · Source |
| CVE-2022-49737 | suse_vex | SUSE CVE CVE-2022-49737 | known affected: 414 known not affected: 80 recommended: 51 | 2026-07-25T17:11:34+00:00 | Vulnerability · Source |
| CVE-2022-49750 | suse_vex | SUSE CVE CVE-2022-49750 | known not affected: 344 recommended: 29 | 2026-07-25T17:11:28+00:00 | Vulnerability · Source |
| CVE-2022-49766 | suse_vex | SUSE CVE CVE-2022-49766 | known affected: 10 known not affected: 135 | 2026-07-25T17:11:25+00:00 | Vulnerability · Source |
| CVE-2022-49781 | suse_vex | SUSE CVE CVE-2022-49781 | known affected: 369 known not affected: 343 recommended: 92 | 2026-07-25T17:11:19+00:00 | Vulnerability · Source |
| CVE-2022-49791 | suse_vex | SUSE CVE CVE-2022-49791 | known affected: 57 known not affected: 349 | 2026-07-25T17:11:15+00:00 | Vulnerability · Source |
| CVE-2022-49812 | suse_vex | SUSE CVE CVE-2022-49812 | known affected: 390 known not affected: 248 recommended: 214 | 2026-07-25T17:11:06+00:00 | Vulnerability · Source |
| CVE-2022-49817 | suse_vex | SUSE CVE CVE-2022-49817 | known affected: 112 known not affected: 285 | 2026-07-25T17:11:04+00:00 | Vulnerability · Source |
| CVE-2022-49831 | suse_vex | SUSE CVE CVE-2022-49831 | known affected: 210 known not affected: 157 | 2026-07-25T17:11:00+00:00 | Vulnerability · Source |
| CVE-2022-49832 | suse_vex | SUSE CVE CVE-2022-49832 | known affected: 418 known not affected: 161 recommended: 304 | 2026-07-25T17:10:59+00:00 | Vulnerability · Source |
| CVE-2022-49833 | suse_vex | SUSE CVE CVE-2022-49833 | known affected: 245 known not affected: 135 | 2026-07-25T17:10:57+00:00 | Vulnerability · Source |