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-0443 | suse_vex | SUSE CVE CVE-2022-0443 | known affected: 0 known not affected: 271 recommended: 33 | 2026-10-17T01:23:54+00:00 | Vulnerability · Source |
| CVE-2022-0485 | suse_vex | SUSE CVE CVE-2022-0485 | recommended: 50 | 2026-10-17T01:23:52+00:00 | Vulnerability · Source |
| CVE-2022-0492 | suse_vex | SUSE CVE CVE-2022-0492 | known affected: 349 known not affected: 57 recommended: 1693 | 2026-10-17T01:23:50+00:00 | Vulnerability · Source |
| CVE-2022-0494 | suse_vex | SUSE CVE CVE-2022-0494 | known affected: 282 known not affected: 329 recommended: 650 | 2026-10-17T01:23:49+00:00 | Vulnerability · Source |
| CVE-2022-0516 | suse_vex | SUSE CVE CVE-2022-0516 | known affected: 350 known not affected: 321 recommended: 1174 | 2026-10-17T01:23:47+00:00 | Vulnerability · Source |
| CVE-2022-0563 | suse_vex | SUSE CVE CVE-2022-0563 | known affected: 0 known not affected: 876 recommended: 395 | 2026-10-17T01:23:46+00:00 | Vulnerability · Source |
| CVE-2022-0581 | suse_vex | SUSE CVE CVE-2022-0581 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:44+00:00 | Vulnerability · Source |
| CVE-2022-0582 | suse_vex | SUSE CVE CVE-2022-0582 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:43+00:00 | Vulnerability · Source |
| CVE-2022-0583 | suse_vex | SUSE CVE CVE-2022-0583 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:42+00:00 | Vulnerability · Source |
| CVE-2022-0585 | suse_vex | SUSE CVE CVE-2022-0585 | known affected: 0 known not affected: 124 recommended: 339 | 2026-10-17T01:23:40+00:00 | Vulnerability · Source |
| CVE-2022-0615 | suse_vex | SUSE CVE CVE-2022-0615 | known affected: 0 known not affected: 439 | 2026-10-17T01:23:39+00:00 | Vulnerability · Source |
| CVE-2022-0617 | suse_vex | SUSE CVE CVE-2022-0617 | known affected: 207 known not affected: 2 recommended: 1651 | 2026-10-17T01:23:37+00:00 | Vulnerability · Source |
| CVE-2022-0644 | suse_vex | SUSE CVE CVE-2022-0644 | known affected: 207 known not affected: 119 recommended: 1332 | 2026-10-17T01:23:35+00:00 | Vulnerability · Source |
| CVE-2022-0711 | suse_vex | SUSE CVE CVE-2022-0711 | known affected: 0 known not affected: 15 recommended: 12 | 2026-10-17T01:23:34+00:00 | Vulnerability · Source |
| CVE-2022-0778 | suse_vex | SUSE CVE CVE-2022-0778 | known affected: 346 known not affected: 188 recommended: 1003 | 2026-10-17T01:23:33+00:00 | Vulnerability · Source |
| CVE-2022-0943 | suse_vex | SUSE CVE CVE-2022-0943 | known affected: 0 known not affected: 293 recommended: 43 | 2026-10-17T01:23:31+00:00 | Vulnerability · Source |
| CVE-2022-1215 | suse_vex | SUSE CVE CVE-2022-1215 | known affected: 394 known not affected: 82 recommended: 241 | 2026-10-17T01:23:28+00:00 | Vulnerability · Source |
| CVE-2022-1381 | suse_vex | SUSE CVE CVE-2022-1381 | known affected: 353 known not affected: 35 recommended: 389 | 2026-10-17T01:23:26+00:00 | Vulnerability · Source |
| CVE-2022-1785 | suse_vex | SUSE CVE CVE-2022-1785 | known affected: 363 recommended: 404 | 2026-10-17T01:23:24+00:00 | Vulnerability · Source |
| CVE-2022-1972 | suse_vex | SUSE CVE CVE-2022-1972 | known affected: 222 known not affected: 296 recommended: 1120 | 2026-10-17T01:23:22+00:00 | Vulnerability · Source |
| CVE-2022-2208 | suse_vex | SUSE CVE CVE-2022-2208 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-17T01:23:19+00:00 | Vulnerability · Source |
| CVE-2022-2344 | suse_vex | SUSE CVE CVE-2022-2344 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-17T01:23:18+00:00 | Vulnerability · Source |
| CVE-2022-2819 | suse_vex | SUSE CVE CVE-2022-2819 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-17T01:23:16+00:00 | Vulnerability · Source |
| CVE-2022-2845 | suse_vex | SUSE CVE CVE-2022-2845 | known affected: 238 recommended: 507 | 2026-10-17T01:23:14+00:00 | Vulnerability · Source |
| CVE-2022-2867 | suse_vex | SUSE CVE CVE-2022-2867 | known affected: 395 known not affected: 1 recommended: 264 | 2026-10-17T01:23:13+00:00 | Vulnerability · Source |
| CVE-2022-2906 | suse_vex | SUSE CVE CVE-2022-2906 | known affected: 0 known not affected: 569 recommended: 41 | 2026-10-17T01:23:11+00:00 | Vulnerability · Source |
| CVE-2022-2963 | suse_vex | SUSE CVE CVE-2022-2963 | known affected: 461 recommended: 109 | 2026-10-17T01:23:10+00:00 | Vulnerability · Source |
| CVE-2022-3107 | suse_vex | SUSE CVE CVE-2022-3107 | known affected: 272 known not affected: 217 recommended: 1045 | 2026-10-17T01:23:08+00:00 | Vulnerability · Source |
| 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 |