VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
283915 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49482 | suse_vex | SUSE CVE CVE-2022-49482 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:13:23+00:00 | Vulnerability · Source |
| CVE-2022-49489 | suse_vex | SUSE CVE CVE-2022-49489 | known affected: 377 known not affected: 239 recommended: 319 | 2026-07-25T17:13:21+00:00 | Vulnerability · Source |
| CVE-2022-49490 | suse_vex | SUSE CVE CVE-2022-49490 | known affected: 377 known not affected: 201 recommended: 319 | 2026-07-25T17:13:20+00:00 | Vulnerability · Source |
| CVE-2022-49494 | suse_vex | SUSE CVE CVE-2022-49494 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:18+00:00 | Vulnerability · Source |
| CVE-2022-49497 | suse_vex | SUSE CVE CVE-2022-49497 | known affected: 545 known not affected: 91 recommended: 140 | 2026-07-25T17:13:17+00:00 | Vulnerability · Source |
| CVE-2022-49498 | suse_vex | SUSE CVE CVE-2022-49498 | known affected: 334 known not affected: 270 recommended: 293 | 2026-07-25T17:13:16+00:00 | Vulnerability · Source |
| CVE-2022-49513 | suse_vex | SUSE CVE CVE-2022-49513 | known affected: 559 known not affected: 163 recommended: 73 | 2026-07-25T17:13:14+00:00 | Vulnerability · Source |
| CVE-2022-49517 | suse_vex | SUSE CVE CVE-2022-49517 | known affected: 385 known not affected: 257 recommended: 293 | 2026-07-25T17:13:12+00:00 | Vulnerability · Source |
| CVE-2022-49519 | suse_vex | SUSE CVE CVE-2022-49519 | known affected: 454 known not affected: 148 recommended: 310 | 2026-07-25T17:13:11+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-49523 | suse_vex | SUSE CVE CVE-2022-49523 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:13:08+00:00 | Vulnerability · Source |
| CVE-2022-49524 | suse_vex | SUSE CVE CVE-2022-49524 | known affected: 403 known not affected: 173 recommended: 319 | 2026-07-25T17:13:06+00:00 | Vulnerability · Source |
| CVE-2022-49542 | suse_vex | SUSE CVE CVE-2022-49542 | known affected: 360 known not affected: 256 recommended: 319 | 2026-07-25T17:13:04+00:00 | Vulnerability · Source |
| CVE-2022-49545 | suse_vex | SUSE CVE CVE-2022-49545 | known affected: 426 known not affected: 142 recommended: 424 | 2026-07-25T17:13:03+00:00 | Vulnerability · Source |
| CVE-2022-49548 | suse_vex | SUSE CVE CVE-2022-49548 | known affected: 456 known not affected: 210 recommended: 127 | 2026-07-25T17:13:01+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-49562 | suse_vex | SUSE CVE CVE-2022-49562 | known affected: 385 known not affected: 247 recommended: 250 | 2026-07-25T17:12:57+00:00 | Vulnerability · Source |
| CVE-2022-49564 | suse_vex | SUSE CVE CVE-2022-49564 | known affected: 424 known not affected: 148 recommended: 370 | 2026-07-25T17:12:55+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-49568 | suse_vex | SUSE CVE CVE-2022-49568 | known affected: 436 known not affected: 234 recommended: 223 | 2026-07-25T17:12:52+00:00 | Vulnerability · Source |
| CVE-2022-49570 | suse_vex | SUSE CVE CVE-2022-49570 | known affected: 334 known not affected: 298 recommended: 223 | 2026-07-25T17:12:51+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-49579 | suse_vex | SUSE CVE CVE-2022-49579 | known affected: 334 known not affected: 200 recommended: 250 | 2026-07-25T17:12:47+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-49589 | suse_vex | SUSE CVE CVE-2022-49589 | known affected: 573 known not affected: 147 recommended: 67 | 2026-07-25T17:12:41+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-49592 | suse_vex | SUSE CVE CVE-2022-49592 | known affected: 436 known not affected: 208 recommended: 293 | 2026-07-25T17:12:38+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-49607 | suse_vex | SUSE CVE CVE-2022-49607 | known affected: 458 known not affected: 148 recommended: 263 | 2026-07-25T17:12:31+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-49611 | suse_vex | SUSE CVE CVE-2022-49611 | known not affected: 238 recommended: 305 | 2026-07-25T17:12:28+00:00 | Vulnerability · Source |
| CVE-2022-49619 | suse_vex | SUSE CVE CVE-2022-49619 | known affected: 588 known not affected: 134 recommended: 26 | 2026-07-25T17:12:27+00:00 | Vulnerability · Source |
| CVE-2022-49623 | suse_vex | SUSE CVE CVE-2022-49623 | known affected: 395 known not affected: 344 recommended: 360 | 2026-07-25T17:12:25+00:00 | Vulnerability · Source |
| CVE-2022-49626 | suse_vex | SUSE CVE CVE-2022-49626 | known affected: 458 known not affected: 148 recommended: 305 | 2026-07-25T17:12:24+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-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 |