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-49513 | suse_vex | SUSE CVE CVE-2022-49513 | known affected: 626 known not affected: 177 recommended: 100 | 2026-10-16T14:21:44+00:00 | Vulnerability · Source |
| CVE-2022-49514 | suse_vex | SUSE CVE CVE-2022-49514 | known affected: 457 known not affected: 275 recommended: 293 | 2026-10-16T14:21:42+00:00 | Vulnerability · Source |
| CVE-2022-49515 | suse_vex | SUSE CVE CVE-2022-49515 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:21:40+00:00 | Vulnerability · Source |
| CVE-2022-49516 | suse_vex | SUSE CVE CVE-2022-49516 | known affected: 468 known not affected: 242 recommended: 126 | 2026-10-16T14:21:37+00:00 | Vulnerability · Source |
| CVE-2022-49518 | suse_vex | SUSE CVE CVE-2022-49518 | known affected: 364 known not affected: 397 recommended: 100 | 2026-10-16T14:21:35+00:00 | Vulnerability · Source |
| CVE-2022-49522 | suse_vex | SUSE CVE CVE-2022-49522 | known affected: 393 known not affected: 299 recommended: 293 | 2026-10-16T14:21:33+00:00 | Vulnerability · Source |
| CVE-2022-49525 | suse_vex | SUSE CVE CVE-2022-49525 | known affected: 499 known not affected: 179 recommended: 333 | 2026-10-16T14:21:28+00:00 | Vulnerability · Source |
| CVE-2022-49526 | suse_vex | SUSE CVE CVE-2022-49526 | known affected: 422 known not affected: 220 recommended: 345 | 2026-10-16T14:21:26+00:00 | Vulnerability · Source |
| CVE-2022-49528 | suse_vex | SUSE CVE CVE-2022-49528 | known affected: 197 known not affected: 265 | 2026-10-16T14:21:23+00:00 | Vulnerability · Source |
| CVE-2022-49529 | suse_vex | SUSE CVE CVE-2022-49529 | known affected: 364 known not affected: 400 recommended: 100 | 2026-10-16T14:21:21+00:00 | Vulnerability · Source |
| CVE-2022-49530 | suse_vex | SUSE CVE CVE-2022-49530 | known affected: 592 known not affected: 117 recommended: 126 | 2026-10-16T14:21:18+00:00 | Vulnerability · Source |
| CVE-2022-49532 | suse_vex | SUSE CVE CVE-2022-49532 | known affected: 481 known not affected: 210 recommended: 333 | 2026-10-16T14:21:16+00:00 | Vulnerability · Source |
| CVE-2022-49533 | suse_vex | SUSE CVE CVE-2022-49533 | known affected: 425 known not affected: 341 recommended: 100 | 2026-10-16T14:21:14+00:00 | Vulnerability · Source |
| CVE-2022-49535 | suse_vex | SUSE CVE CVE-2022-49535 | known affected: 495 known not affected: 179 recommended: 319 | 2026-10-16T14:21:11+00:00 | Vulnerability · Source |
| CVE-2022-49537 | suse_vex | SUSE CVE CVE-2022-49537 | known affected: 372 known not affected: 274 recommended: 361 | 2026-10-16T14:21:09+00:00 | Vulnerability · Source |
| CVE-2022-49545 | suse_vex | SUSE CVE CVE-2022-49545 | known affected: 496 known not affected: 138 recommended: 424 | 2026-10-16T14:21:05+00:00 | Vulnerability · Source |
| CVE-2022-49546 | suse_vex | SUSE CVE CVE-2022-49546 | known affected: 489 known not affected: 153 recommended: 333 | 2026-10-16T14:21:02+00:00 | Vulnerability · Source |
| CVE-2022-49548 | suse_vex | SUSE CVE CVE-2022-49548 | known affected: 468 known not affected: 294 recommended: 154 | 2026-10-16T14:21:00+00:00 | Vulnerability · Source |
| CVE-2022-49549 | suse_vex | SUSE CVE CVE-2022-49549 | known affected: 334 known not affected: 397 recommended: 223 | 2026-10-16T14:20:57+00:00 | Vulnerability · Source |
| CVE-2022-49552 | suse_vex | SUSE CVE CVE-2022-49552 | known affected: 425 known not affected: 341 recommended: 154 | 2026-10-16T14:20:54+00:00 | Vulnerability · Source |
| CVE-2022-49553 | suse_vex | SUSE CVE CVE-2022-49553 | known affected: 0 known not affected: 462 | 2026-10-16T14:20:52+00:00 | Vulnerability · Source |
| CVE-2022-49554 | suse_vex | SUSE CVE CVE-2022-49554 | known affected: 130 known not affected: 332 | 2026-10-16T14:20:50+00:00 | Vulnerability · Source |
| CVE-2022-49557 | suse_vex | SUSE CVE CVE-2022-49557 | known affected: 0 known not affected: 462 recommended: 42 | 2026-10-16T14:20:47+00:00 | Vulnerability · Source |
| CVE-2022-49558 | suse_vex | SUSE CVE CVE-2022-49558 | known affected: 61 known not affected: 401 | 2026-10-16T14:20:45+00:00 | Vulnerability · Source |
| CVE-2022-49559 | suse_vex | SUSE CVE CVE-2022-49559 | known affected: 334 known not affected: 394 recommended: 265 | 2026-10-16T14:20:42+00:00 | Vulnerability · Source |
| CVE-2022-49561 | suse_vex | SUSE CVE CVE-2022-49561 | known affected: 621 known not affected: 209 recommended: 68 | 2026-10-16T14:20:39+00:00 | Vulnerability · Source |
| 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-49565 | suse_vex | SUSE CVE CVE-2022-49565 | known affected: 364 known not affected: 402 recommended: 154 | 2026-10-16T14:20:32+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 |