VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
103255 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2022-26495 | suse_vex | SUSE CVE CVE-2022-26495 | recommended: 13 | 2026-10-17T01:22:28+00:00 | Vulnerability · Source |
| CVE-2022-26710 | suse_vex | SUSE CVE CVE-2022-26710 | known affected: 25 recommended: 973 | 2026-10-17T01:22:26+00:00 | Vulnerability · Source |
| CVE-2022-26717 | suse_vex | SUSE CVE CVE-2022-26717 | known affected: 1 recommended: 1008 | 2026-10-17T01:22:25+00:00 | Vulnerability · Source |
| CVE-2022-27386 | suse_vex | SUSE CVE CVE-2022-27386 | known affected: 1 known not affected: 114 recommended: 514 | 2026-10-17T01:22:23+00:00 | Vulnerability · Source |
| CVE-2022-27405 | suse_vex | SUSE CVE CVE-2022-27405 | known affected: 237 known not affected: 130 recommended: 482 | 2026-10-17T01:22:22+00:00 | Vulnerability · Source |
| CVE-2022-27445 | suse_vex | SUSE CVE CVE-2022-27445 | known affected: 0 known not affected: 93 recommended: 514 | 2026-10-17T01:22:20+00:00 | Vulnerability · Source |
| CVE-2022-28734 | suse_vex | SUSE CVE CVE-2022-28734 | known affected: 353 recommended: 722 | 2026-10-17T01:22:18+00:00 | Vulnerability · Source |
| CVE-2022-30184 | suse_vex | SUSE CVE CVE-2022-30184 | recommended: 41 | 2026-10-17T01:22:16+00:00 | Vulnerability · Source |
| CVE-2022-30293 | suse_vex | SUSE CVE CVE-2022-30293 | known affected: 1 known not affected: 231 recommended: 1008 | 2026-10-17T01:22:14+00:00 | Vulnerability · Source |
| CVE-2022-30787 | suse_vex | SUSE CVE CVE-2022-30787 | recommended: 126 | 2026-10-17T01:22:13+00:00 | Vulnerability · Source |
| CVE-2022-31631 | suse_vex | SUSE CVE CVE-2022-31631 | recommended: 3373 | 2026-10-17T01:22:11+00:00 | Vulnerability · Source |
| CVE-2022-31745 | suse_vex | SUSE CVE CVE-2022-31745 | known affected: 0 known not affected: 1 recommended: 9 | 2026-10-17T01:22:09+00:00 | Vulnerability · Source |
| CVE-2022-32089 | suse_vex | SUSE CVE CVE-2022-32089 | known affected: 0 known not affected: 231 recommended: 410 | 2026-10-17T01:22:07+00:00 | Vulnerability · Source |
| CVE-2022-32912 | suse_vex | SUSE CVE CVE-2022-32912 | known affected: 1 recommended: 1021 | 2026-10-17T01:22:05+00:00 | Vulnerability · Source |
| CVE-2022-33070 | suse_vex | SUSE CVE CVE-2022-33070 | known affected: 0 known not affected: 113 recommended: 24 | 2026-10-17T01:22:04+00:00 | Vulnerability · Source |
| CVE-2022-34483 | suse_vex | SUSE CVE CVE-2022-34483 | known affected: 1 recommended: 363 | 2026-10-17T01:22:02+00:00 | Vulnerability · Source |
| CVE-2022-34485 | suse_vex | SUSE CVE CVE-2022-34485 | known affected: 1 recommended: 363 | 2026-10-17T01:22:01+00:00 | Vulnerability · Source |
| CVE-2022-37026 | suse_vex | SUSE CVE CVE-2022-37026 | recommended: 256 | 2026-10-17T01:21:57+00:00 | Vulnerability · Source |
| CVE-2022-37966 | suse_vex | SUSE CVE CVE-2022-37966 | known affected: 272 known not affected: 103 recommended: 2281 | 2026-10-17T01:21:55+00:00 | Vulnerability · Source |
| CVE-2022-38398 | suse_vex | SUSE CVE CVE-2022-38398 | recommended: 132 | 2026-10-17T01:21:54+00:00 | Vulnerability · Source |
| CVE-2022-39347 | suse_vex | SUSE CVE CVE-2022-39347 | recommended: 174 | 2026-10-17T01:21:50+00:00 | Vulnerability · Source |
| CVE-2022-40982 | suse_vex | SUSE CVE CVE-2022-40982 | known affected: 213 recommended: 1744 | 2026-10-17T01:21:48+00:00 | Vulnerability · Source |
| CVE-2022-42856 | suse_vex | SUSE CVE CVE-2022-42856 | known affected: 1 recommended: 863 | 2026-10-17T01:21:45+00:00 | Vulnerability · Source |
| CVE-2022-42867 | suse_vex | SUSE CVE CVE-2022-42867 | known affected: 1 recommended: 875 | 2026-10-17T01:21:44+00:00 | Vulnerability · Source |
| CVE-2022-44729 | suse_vex | SUSE CVE CVE-2022-44729 | known not affected: 43 recommended: 80 | 2026-10-17T01:21:42+00:00 | Vulnerability · Source |
| CVE-2022-45887 | suse_vex | SUSE CVE CVE-2022-45887 | known affected: 192 recommended: 1336 | 2026-10-17T01:21:40+00:00 | Vulnerability · Source |
| CVE-2022-46691 | suse_vex | SUSE CVE CVE-2022-46691 | known affected: 1 recommended: 875 | 2026-10-17T01:21:38+00:00 | Vulnerability · Source |
| CVE-2022-46692 | suse_vex | SUSE CVE CVE-2022-46692 | known affected: 1 recommended: 875 | 2026-10-17T01:21:37+00:00 | Vulnerability · Source |
| CVE-2022-46881 | suse_vex | SUSE CVE CVE-2022-46881 | known affected: 21 recommended: 371 | 2026-10-17T01:21:35+00:00 | Vulnerability · Source |
| CVE-2022-47695 | suse_vex | SUSE CVE CVE-2022-47695 | known affected: 394 known not affected: 69 recommended: 327 | 2026-10-17T01:21:34+00:00 | Vulnerability · Source |
| CVE-2022-47943 | suse_vex | SUSE CVE CVE-2022-47943 | known affected: 0 known not affected: 392 | 2026-10-17T01:21:32+00:00 | Vulnerability · Source |
| CVE-2022-48065 | suse_vex | SUSE CVE CVE-2022-48065 | known affected: 442 recommended: 327 | 2026-10-17T01:21:31+00:00 | Vulnerability · Source |
| CVE-2022-48468 | suse_vex | SUSE CVE CVE-2022-48468 | known affected: 15 recommended: 103 | 2026-10-17T01:21:30+00:00 | Vulnerability · Source |
| CVE-2022-48503 | suse_vex | SUSE CVE CVE-2022-48503 | known affected: 138 recommended: 761 | 2026-10-17T01:21:28+00:00 | Vulnerability · Source |
| CVE-2022-48566 | suse_vex | SUSE CVE CVE-2022-48566 | known affected: 570 known not affected: 304 recommended: 478 | 2026-10-17T01:21:27+00:00 | Vulnerability · Source |
| CVE-2022-48649 | suse_vex | SUSE CVE CVE-2022-48649 | known not affected: 343 | 2026-10-17T01:21:23+00:00 | Vulnerability · Source |
| CVE-2022-48686 | suse_vex | SUSE CVE CVE-2022-48686 | known affected: 297 known not affected: 186 recommended: 670 | 2026-10-17T01:21:19+00:00 | Vulnerability · Source |
| CVE-2022-48709 | suse_vex | SUSE CVE CVE-2022-48709 | known affected: 275 known not affected: 266 recommended: 452 | 2026-10-17T01:21:17+00:00 | Vulnerability · Source |
| CVE-2022-48716 | suse_vex | SUSE CVE CVE-2022-48716 | known affected: 397 known not affected: 294 recommended: 298 | 2026-10-17T01:21:16+00:00 | Vulnerability · Source |
| CVE-2022-48726 | suse_vex | SUSE CVE CVE-2022-48726 | known affected: 324 known not affected: 212 recommended: 482 | 2026-10-17T01:21:14+00:00 | Vulnerability · Source |
| CVE-2022-48737 | suse_vex | SUSE CVE CVE-2022-48737 | known affected: 324 known not affected: 59 recommended: 482 | 2026-10-17T01:21:11+00:00 | Vulnerability · Source |
| CVE-2022-48739 | suse_vex | SUSE CVE CVE-2022-48739 | known affected: 330 known not affected: 254 recommended: 391 | 2026-10-17T01:21:10+00:00 | Vulnerability · Source |
| CVE-2022-48765 | suse_vex | SUSE CVE CVE-2022-48765 | known affected: 330 known not affected: 254 recommended: 433 | 2026-10-17T01:21:08+00:00 | Vulnerability · Source |
| CVE-2022-48801 | suse_vex | SUSE CVE CVE-2022-48801 | known affected: 295 known not affected: 254 recommended: 426 | 2026-10-17T01:21:06+00:00 | Vulnerability · Source |
| CVE-2022-48819 | suse_vex | SUSE CVE CVE-2022-48819 | known not affected: 373 | 2026-10-17T01:21:05+00:00 | Vulnerability · Source |
| CVE-2022-48889 | suse_vex | SUSE CVE CVE-2022-48889 | known affected: 340 known not affected: 309 recommended: 288 | 2026-10-17T01:21:00+00:00 | Vulnerability · Source |
| CVE-2022-48901 | suse_vex | SUSE CVE CVE-2022-48901 | known affected: 410 known not affected: 289 recommended: 417 | 2026-10-17T01:20:58+00:00 | Vulnerability · Source |
| CVE-2022-48917 | suse_vex | SUSE CVE CVE-2022-48917 | known affected: 310 known not affected: 246 recommended: 496 | 2026-10-17T01:20:55+00:00 | Vulnerability · Source |
| CVE-2022-48923 | suse_vex | SUSE CVE CVE-2022-48923 | known affected: 314 known not affected: 271 recommended: 445 | 2026-10-17T01:20:53+00:00 | Vulnerability · Source |
| CVE-2022-48981 | suse_vex | SUSE CVE CVE-2022-48981 | known affected: 367 known not affected: 371 recommended: 394 | 2026-10-17T01:20:50+00:00 | Vulnerability · Source |