VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283924 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-49635 | suse_vex | SUSE CVE CVE-2022-49635 | known affected: 529 known not affected: 149 recommended: 123 | 2026-07-25T17:12:20+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-49640 | suse_vex | SUSE CVE CVE-2022-49640 | known affected: 407 known not affected: 171 recommended: 333 | 2026-07-25T17:12:15+00:00 | Vulnerability · Source |
| CVE-2022-49650 | suse_vex | SUSE CVE CVE-2022-49650 | known affected: 334 known not affected: 257 recommended: 222 | 2026-07-25T17:12:14+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-49665 | suse_vex | SUSE CVE CVE-2022-49665 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:12:06+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-49673 | suse_vex | SUSE CVE CVE-2022-49673 | known affected: 415 known not affected: 163 recommended: 375 | 2026-07-25T17:12:03+00:00 | Vulnerability · Source |
| CVE-2022-49678 | suse_vex | SUSE CVE CVE-2022-49678 | known affected: 348 known not affected: 256 recommended: 293 | 2026-07-25T17:12:02+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-49703 | suse_vex | SUSE CVE CVE-2022-49703 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:11:50+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-49707 | suse_vex | SUSE CVE CVE-2022-49707 | known affected: 381 known not affected: 358 recommended: 387 | 2026-07-25T17:11:47+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-49710 | suse_vex | SUSE CVE CVE-2022-49710 | known affected: 415 known not affected: 163 recommended: 375 | 2026-07-25T17:11:44+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-49719 | suse_vex | SUSE CVE CVE-2022-49719 | known affected: 422 known not affected: 248 recommended: 223 | 2026-07-25T17:11:37+00:00 | Vulnerability · Source |
| CVE-2022-49727 | suse_vex | SUSE CVE CVE-2022-49727 | known affected: 632 known not affected: 88 recommended: 40 | 2026-07-25T17:11:36+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-49740 | suse_vex | SUSE CVE CVE-2022-49740 | known affected: 394 known not affected: 322 recommended: 26 | 2026-07-25T17:11:32+00:00 | Vulnerability · Source |
| CVE-2022-49745 | suse_vex | SUSE CVE CVE-2022-49745 | known affected: 369 known not affected: 294 recommended: 95 | 2026-07-25T17:11:31+00:00 | Vulnerability · Source |
| CVE-2022-49746 | suse_vex | SUSE CVE CVE-2022-49746 | known affected: 385 known not affected: 198 recommended: 251 | 2026-07-25T17:11:29+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-49761 | suse_vex | SUSE CVE CVE-2022-49761 | known affected: 506 known not affected: 204 recommended: 37 | 2026-07-25T17:11:26+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-49771 | suse_vex | SUSE CVE CVE-2022-49771 | known affected: 404 known not affected: 173 recommended: 318 | 2026-07-25T17:11:23+00:00 | Vulnerability · Source |
| CVE-2022-49773 | suse_vex | SUSE CVE CVE-2022-49773 | known affected: 369 known not affected: 343 recommended: 141 | 2026-07-25T17:11:22+00:00 | Vulnerability · Source |
| CVE-2022-49776 | suse_vex | SUSE CVE CVE-2022-49776 | known affected: 441 known not affected: 164 recommended: 251 | 2026-07-25T17:11:21+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-49788 | suse_vex | SUSE CVE CVE-2022-49788 | known affected: 418 known not affected: 174 recommended: 394 | 2026-07-25T17:11:18+00:00 | Vulnerability · Source |
| CVE-2022-49789 | suse_vex | SUSE CVE CVE-2022-49789 | known affected: 351 known not affected: 226 recommended: 316 | 2026-07-25T17:11:16+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-49795 | suse_vex | SUSE CVE CVE-2022-49795 | known affected: 369 known not affected: 343 recommended: 121 | 2026-07-25T17:11:13+00:00 | Vulnerability · Source |
| CVE-2022-49797 | suse_vex | SUSE CVE CVE-2022-49797 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-25T17:11:12+00:00 | Vulnerability · Source |
| CVE-2022-49800 | suse_vex | SUSE CVE CVE-2022-49800 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-25T17:11:10+00:00 | Vulnerability · Source |
| CVE-2022-49801 | suse_vex | SUSE CVE CVE-2022-49801 | known affected: 339 known not affected: 294 recommended: 214 | 2026-07-25T17:11:09+00:00 | Vulnerability · Source |