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-49563 | suse_vex | SUSE CVE CVE-2022-49563 | known affected: 494 known not affected: 144 recommended: 370 | 2026-10-16T14:20:37+00:00 | Vulnerability · Source |
| CVE-2022-49564 | suse_vex | SUSE CVE CVE-2022-49564 | known affected: 494 known not affected: 144 recommended: 370 | 2026-10-16T14:20:34+00:00 | Vulnerability · Source |
| CVE-2022-49566 | suse_vex | SUSE CVE CVE-2022-49566 | known affected: 453 known not affected: 130 recommended: 333 | 2026-10-16T14:20:30+00:00 | Vulnerability · Source |
| CVE-2022-49567 | suse_vex | SUSE CVE CVE-2022-49567 | known affected: 388 known not affected: 72 recommended: 58 | 2026-10-16T14:20:27+00:00 | Vulnerability · Source |
| CVE-2022-49568 | suse_vex | SUSE CVE CVE-2022-49568 | known affected: 500 known not affected: 266 recommended: 223 | 2026-10-16T14:20:25+00:00 | Vulnerability · Source |
| CVE-2022-49569 | suse_vex | SUSE CVE CVE-2022-49569 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:20:22+00:00 | Vulnerability · Source |
| CVE-2022-49572 | suse_vex | SUSE CVE CVE-2022-49572 | known affected: 0 known not affected: 141 recommended: 54 | 2026-10-16T14:20:20+00:00 | Vulnerability · Source |
| CVE-2022-49574 | suse_vex | SUSE CVE CVE-2022-49574 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:20:18+00:00 | Vulnerability · Source |
| CVE-2022-49575 | suse_vex | SUSE CVE CVE-2022-49575 | known affected: 0 known not affected: 141 recommended: 54 | 2026-10-16T14:20:16+00:00 | Vulnerability · Source |
| CVE-2022-49578 | suse_vex | SUSE CVE CVE-2022-49578 | known affected: 698 known not affected: 108 recommended: 80 | 2026-10-16T14:20:14+00:00 | Vulnerability · Source |
| CVE-2022-49580 | suse_vex | SUSE CVE CVE-2022-49580 | known affected: 0 known not affected: 177 recommended: 54 | 2026-10-16T14:20:11+00:00 | Vulnerability · Source |
| CVE-2022-49581 | suse_vex | SUSE CVE CVE-2022-49581 | known affected: 539 known not affected: 138 recommended: 263 | 2026-10-16T14:20:09+00:00 | Vulnerability · Source |
| CVE-2022-49583 | suse_vex | SUSE CVE CVE-2022-49583 | known affected: 403 known not affected: 325 recommended: 297 | 2026-10-16T14:20:07+00:00 | Vulnerability · Source |
| CVE-2022-49584 | suse_vex | SUSE CVE CVE-2022-49584 | known affected: 530 known not affected: 150 recommended: 305 | 2026-10-16T14:20:04+00:00 | Vulnerability · Source |
| CVE-2022-49586 | suse_vex | SUSE CVE CVE-2022-49586 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:20:02+00:00 | Vulnerability · Source |
| CVE-2022-49587 | suse_vex | SUSE CVE CVE-2022-49587 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:20:00+00:00 | Vulnerability · Source |
| CVE-2022-49588 | suse_vex | SUSE CVE CVE-2022-49588 | known affected: 61 known not affected: 401 recommended: 54 | 2026-10-16T14:19:58+00:00 | Vulnerability · Source |
| CVE-2022-49591 | suse_vex | SUSE CVE CVE-2022-49591 | known affected: 334 known not affected: 394 recommended: 223 | 2026-10-16T14:19:56+00:00 | Vulnerability · Source |
| CVE-2022-49592 | suse_vex | SUSE CVE CVE-2022-49592 | known affected: 500 known not affected: 211 recommended: 320 | 2026-10-16T14:19:53+00:00 | Vulnerability · Source |
| CVE-2022-49593 | suse_vex | SUSE CVE CVE-2022-49593 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-16T14:19:51+00:00 | Vulnerability · Source |
| CVE-2022-49594 | suse_vex | SUSE CVE CVE-2022-49594 | known affected: 61 known not affected: 401 recommended: 54 | 2026-10-16T14:19:49+00:00 | Vulnerability · Source |
| CVE-2022-49596 | suse_vex | SUSE CVE CVE-2022-49596 | known affected: 0 known not affected: 141 recommended: 54 | 2026-10-16T14:19:47+00:00 | Vulnerability · Source |
| CVE-2022-49597 | suse_vex | SUSE CVE CVE-2022-49597 | known affected: 0 known not affected: 141 | 2026-10-16T14:19:44+00:00 | Vulnerability · Source |
| 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 |