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-49598 | suse_vex | SUSE CVE CVE-2022-49598 | known affected: 0 known not affected: 141 recommended: 54 | 2026-10-16T14:19:42+00:00 | Vulnerability · Source |
| CVE-2022-49599 | suse_vex | SUSE CVE CVE-2022-49599 | known affected: 0 known not affected: 177 recommended: 54 | 2026-10-16T14:19:40+00:00 | Vulnerability · Source |
| CVE-2022-49602 | suse_vex | SUSE CVE CVE-2022-49602 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:19:38+00:00 | Vulnerability · Source |
| CVE-2022-49603 | suse_vex | SUSE CVE CVE-2022-49603 | known affected: 403 known not affected: 325 recommended: 277 | 2026-10-16T14:19:35+00:00 | Vulnerability · Source |
| CVE-2022-49604 | suse_vex | SUSE CVE CVE-2022-49604 | known affected: 394 known not affected: 80 recommended: 237 | 2026-10-16T14:19:33+00:00 | Vulnerability · Source |
| CVE-2022-49609 | suse_vex | SUSE CVE CVE-2022-49609 | known affected: 457 known not affected: 275 recommended: 293 | 2026-10-16T14:19:31+00:00 | Vulnerability · Source |
| CVE-2022-49611 | suse_vex | SUSE CVE CVE-2022-49611 | known affected: 0 known not affected: 305 recommended: 305 | 2026-10-16T14:19:29+00:00 | Vulnerability · Source |
| CVE-2022-49613 | suse_vex | SUSE CVE CVE-2022-49613 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:19:26+00:00 | Vulnerability · Source |
| CVE-2022-49615 | suse_vex | SUSE CVE CVE-2022-49615 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:19:24+00:00 | Vulnerability · Source |
| CVE-2022-49616 | suse_vex | SUSE CVE CVE-2022-49616 | known affected: 377 known not affected: 351 recommended: 243 | 2026-10-16T14:19:21+00:00 | Vulnerability · Source |
| CVE-2022-49619 | suse_vex | SUSE CVE CVE-2022-49619 | known affected: 635 known not affected: 168 recommended: 26 | 2026-10-16T14:19:19+00:00 | Vulnerability · Source |
| CVE-2022-49622 | suse_vex | SUSE CVE CVE-2022-49622 | known affected: 713 known not affected: 140 recommended: 23 | 2026-10-16T14:19:17+00:00 | Vulnerability · Source |
| CVE-2022-49623 | suse_vex | SUSE CVE CVE-2022-49623 | known affected: 453 known not affected: 378 recommended: 360 | 2026-10-16T14:19:14+00:00 | Vulnerability · Source |
| CVE-2022-49625 | suse_vex | SUSE CVE CVE-2022-49625 | known affected: 536 known not affected: 144 recommended: 302 | 2026-10-16T14:19:12+00:00 | Vulnerability · Source |
| CVE-2022-49629 | suse_vex | SUSE CVE CVE-2022-49629 | known affected: 171 known not affected: 291 recommended: 54 | 2026-10-16T14:19:10+00:00 | Vulnerability · Source |
| CVE-2022-49630 | suse_vex | SUSE CVE CVE-2022-49630 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:19:08+00:00 | Vulnerability · Source |
| CVE-2022-49632 | suse_vex | SUSE CVE CVE-2022-49632 | known affected: 0 known not affected: 141 recommended: 54 | 2026-10-16T14:19:06+00:00 | Vulnerability · Source |
| CVE-2022-49633 | suse_vex | SUSE CVE CVE-2022-49633 | known affected: 128 known not affected: 334 | 2026-10-16T14:19:03+00:00 | Vulnerability · Source |
| CVE-2022-49634 | suse_vex | SUSE CVE CVE-2022-49634 | known affected: 334 known not affected: 397 recommended: 277 | 2026-10-16T14:19:01+00:00 | Vulnerability · Source |
| CVE-2022-49635 | suse_vex | SUSE CVE CVE-2022-49635 | known affected: 596 known not affected: 149 recommended: 123 | 2026-10-16T14:18:58+00:00 | Vulnerability · Source |
| CVE-2022-49637 | suse_vex | SUSE CVE CVE-2022-49637 | known affected: 197 known not affected: 265 recommended: 54 | 2026-10-16T14:18:56+00:00 | Vulnerability · Source |
| CVE-2022-49638 | suse_vex | SUSE CVE CVE-2022-49638 | known affected: 0 known not affected: 99 recommended: 150 | 2026-10-16T14:18:53+00:00 | Vulnerability · Source |
| CVE-2022-49639 | suse_vex | SUSE CVE CVE-2022-49639 | known affected: 0 known not affected: 25 recommended: 74 | 2026-10-16T14:18:51+00:00 | Vulnerability · Source |
| CVE-2022-49640 | suse_vex | SUSE CVE CVE-2022-49640 | known affected: 465 known not affected: 181 recommended: 333 | 2026-10-16T14:18:48+00:00 | Vulnerability · Source |
| CVE-2022-49645 | suse_vex | SUSE CVE CVE-2022-49645 | known affected: 334 known not affected: 364 recommended: 293 | 2026-10-16T14:18:45+00:00 | Vulnerability · Source |
| CVE-2022-49646 | suse_vex | SUSE CVE CVE-2022-49646 | known affected: 360 known not affected: 336 recommended: 367 | 2026-10-16T14:18:42+00:00 | Vulnerability · Source |
| CVE-2022-49647 | suse_vex | SUSE CVE CVE-2022-49647 | known affected: 481 known not affected: 210 recommended: 407 | 2026-10-16T14:18:39+00:00 | Vulnerability · Source |
| CVE-2022-49650 | suse_vex | SUSE CVE CVE-2022-49650 | known affected: 334 known not affected: 350 recommended: 222 | 2026-10-16T14:18:37+00:00 | Vulnerability · Source |
| CVE-2022-49651 | suse_vex | SUSE CVE CVE-2022-49651 | known affected: 0 known not affected: 297 recommended: 54 | 2026-10-16T14:18:35+00:00 | Vulnerability · Source |
| CVE-2022-49654 | suse_vex | SUSE CVE CVE-2022-49654 | known affected: 61 known not affected: 401 | 2026-10-16T14:18:33+00:00 | Vulnerability · Source |
| CVE-2022-49655 | suse_vex | SUSE CVE CVE-2022-49655 | known affected: 364 known not affected: 398 recommended: 154 | 2026-10-16T14:18:30+00:00 | Vulnerability · Source |
| CVE-2022-49656 | suse_vex | SUSE CVE CVE-2022-49656 | known affected: 403 known not affected: 325 recommended: 223 | 2026-10-16T14:18:28+00:00 | Vulnerability · Source |
| CVE-2022-49657 | suse_vex | SUSE CVE CVE-2022-49657 | known affected: 481 known not affected: 165 recommended: 374 | 2026-10-16T14:18:25+00:00 | Vulnerability · Source |
| CVE-2022-49659 | suse_vex | SUSE CVE CVE-2022-49659 | known affected: 61 known not affected: 401 recommended: 54 | 2026-10-16T14:18:23+00:00 | Vulnerability · Source |
| CVE-2022-49660 | suse_vex | SUSE CVE CVE-2022-49660 | No product status | 2026-10-16T14:18:20+00:00 | Vulnerability · Source |
| CVE-2022-49661 | suse_vex | SUSE CVE CVE-2022-49661 | known affected: 493 known not affected: 153 recommended: 333 | 2026-10-16T14:18:17+00:00 | Vulnerability · Source |
| CVE-2022-49662 | suse_vex | SUSE CVE CVE-2022-49662 | known affected: 61 known not affected: 401 | 2026-10-16T14:18:15+00:00 | Vulnerability · Source |
| CVE-2022-49665 | suse_vex | SUSE CVE CVE-2022-49665 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:18:13+00:00 | Vulnerability · Source |
| CVE-2022-49666 | suse_vex | SUSE CVE CVE-2022-49666 | known affected: 0 known not affected: 462 recommended: 54 | 2026-10-16T14:18:11+00:00 | Vulnerability · Source |
| CVE-2022-49670 | suse_vex | SUSE CVE CVE-2022-49670 | known affected: 420 known not affected: 276 recommended: 334 | 2026-10-16T14:18:09+00:00 | Vulnerability · Source |
| CVE-2022-49672 | suse_vex | SUSE CVE CVE-2022-49672 | known affected: 448 known not affected: 234 recommended: 290 | 2026-10-16T14:18:07+00:00 | Vulnerability · Source |
| CVE-2022-49673 | suse_vex | SUSE CVE CVE-2022-49673 | known affected: 487 known not affected: 158 recommended: 375 | 2026-10-16T14:18:04+00:00 | Vulnerability · Source |
| CVE-2022-49674 | suse_vex | SUSE CVE CVE-2022-49674 | known affected: 453 known not affected: 418 recommended: 353 | 2026-10-16T14:18:02+00:00 | Vulnerability · Source |
| CVE-2022-49676 | suse_vex | SUSE CVE CVE-2022-49676 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:18:00+00:00 | Vulnerability · Source |
| CVE-2022-49677 | suse_vex | SUSE CVE CVE-2022-49677 | known affected: 528 known not affected: 238 recommended: 223 | 2026-10-16T14:17:58+00:00 | Vulnerability · Source |
| CVE-2022-49682 | suse_vex | SUSE CVE CVE-2022-49682 | known affected: 0 known not affected: 462 | 2026-10-16T14:17:53+00:00 | Vulnerability · Source |
| CVE-2022-49683 | suse_vex | SUSE CVE CVE-2022-49683 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:17:51+00:00 | Vulnerability · Source |
| CVE-2022-49684 | suse_vex | SUSE CVE CVE-2022-49684 | known affected: 0 known not affected: 462 | 2026-10-16T14:17:48+00:00 | Vulnerability · Source |
| CVE-2022-49685 | suse_vex | SUSE CVE CVE-2022-49685 | known affected: 429 known not affected: 302 recommended: 293 | 2026-10-16T14:17:45+00:00 | Vulnerability · Source |
| CVE-2022-49690 | suse_vex | SUSE CVE CVE-2022-49690 | No product status | 2026-10-16T14:17:43+00:00 | Vulnerability · Source |