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-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 |
| CVE-2022-2519 | suse_vex | SUSE CVE CVE-2022-2519 | known affected: 395 known not affected: 1 recommended: 270 | 2026-10-16T14:59:50+00:00 | Vulnerability · Source |
| CVE-2022-2520 | suse_vex | SUSE CVE CVE-2022-2520 | known affected: 395 known not affected: 1 recommended: 270 | 2026-10-16T14:59:48+00:00 | Vulnerability · Source |
| CVE-2022-2521 | suse_vex | SUSE CVE CVE-2022-2521 | known affected: 395 known not affected: 1 recommended: 270 | 2026-10-16T14:59:46+00:00 | Vulnerability · Source |
| CVE-2022-2571 | suse_vex | SUSE CVE CVE-2022-2571 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:59:45+00:00 | Vulnerability · Source |
| CVE-2022-2580 | suse_vex | SUSE CVE CVE-2022-2580 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:59:43+00:00 | Vulnerability · Source |
| CVE-2022-2581 | suse_vex | SUSE CVE CVE-2022-2581 | known affected: 238 recommended: 507 | 2026-10-16T14:59:41+00:00 | Vulnerability · Source |
| CVE-2022-2586 | suse_vex | SUSE CVE CVE-2022-2586 | known affected: 228 known not affected: 73 recommended: 1576 | 2026-10-16T14:59:39+00:00 | Vulnerability · Source |
| CVE-2022-2602 | suse_vex | SUSE CVE CVE-2022-2602 | known affected: 242 known not affected: 199 recommended: 1548 | 2026-10-16T14:59:35+00:00 | Vulnerability · Source |
| CVE-2022-2639 | suse_vex | SUSE CVE CVE-2022-2639 | known affected: 237 known not affected: 34 recommended: 1465 | 2026-10-16T14:59:33+00:00 | Vulnerability · Source |
| CVE-2022-2663 | suse_vex | SUSE CVE CVE-2022-2663 | known affected: 237 known not affected: 307 recommended: 1552 | 2026-10-16T14:59:31+00:00 | Vulnerability · Source |
| CVE-2022-2795 | suse_vex | SUSE CVE CVE-2022-2795 | known affected: 253 known not affected: 247 recommended: 1102 | 2026-10-16T14:59:29+00:00 | Vulnerability · Source |
| CVE-2022-2816 | suse_vex | SUSE CVE CVE-2022-2816 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:59:27+00:00 | Vulnerability · Source |
| CVE-2022-2850 | suse_vex | SUSE CVE CVE-2022-2850 | known affected: 0 known not affected: 82 recommended: 122 | 2026-10-16T14:59:25+00:00 | Vulnerability · Source |
| CVE-2022-2862 | suse_vex | SUSE CVE CVE-2022-2862 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:59:22+00:00 | Vulnerability · Source |
| CVE-2022-2868 | suse_vex | SUSE CVE CVE-2022-2868 | known affected: 395 known not affected: 1 recommended: 264 | 2026-10-16T14:59:20+00:00 | Vulnerability · Source |
| CVE-2022-2869 | suse_vex | SUSE CVE CVE-2022-2869 | known affected: 395 known not affected: 1 recommended: 264 | 2026-10-16T14:59:17+00:00 | Vulnerability · Source |
| CVE-2022-2879 | suse_vex | SUSE CVE CVE-2022-2879 | recommended: 279 | 2026-10-16T14:59:15+00:00 | Vulnerability · Source |
| CVE-2022-2880 | suse_vex | SUSE CVE CVE-2022-2880 | recommended: 284 | 2026-10-16T14:59:13+00:00 | Vulnerability · Source |
| CVE-2022-2905 | suse_vex | SUSE CVE CVE-2022-2905 | known affected: 212 known not affected: 199 recommended: 1342 | 2026-10-16T14:59:10+00:00 | Vulnerability · Source |
| CVE-2022-2928 | suse_vex | SUSE CVE CVE-2022-2928 | known affected: 406 recommended: 300 | 2026-10-16T14:59:07+00:00 | Vulnerability · Source |
| CVE-2022-2929 | suse_vex | SUSE CVE CVE-2022-2929 | known affected: 406 recommended: 300 | 2026-10-16T14:59:04+00:00 | Vulnerability · Source |
| CVE-2022-2959 | suse_vex | SUSE CVE CVE-2022-2959 | known affected: 265 known not affected: 306 recommended: 660 | 2026-10-16T14:59:02+00:00 | Vulnerability · Source |
| CVE-2022-2964 | suse_vex | SUSE CVE CVE-2022-2964 | known not affected: 6 recommended: 1598 | 2026-10-16T14:59:00+00:00 | Vulnerability · Source |
| CVE-2022-2978 | suse_vex | SUSE CVE CVE-2022-2978 | known affected: 228 known not affected: 267 recommended: 1338 | 2026-10-16T14:58:57+00:00 | Vulnerability · Source |
| CVE-2022-2982 | suse_vex | SUSE CVE CVE-2022-2982 | known affected: 259 known not affected: 2 recommended: 487 | 2026-10-16T14:58:54+00:00 | Vulnerability · Source |
| CVE-2022-2989 | suse_vex | SUSE CVE CVE-2022-2989 | recommended: 197 | 2026-10-16T14:58:52+00:00 | Vulnerability · Source |
| CVE-2022-3016 | suse_vex | SUSE CVE CVE-2022-3016 | known affected: 237 known not affected: 2 recommended: 507 | 2026-10-16T14:58:50+00:00 | Vulnerability · Source |
| CVE-2022-3028 | suse_vex | SUSE CVE CVE-2022-3028 | known affected: 237 recommended: 1554 | 2026-10-16T14:58:47+00:00 | Vulnerability · Source |
| CVE-2022-3078 | suse_vex | SUSE CVE CVE-2022-3078 | known affected: 263 known not affected: 306 recommended: 612 | 2026-10-16T14:58:44+00:00 | Vulnerability · Source |
| CVE-2022-3104 | suse_vex | SUSE CVE CVE-2022-3104 | known affected: 284 known not affected: 335 recommended: 597 | 2026-10-16T14:58:39+00:00 | Vulnerability · Source |
| CVE-2022-3105 | suse_vex | SUSE CVE CVE-2022-3105 | known affected: 272 known not affected: 258 recommended: 871 | 2026-10-16T14:58:37+00:00 | Vulnerability · Source |
| CVE-2022-3108 | suse_vex | SUSE CVE CVE-2022-3108 | known affected: 272 known not affected: 181 recommended: 1045 | 2026-10-16T14:58:34+00:00 | Vulnerability · Source |
| CVE-2022-3115 | suse_vex | SUSE CVE CVE-2022-3115 | known affected: 272 known not affected: 279 recommended: 851 | 2026-10-16T14:58:31+00:00 | Vulnerability · Source |
| CVE-2022-3162 | suse_vex | SUSE CVE CVE-2022-3162 | known affected: 0 known not affected: 24 recommended: 65 | 2026-10-16T14:58:28+00:00 | Vulnerability · Source |
| CVE-2022-3165 | suse_vex | SUSE CVE CVE-2022-3165 | known affected: 20 known not affected: 1002 recommended: 949 | 2026-10-16T14:58:25+00:00 | Vulnerability · Source |
| CVE-2022-3169 | suse_vex | SUSE CVE CVE-2022-3169 | known affected: 255 known not affected: 2 recommended: 1436 | 2026-10-16T14:58:22+00:00 | Vulnerability · Source |
| CVE-2022-3190 | suse_vex | SUSE CVE CVE-2022-3190 | known affected: 68 known not affected: 84 recommended: 234 | 2026-10-16T14:58:19+00:00 | Vulnerability · Source |
| CVE-2022-3202 | suse_vex | SUSE CVE CVE-2022-3202 | known affected: 271 known not affected: 243 recommended: 606 | 2026-10-16T14:58:16+00:00 | Vulnerability · Source |
| CVE-2022-3213 | suse_vex | SUSE CVE CVE-2022-3213 | known affected: 0 known not affected: 373 recommended: 320 | 2026-10-16T14:58:14+00:00 | Vulnerability · Source |
| CVE-2022-3235 | suse_vex | SUSE CVE CVE-2022-3235 | known affected: 259 known not affected: 2 recommended: 487 | 2026-10-16T14:58:11+00:00 | Vulnerability · Source |
| CVE-2022-3238 | suse_vex | SUSE CVE CVE-2022-3238 | known not affected: 363 | 2026-10-16T14:58:08+00:00 | Vulnerability · Source |
| CVE-2022-3287 | suse_vex | SUSE CVE CVE-2022-3287 | known affected: 0 known not affected: 242 recommended: 131 | 2026-10-16T14:58:05+00:00 | Vulnerability · Source |
| CVE-2022-3294 | suse_vex | SUSE CVE CVE-2022-3294 | known affected: 0 known not affected: 24 recommended: 83 | 2026-10-16T14:58:03+00:00 | Vulnerability · Source |
| CVE-2022-3303 | suse_vex | SUSE CVE CVE-2022-3303 | known affected: 223 known not affected: 46 recommended: 1682 | 2026-10-16T14:57:59+00:00 | Vulnerability · Source |
| CVE-2022-3437 | suse_vex | SUSE CVE CVE-2022-3437 | known affected: 269 known not affected: 1768 recommended: 1160 | 2026-10-16T14:57:53+00:00 | Vulnerability · Source |
| CVE-2022-3517 | suse_vex | SUSE CVE CVE-2022-3517 | recommended: 26 | 2026-10-16T14:57:50+00:00 | Vulnerability · Source |
| CVE-2022-3520 | suse_vex | SUSE CVE CVE-2022-3520 | known affected: 267 known not affected: 26 recommended: 407 | 2026-10-16T14:57:48+00:00 | Vulnerability · Source |