VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
104648 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-49519 | suse_vex | SUSE CVE CVE-2022-49519 | known affected: 529 known not affected: 144 recommended: 337 | 2026-10-17T01:19:53+00:00 | Vulnerability · Source |
| CVE-2022-49521 | suse_vex | SUSE CVE CVE-2022-49521 | known affected: 487 known not affected: 154 recommended: 333 | 2026-10-17T01:19:51+00:00 | Vulnerability · Source |
| CVE-2022-49538 | suse_vex | SUSE CVE CVE-2022-49538 | known affected: 627 known not affected: 87 recommended: 182 | 2026-10-17T01:19:49+00:00 | Vulnerability · Source |
| CVE-2022-49595 | suse_vex | SUSE CVE CVE-2022-49595 | known affected: 0 known not affected: 147 recommended: 54 | 2026-10-17T01:19:47+00:00 | Vulnerability · Source |
| CVE-2022-49652 | suse_vex | SUSE CVE CVE-2022-49652 | known affected: 462 known not affected: 215 recommended: 316 | 2026-10-17T01:19:44+00:00 | Vulnerability · Source |
| CVE-2022-49664 | suse_vex | SUSE CVE CVE-2022-49664 | known affected: 61 known not affected: 401 recommended: 42 | 2026-10-17T01:19:42+00:00 | Vulnerability · Source |
| CVE-2022-49692 | suse_vex | SUSE CVE CVE-2022-49692 | known affected: 0 known not affected: 462 | 2026-10-17T01:19:41+00:00 | Vulnerability · Source |
| CVE-2022-49693 | suse_vex | SUSE CVE CVE-2022-49693 | known affected: 462 known not affected: 215 recommended: 319 | 2026-10-17T01:19:39+00:00 | Vulnerability · Source |
| CVE-2022-49696 | suse_vex | SUSE CVE CVE-2022-49696 | known affected: 61 known not affected: 401 | 2026-10-17T01:19:38+00:00 | Vulnerability · Source |
| CVE-2022-49713 | suse_vex | SUSE CVE CVE-2022-49713 | known affected: 334 known not affected: 310 recommended: 319 | 2026-10-17T01:19:36+00:00 | Vulnerability · Source |
| CVE-2022-49726 | suse_vex | SUSE CVE CVE-2022-49726 | known affected: 407 known not affected: 267 recommended: 297 | 2026-10-17T01:19:34+00:00 | Vulnerability · Source |
| CVE-2022-49730 | suse_vex | SUSE CVE CVE-2022-49730 | known affected: 433 known not affected: 243 recommended: 319 | 2026-10-17T01:19:33+00:00 | Vulnerability · Source |
| CVE-2022-49747 | suse_vex | SUSE CVE CVE-2022-49747 | known affected: 0 known not affected: 456 recommended: 86 | 2026-10-17T01:19:32+00:00 | Vulnerability · Source |
| CVE-2022-49767 | suse_vex | SUSE CVE CVE-2022-49767 | known affected: 377 known not affected: 324 recommended: 296 | 2026-10-17T01:19:30+00:00 | Vulnerability · Source |
| CVE-2022-49810 | suse_vex | SUSE CVE CVE-2022-49810 | known affected: 339 known not affected: 383 recommended: 214 | 2026-10-17T01:19:28+00:00 | Vulnerability · Source |
| CVE-2022-49842 | suse_vex | SUSE CVE CVE-2022-49842 | known affected: 494 known not affected: 141 recommended: 318 | 2026-10-17T01:19:26+00:00 | Vulnerability · Source |
| CVE-2022-49843 | suse_vex | SUSE CVE CVE-2022-49843 | known affected: 0 known not affected: 504 | 2026-10-17T01:19:25+00:00 | Vulnerability · Source |
| CVE-2022-49844 | suse_vex | SUSE CVE CVE-2022-49844 | known affected: 0 known not affected: 507 | 2026-10-17T01:19:23+00:00 | Vulnerability · Source |
| CVE-2022-49848 | suse_vex | SUSE CVE CVE-2022-49848 | known affected: 0 known not affected: 502 recommended: 54 | 2026-10-17T01:19:22+00:00 | Vulnerability · Source |
| CVE-2022-49891 | suse_vex | SUSE CVE CVE-2022-49891 | known affected: 339 known not affected: 381 recommended: 214 | 2026-10-17T01:19:20+00:00 | Vulnerability · Source |
| CVE-2022-49940 | suse_vex | SUSE CVE CVE-2022-49940 | known affected: 344 known not affected: 385 recommended: 284 | 2026-10-17T01:19:17+00:00 | Vulnerability · Source |
| CVE-2022-49945 | suse_vex | SUSE CVE CVE-2022-49945 | known affected: 491 known not affected: 236 recommended: 273 | 2026-10-17T01:19:16+00:00 | Vulnerability · Source |
| CVE-2022-49947 | suse_vex | SUSE CVE CVE-2022-49947 | known affected: 0 known not affected: 506 | 2026-10-17T01:19:14+00:00 | Vulnerability · Source |
| CVE-2022-49953 | suse_vex | SUSE CVE CVE-2022-49953 | known affected: 0 known not affected: 506 | 2026-10-17T01:19:13+00:00 | Vulnerability · Source |
| CVE-2022-49981 | suse_vex | SUSE CVE CVE-2022-49981 | known affected: 495 known not affected: 242 recommended: 364 | 2026-10-17T01:19:11+00:00 | Vulnerability · Source |
| CVE-2022-49986 | suse_vex | SUSE CVE CVE-2022-49986 | known affected: 404 known not affected: 263 recommended: 396 | 2026-10-17T01:19:10+00:00 | Vulnerability · Source |
| CVE-2022-49999 | suse_vex | SUSE CVE CVE-2022-49999 | known affected: 344 known not affected: 385 recommended: 206 | 2026-10-17T01:19:08+00:00 | Vulnerability · Source |
| CVE-2022-50007 | suse_vex | SUSE CVE CVE-2022-50007 | known affected: 676 known not affected: 234 recommended: 111 | 2026-10-17T01:19:06+00:00 | Vulnerability · Source |
| CVE-2022-50036 | suse_vex | SUSE CVE CVE-2022-50036 | known affected: 344 known not affected: 396 recommended: 273 | 2026-10-17T01:19:03+00:00 | Vulnerability · Source |
| CVE-2022-50048 | suse_vex | SUSE CVE CVE-2022-50048 | known affected: 61 known not affected: 445 recommended: 42 | 2026-10-17T01:19:01+00:00 | Vulnerability · Source |
| CVE-2022-50050 | suse_vex | SUSE CVE CVE-2022-50050 | known affected: 473 known not affected: 337 recommended: 166 | 2026-10-17T01:18:59+00:00 | Vulnerability · Source |
| CVE-2022-50073 | suse_vex | SUSE CVE CVE-2022-50073 | known affected: 344 known not affected: 331 recommended: 249 | 2026-10-17T01:18:58+00:00 | Vulnerability · Source |
| CVE-2022-50109 | suse_vex | SUSE CVE CVE-2022-50109 | known affected: 344 known not affected: 344 recommended: 296 | 2026-10-17T01:18:56+00:00 | Vulnerability · Source |
| CVE-2022-50113 | suse_vex | SUSE CVE CVE-2022-50113 | known affected: 0 known not affected: 506 recommended: 47 | 2026-10-17T01:18:54+00:00 | Vulnerability · Source |
| CVE-2022-50155 | suse_vex | SUSE CVE CVE-2022-50155 | known affected: 344 known not affected: 385 recommended: 206 | 2026-10-17T01:18:52+00:00 | Vulnerability · Source |
| CVE-2022-50161 | suse_vex | SUSE CVE CVE-2022-50161 | known affected: 463 known not affected: 277 recommended: 273 | 2026-10-17T01:18:50+00:00 | Vulnerability · Source |
| CVE-2022-50163 | suse_vex | SUSE CVE CVE-2022-50163 | known affected: 104 known not affected: 402 | 2026-10-17T01:18:49+00:00 | Vulnerability · Source |
| CVE-2022-50234 | suse_vex | SUSE CVE CVE-2022-50234 | known affected: 0 known not affected: 347 recommended: 264 | 2026-10-17T01:18:47+00:00 | Vulnerability · Source |
| CVE-2022-50263 | suse_vex | SUSE CVE CVE-2022-50263 | known affected: 0 known not affected: 520 recommended: 54 | 2026-10-17T01:18:45+00:00 | Vulnerability · Source |
| CVE-2022-50291 | suse_vex | SUSE CVE CVE-2022-50291 | known affected: 684 known not affected: 172 recommended: 23 | 2026-10-17T01:18:44+00:00 | Vulnerability · Source |
| CVE-2022-50362 | suse_vex | SUSE CVE CVE-2022-50362 | known affected: 344 known not affected: 392 recommended: 206 | 2026-10-17T01:18:42+00:00 | Vulnerability · Source |
| CVE-2022-50420 | suse_vex | SUSE CVE CVE-2022-50420 | known affected: 171 known not affected: 349 | 2026-10-17T01:18:40+00:00 | Vulnerability · Source |
| CVE-2022-50442 | suse_vex | SUSE CVE CVE-2022-50442 | known affected: 0 known not affected: 520 | 2026-10-17T01:18:38+00:00 | Vulnerability · Source |
| CVE-2022-50469 | suse_vex | SUSE CVE CVE-2022-50469 | known affected: 506 known not affected: 172 recommended: 206 | 2026-10-17T01:18:37+00:00 | Vulnerability · Source |
| CVE-2022-50471 | suse_vex | SUSE CVE CVE-2022-50471 | known affected: 556 known not affected: 167 recommended: 196 | 2026-10-17T01:18:35+00:00 | Vulnerability · Source |
| CVE-2022-50507 | suse_vex | SUSE CVE CVE-2022-50507 | known affected: 0 known not affected: 520 | 2026-10-17T01:18:34+00:00 | Vulnerability · Source |
| CVE-2022-50517 | suse_vex | SUSE CVE CVE-2022-50517 | known affected: 0 known not affected: 520 | 2026-10-17T01:18:32+00:00 | Vulnerability · Source |
| CVE-2022-50527 | suse_vex | SUSE CVE CVE-2022-50527 | known affected: 631 known not affected: 173 recommended: 188 | 2026-10-17T01:18:31+00:00 | Vulnerability · Source |
| CVE-2022-50529 | suse_vex | SUSE CVE CVE-2022-50529 | known affected: 516 known not affected: 230 recommended: 196 | 2026-10-17T01:18:29+00:00 | Vulnerability · Source |
| CVE-2023-0394 | suse_vex | SUSE CVE CVE-2023-0394 | known affected: 299 recommended: 1187 | 2026-10-17T01:18:25+00:00 | Vulnerability · Source |