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-1616 | suse_vex | SUSE CVE CVE-2022-1616 | known affected: 363 known not affected: 1 recommended: 389 | 2026-10-16T15:01:15+00:00 | Vulnerability · Source |
| CVE-2022-1619 | suse_vex | SUSE CVE CVE-2022-1619 | known affected: 353 known not affected: 33 recommended: 389 | 2026-10-16T15:01:13+00:00 | Vulnerability · Source |
| CVE-2022-1620 | suse_vex | SUSE CVE CVE-2022-1620 | known affected: 363 recommended: 389 | 2026-10-16T15:01:11+00:00 | Vulnerability · Source |
| CVE-2022-1651 | suse_vex | SUSE CVE CVE-2022-1651 | known affected: 257 known not affected: 367 recommended: 586 | 2026-10-16T15:01:08+00:00 | Vulnerability · Source |
| CVE-2022-1664 | suse_vex | SUSE CVE CVE-2022-1664 | known affected: 0 known not affected: 3 recommended: 132 | 2026-10-16T15:01:07+00:00 | Vulnerability · Source |
| CVE-2022-1674 | suse_vex | SUSE CVE CVE-2022-1674 | known affected: 0 known not affected: 277 recommended: 33 | 2026-10-16T15:01:06+00:00 | Vulnerability · Source |
| CVE-2022-1679 | suse_vex | SUSE CVE CVE-2022-1679 | known affected: 194 known not affected: 6 recommended: 2002 | 2026-10-16T15:01:04+00:00 | Vulnerability · Source |
| CVE-2022-1705 | suse_vex | SUSE CVE CVE-2022-1705 | known affected: 0 known not affected: 51 recommended: 300 | 2026-10-16T15:01:02+00:00 | Vulnerability · Source |
| CVE-2022-1708 | suse_vex | SUSE CVE CVE-2022-1708 | recommended: 100 | 2026-10-16T15:01:01+00:00 | Vulnerability · Source |
| CVE-2022-1733 | suse_vex | SUSE CVE CVE-2022-1733 | known affected: 363 known not affected: 7 recommended: 389 | 2026-10-16T15:00:59+00:00 | Vulnerability · Source |
| CVE-2022-1769 | suse_vex | SUSE CVE CVE-2022-1769 | known affected: 0 known not affected: 277 recommended: 33 | 2026-10-16T15:00:58+00:00 | Vulnerability · Source |
| CVE-2022-1796 | suse_vex | SUSE CVE CVE-2022-1796 | known affected: 363 recommended: 389 | 2026-10-16T15:00:57+00:00 | Vulnerability · Source |
| CVE-2022-1804 | suse_vex | SUSE CVE CVE-2022-1804 | known affected: 0 known not affected: 228 | 2026-10-16T15:00:55+00:00 | Vulnerability · Source |
| CVE-2022-1836 | suse_vex | SUSE CVE CVE-2022-1836 | known affected: 219 recommended: 395 | 2026-10-16T15:00:54+00:00 | Vulnerability · Source |
| CVE-2022-1852 | suse_vex | SUSE CVE CVE-2022-1852 | known affected: 257 known not affected: 363 recommended: 634 | 2026-10-16T15:00:52+00:00 | Vulnerability · Source |
| CVE-2022-1882 | suse_vex | SUSE CVE CVE-2022-1882 | known affected: 273 known not affected: 384 recommended: 645 | 2026-10-16T15:00:50+00:00 | Vulnerability · Source |
| CVE-2022-1897 | suse_vex | SUSE CVE CVE-2022-1897 | known affected: 363 recommended: 404 | 2026-10-16T15:00:48+00:00 | Vulnerability · Source |
| CVE-2022-1919 | suse_vex | SUSE CVE CVE-2022-1919 | known affected: 0 known not affected: 1 recommended: 9 | 2026-10-16T15:00:47+00:00 | Vulnerability · Source |
| CVE-2022-1920 | suse_vex | SUSE CVE CVE-2022-1920 | known affected: 2 known not affected: 10 recommended: 183 | 2026-10-16T15:00:46+00:00 | Vulnerability · Source |
| CVE-2022-1921 | suse_vex | SUSE CVE CVE-2022-1921 | known affected: 2 known not affected: 10 recommended: 183 | 2026-10-16T15:00:44+00:00 | Vulnerability · Source |
| CVE-2022-1927 | suse_vex | SUSE CVE CVE-2022-1927 | known affected: 353 known not affected: 33 recommended: 404 | 2026-10-16T15:00:43+00:00 | Vulnerability · Source |
| CVE-2022-1973 | suse_vex | SUSE CVE CVE-2022-1973 | known affected: 0 known not affected: 418 recommended: 6 | 2026-10-16T15:00:41+00:00 | Vulnerability · Source |
| CVE-2022-1975 | suse_vex | SUSE CVE CVE-2022-1975 | known affected: 220 known not affected: 2 recommended: 1249 | 2026-10-16T15:00:40+00:00 | Vulnerability · Source |
| CVE-2022-1998 | suse_vex | SUSE CVE CVE-2022-1998 | known affected: 257 known not affected: 358 recommended: 630 | 2026-10-16T15:00:38+00:00 | Vulnerability · Source |
| CVE-2022-2056 | suse_vex | SUSE CVE CVE-2022-2056 | known affected: 481 known not affected: 1 recommended: 180 | 2026-10-16T15:00:36+00:00 | Vulnerability · Source |
| CVE-2022-2057 | suse_vex | SUSE CVE CVE-2022-2057 | known affected: 481 known not affected: 1 recommended: 180 | 2026-10-16T15:00:35+00:00 | Vulnerability · Source |
| CVE-2022-2078 | suse_vex | SUSE CVE CVE-2022-2078 | known affected: 0 known not affected: 296 recommended: 64 | 2026-10-16T15:00:33+00:00 | Vulnerability · Source |
| CVE-2022-2084 | suse_vex | SUSE CVE CVE-2022-2084 | known affected: 254 recommended: 251 | 2026-10-16T15:00:31+00:00 | Vulnerability · Source |
| CVE-2022-2097 | suse_vex | SUSE CVE CVE-2022-2097 | known affected: 213 known not affected: 393 recommended: 773 | 2026-10-16T15:00:30+00:00 | Vulnerability · Source |
| CVE-2022-2124 | suse_vex | SUSE CVE CVE-2022-2124 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-16T15:00:28+00:00 | Vulnerability · Source |
| CVE-2022-2127 | suse_vex | SUSE CVE CVE-2022-2127 | known affected: 524 recommended: 2281 | 2026-10-16T15:00:26+00:00 | Vulnerability · Source |
| CVE-2022-2153 | suse_vex | SUSE CVE CVE-2022-2153 | known affected: 255 known not affected: 160 recommended: 1429 | 2026-10-16T15:00:25+00:00 | Vulnerability · Source |
| CVE-2022-2182 | suse_vex | SUSE CVE CVE-2022-2182 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-16T15:00:23+00:00 | Vulnerability · Source |
| CVE-2022-2183 | suse_vex | SUSE CVE CVE-2022-2183 | known affected: 247 recommended: 507 | 2026-10-16T15:00:22+00:00 | Vulnerability · Source |
| CVE-2022-2196 | suse_vex | SUSE CVE CVE-2022-2196 | known affected: 298 known not affected: 199 recommended: 964 | 2026-10-16T15:00:20+00:00 | Vulnerability · Source |
| CVE-2022-2211 | suse_vex | SUSE CVE CVE-2022-2211 | known affected: 0 known not affected: 523 recommended: 563 | 2026-10-16T15:00:18+00:00 | Vulnerability · Source |
| CVE-2022-2231 | suse_vex | SUSE CVE CVE-2022-2231 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-16T15:00:16+00:00 | Vulnerability · Source |
| CVE-2022-2257 | suse_vex | SUSE CVE CVE-2022-2257 | known affected: 247 recommended: 507 | 2026-10-16T15:00:14+00:00 | Vulnerability · Source |
| CVE-2022-2264 | suse_vex | SUSE CVE CVE-2022-2264 | known affected: 237 known not affected: 26 recommended: 507 | 2026-10-16T15:00:12+00:00 | Vulnerability · Source |
| CVE-2022-2274 | suse_vex | SUSE CVE CVE-2022-2274 | known affected: 0 known not affected: 723 recommended: 209 | 2026-10-16T15:00:11+00:00 | Vulnerability · Source |
| CVE-2022-2284 | suse_vex | SUSE CVE CVE-2022-2284 | known affected: 247 recommended: 507 | 2026-10-16T15:00:09+00:00 | Vulnerability · Source |
| CVE-2022-2288 | suse_vex | SUSE CVE CVE-2022-2288 | known affected: 0 known not affected: 273 recommended: 33 | 2026-10-16T15:00:07+00:00 | Vulnerability · Source |
| CVE-2022-2308 | suse_vex | SUSE CVE CVE-2022-2308 | known affected: 0 known not affected: 622 recommended: 6 | 2026-10-16T15:00:06+00:00 | Vulnerability · Source |
| CVE-2022-2309 | suse_vex | SUSE CVE CVE-2022-2309 | known affected: 394 known not affected: 114 recommended: 276 | 2026-10-16T15:00:04+00:00 | Vulnerability · Source |
| CVE-2022-2318 | suse_vex | SUSE CVE CVE-2022-2318 | known affected: 228 recommended: 1457 | 2026-10-16T15:00:01+00:00 | Vulnerability · Source |
| CVE-2022-2320 | suse_vex | SUSE CVE CVE-2022-2320 | known affected: 401 recommended: 278 | 2026-10-16T14:59:59+00:00 | Vulnerability · Source |
| CVE-2022-2327 | suse_vex | SUSE CVE CVE-2022-2327 | known affected: 0 known not affected: 624 | 2026-10-16T14:59:57+00:00 | Vulnerability · Source |
| CVE-2022-2345 | suse_vex | SUSE CVE CVE-2022-2345 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:59:55+00:00 | Vulnerability · Source |
| CVE-2022-2503 | suse_vex | SUSE CVE CVE-2022-2503 | known affected: 376 known not affected: 300 recommended: 874 | 2026-10-16T14:59:53+00:00 | Vulnerability · Source |
| CVE-2022-2509 | suse_vex | SUSE CVE CVE-2022-2509 | known affected: 237 known not affected: 62 recommended: 652 | 2026-10-16T14:59:52+00:00 | Vulnerability · Source |