VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292089 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-2054 | suse_vex | SUSE CVE CVE-2019-2054 | known not affected: 413 | 2026-07-25T18:09:02+00:00 | Vulnerability · Source |
| CVE-2019-2214 | suse_vex | SUSE CVE CVE-2019-2214 | known not affected: 208 | 2026-07-25T18:08:59+00:00 | Vulnerability · Source |
| CVE-2019-2426 | suse_vex | SUSE CVE CVE-2019-2426 | known affected: 480 known not affected: 9 recommended: 814 | 2026-07-25T18:08:58+00:00 | Vulnerability · Source |
| CVE-2019-2481 | suse_vex | SUSE CVE CVE-2019-2481 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:56+00:00 | Vulnerability · Source |
| CVE-2019-2503 | suse_vex | SUSE CVE CVE-2019-2503 | known affected: 70 known not affected: 185 recommended: 163 | 2026-07-25T18:08:55+00:00 | Vulnerability · Source |
| CVE-2019-2513 | suse_vex | SUSE CVE CVE-2019-2513 | known affected: 70 known not affected: 185 | 2026-07-25T18:08:54+00:00 | Vulnerability · Source |
| CVE-2019-2528 | suse_vex | SUSE CVE CVE-2019-2528 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:51+00:00 | Vulnerability · Source |
| CVE-2019-2533 | suse_vex | SUSE CVE CVE-2019-2533 | known affected: 70 known not affected: 185 recommended: 10 | 2026-07-25T18:08:50+00:00 | Vulnerability · Source |
| CVE-2019-2602 | suse_vex | SUSE CVE CVE-2019-2602 | known affected: 492 known not affected: 9 recommended: 1124 | 2026-07-25T18:08:46+00:00 | Vulnerability · Source |
| CVE-2019-2758 | suse_vex | SUSE CVE CVE-2019-2758 | known affected: 1 known not affected: 123 recommended: 871 | 2026-07-25T18:08:33+00:00 | Vulnerability · Source |
| CVE-2019-2769 | suse_vex | SUSE CVE CVE-2019-2769 | known affected: 500 known not affected: 9 recommended: 1149 | 2026-07-25T18:08:31+00:00 | Vulnerability · Source |
| CVE-2019-2821 | suse_vex | SUSE CVE CVE-2019-2821 | known affected: 394 known not affected: 9 recommended: 316 | 2026-07-25T18:08:26+00:00 | Vulnerability · Source |
| CVE-2019-2911 | suse_vex | SUSE CVE CVE-2019-2911 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:24+00:00 | Vulnerability · Source |
| CVE-2019-2920 | suse_vex | SUSE CVE CVE-2019-2920 | known affected: 13 known not affected: 121 | 2026-07-25T18:08:23+00:00 | Vulnerability · Source |
| CVE-2019-2924 | suse_vex | SUSE CVE CVE-2019-2924 | known affected: 13 known not affected: 121 | 2026-07-25T18:08:22+00:00 | Vulnerability · Source |
| CVE-2019-2933 | suse_vex | SUSE CVE CVE-2019-2933 | known affected: 525 recommended: 1074 | 2026-07-25T18:08:20+00:00 | Vulnerability · Source |
| CVE-2019-2948 | suse_vex | SUSE CVE CVE-2019-2948 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:19+00:00 | Vulnerability · Source |
| CVE-2019-2949 | suse_vex | SUSE CVE CVE-2019-2949 | known affected: 525 recommended: 984 | 2026-07-25T18:08:17+00:00 | Vulnerability · Source |
| CVE-2019-2958 | suse_vex | SUSE CVE CVE-2019-2958 | known affected: 525 recommended: 953 | 2026-07-25T18:08:15+00:00 | Vulnerability · Source |
| CVE-2019-2960 | suse_vex | SUSE CVE CVE-2019-2960 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:14+00:00 | Vulnerability · Source |
| CVE-2019-2969 | suse_vex | SUSE CVE CVE-2019-2969 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:13+00:00 | Vulnerability · Source |
| CVE-2019-2991 | suse_vex | SUSE CVE CVE-2019-2991 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:10+00:00 | Vulnerability · Source |
| CVE-2019-2992 | suse_vex | SUSE CVE CVE-2019-2992 | known affected: 525 recommended: 1129 | 2026-07-25T18:08:08+00:00 | Vulnerability · Source |
| CVE-2019-2996 | suse_vex | SUSE CVE CVE-2019-2996 | known affected: 131 recommended: 295 | 2026-07-25T18:08:07+00:00 | Vulnerability · Source |
| CVE-2019-3003 | suse_vex | SUSE CVE CVE-2019-3003 | known affected: 13 known not affected: 121 recommended: 10 | 2026-07-25T18:08:05+00:00 | Vulnerability · Source |
| CVE-2019-3459 | suse_vex | SUSE CVE CVE-2019-3459 | known affected: 74 known not affected: 186 recommended: 732 | 2026-07-25T18:08:02+00:00 | Vulnerability · Source |
| CVE-2019-3689 | suse_vex | SUSE CVE CVE-2019-3689 | known affected: 387 known not affected: 3 recommended: 392 | 2026-07-25T18:08:01+00:00 | Vulnerability · Source |
| CVE-2019-3693 | suse_vex | SUSE CVE CVE-2019-3693 | recommended: 31 | 2026-07-25T18:07:59+00:00 | Vulnerability · Source |
| CVE-2019-3821 | suse_vex | SUSE CVE CVE-2019-3821 | known affected: 85 known not affected: 310 recommended: 958 | 2026-07-25T18:07:56+00:00 | Vulnerability · Source |
| CVE-2019-3824 | suse_vex | SUSE CVE CVE-2019-3824 | known affected: 320 known not affected: 1419 recommended: 3100 | 2026-07-25T18:07:54+00:00 | Vulnerability · Source |
| CVE-2019-3846 | suse_vex | SUSE CVE CVE-2019-3846 | known affected: 203 known not affected: 21 recommended: 1052 | 2026-07-25T18:07:49+00:00 | Vulnerability · Source |
| CVE-2019-3857 | suse_vex | SUSE CVE CVE-2019-3857 | known affected: 457 known not affected: 76 recommended: 357 | 2026-07-25T18:07:48+00:00 | Vulnerability · Source |
| CVE-2019-3896 | suse_vex | SUSE CVE CVE-2019-3896 | known not affected: 272 recommended: 49 | 2026-07-25T18:07:42+00:00 | Vulnerability · Source |
| CVE-2019-5018 | suse_vex | SUSE CVE CVE-2019-5018 | known not affected: 356 recommended: 5 | 2026-07-25T18:07:41+00:00 | Vulnerability · Source |
| CVE-2019-5188 | suse_vex | SUSE CVE CVE-2019-5188 | known affected: 410 known not affected: 123 recommended: 707 | 2026-07-25T18:07:38+00:00 | Vulnerability · Source |
| CVE-2019-5418 | suse_vex | SUSE CVE CVE-2019-5418 | known affected: 405 recommended: 208 | 2026-07-25T18:07:36+00:00 | Vulnerability · Source |
| CVE-2019-5435 | suse_vex | SUSE CVE CVE-2019-5435 | known affected: 320 known not affected: 208 recommended: 281 | 2026-07-25T18:07:35+00:00 | Vulnerability · Source |
| CVE-2019-5747 | suse_vex | SUSE CVE CVE-2019-5747 | known affected: 1 known not affected: 27 recommended: 136 | 2026-07-25T18:07:21+00:00 | Vulnerability · Source |
| CVE-2019-5815 | suse_vex | SUSE CVE CVE-2019-5815 | recommended: 15 | 2026-07-25T18:07:20+00:00 | Vulnerability · Source |
| CVE-2019-6227 | suse_vex | SUSE CVE CVE-2019-6227 | known not affected: 82 recommended: 983 | 2026-07-25T18:07:07+00:00 | Vulnerability · Source |
| CVE-2019-6234 | suse_vex | SUSE CVE CVE-2019-6234 | known not affected: 82 recommended: 983 | 2026-07-25T18:07:04+00:00 | Vulnerability · Source |
| CVE-2019-6237 | suse_vex | SUSE CVE CVE-2019-6237 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-25T18:07:03+00:00 | Vulnerability · Source |
| CVE-2019-6446 | suse_vex | SUSE CVE CVE-2019-6446 | known affected: 411 known not affected: 27 recommended: 527 | 2026-07-25T18:07:02+00:00 | Vulnerability · Source |
| CVE-2019-6462 | suse_vex | SUSE CVE CVE-2019-6462 | known affected: 627 known not affected: 62 recommended: 87 | 2026-07-25T18:07:00+00:00 | Vulnerability · Source |
| CVE-2019-6477 | suse_vex | SUSE CVE CVE-2019-6477 | known affected: 414 known not affected: 40 recommended: 875 | 2026-07-25T18:06:55+00:00 | Vulnerability · Source |
| CVE-2019-7398 | suse_vex | SUSE CVE CVE-2019-7398 | known affected: 46 recommended: 842 | 2026-07-25T18:06:49+00:00 | Vulnerability · Source |
| CVE-2019-7573 | suse_vex | SUSE CVE CVE-2019-7573 | known affected: 71 recommended: 323 | 2026-07-25T18:06:47+00:00 | Vulnerability · Source |
| CVE-2019-7574 | suse_vex | SUSE CVE CVE-2019-7574 | known affected: 71 recommended: 323 | 2026-07-25T18:06:46+00:00 | Vulnerability · Source |
| CVE-2019-7635 | suse_vex | SUSE CVE CVE-2019-7635 | known affected: 71 recommended: 343 | 2026-07-25T18:06:43+00:00 | Vulnerability · Source |
| CVE-2019-7665 | suse_vex | SUSE CVE CVE-2019-7665 | known affected: 522 recommended: 1124 | 2026-07-25T18:06:42+00:00 | Vulnerability · Source |