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-3112 | suse_vex | SUSE CVE CVE-2022-3112 | known affected: 272 known not affected: 199 recommended: 851 | 2026-10-17T01:23:06+00:00 | Vulnerability · Source |
| CVE-2022-3134 | suse_vex | SUSE CVE CVE-2022-3134 | known affected: 259 known not affected: 2 recommended: 487 | 2026-10-17T01:23:04+00:00 | Vulnerability · Source |
| CVE-2022-3570 | suse_vex | SUSE CVE CVE-2022-3570 | known affected: 426 known not affected: 1 recommended: 238 | 2026-10-17T01:23:02+00:00 | Vulnerability · Source |
| CVE-2022-4883 | suse_vex | SUSE CVE CVE-2022-4883 | known affected: 395 recommended: 174 | 2026-10-17T01:22:59+00:00 | Vulnerability · Source |
| CVE-2022-20770 | suse_vex | SUSE CVE CVE-2022-20770 | known affected: 59 recommended: 186 | 2026-10-17T01:22:58+00:00 | Vulnerability · Source |
| CVE-2022-21427 | suse_vex | SUSE CVE CVE-2022-21427 | recommended: 418 | 2026-10-17T01:22:56+00:00 | Vulnerability · Source |
| CVE-2022-22637 | suse_vex | SUSE CVE CVE-2022-22637 | known affected: 24 known not affected: 403 recommended: 930 | 2026-10-17T01:22:54+00:00 | Vulnerability · Source |
| CVE-2022-22662 | suse_vex | SUSE CVE CVE-2022-22662 | known affected: 25 recommended: 973 | 2026-10-17T01:22:52+00:00 | Vulnerability · Source |
| CVE-2022-22739 | suse_vex | SUSE CVE CVE-2022-22739 | recommended: 413 | 2026-10-17T01:22:51+00:00 | Vulnerability · Source |
| CVE-2022-22751 | suse_vex | SUSE CVE CVE-2022-22751 | recommended: 413 | 2026-10-17T01:22:50+00:00 | Vulnerability · Source |
| CVE-2022-22817 | suse_vex | SUSE CVE CVE-2022-22817 | recommended: 140 | 2026-10-17T01:22:48+00:00 | Vulnerability · Source |
| CVE-2022-22942 | suse_vex | SUSE CVE CVE-2022-22942 | known affected: 276 known not affected: 238 recommended: 1535 | 2026-10-17T01:22:46+00:00 | Vulnerability · Source |
| CVE-2022-23037 | suse_vex | SUSE CVE CVE-2022-23037 | known affected: 344 known not affected: 65 recommended: 1298 | 2026-10-17T01:22:45+00:00 | Vulnerability · Source |
| CVE-2022-23645 | suse_vex | SUSE CVE CVE-2022-23645 | known affected: 15 recommended: 186 | 2026-10-17T01:22:43+00:00 | Vulnerability · Source |
| CVE-2022-23816 | suse_vex | SUSE CVE CVE-2022-23816 | known affected: 231 known not affected: 384 recommended: 617 | 2026-10-17T01:22:41+00:00 | Vulnerability · Source |
| CVE-2022-24303 | suse_vex | SUSE CVE CVE-2022-24303 | known affected: 0 known not affected: 5 recommended: 28 | 2026-10-17T01:22:40+00:00 | Vulnerability · Source |
| CVE-2022-24795 | suse_vex | SUSE CVE CVE-2022-24795 | known affected: 273 recommended: 299 | 2026-10-17T01:22:38+00:00 | Vulnerability · Source |
| CVE-2022-24805 | suse_vex | SUSE CVE CVE-2022-24805 | known affected: 394 known not affected: 205 recommended: 263 | 2026-10-17T01:22:36+00:00 | Vulnerability · Source |
| CVE-2022-24836 | suse_vex | SUSE CVE CVE-2022-24836 | known affected: 394 recommended: 53 | 2026-10-17T01:22:35+00:00 | Vulnerability · Source |
| CVE-2022-25368 | suse_vex | SUSE CVE CVE-2022-25368 | known affected: 0 known not affected: 439 | 2026-10-17T01:22:33+00:00 | Vulnerability · Source |
| CVE-2022-25857 | suse_vex | SUSE CVE CVE-2022-25857 | known affected: 400 recommended: 53 | 2026-10-17T01:22:31+00:00 | Vulnerability · Source |
| CVE-2022-26383 | suse_vex | SUSE CVE CVE-2022-26383 | known affected: 1 recommended: 411 | 2026-10-17T01:22:29+00:00 | Vulnerability · Source |
| 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-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 |