VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
287978 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2019-11045 | suse_vex | SUSE CVE CVE-2019-11045 | known not affected: 1230 recommended: 4064 | 2026-07-31T01:39:47+00:00 | Vulnerability · Source |
| CVE-2019-11070 | suse_vex | SUSE CVE CVE-2019-11070 | known affected: 154 known not affected: 82 recommended: 1095 | 2026-07-31T01:39:45+00:00 | Vulnerability · Source |
| CVE-2019-11234 | suse_vex | SUSE CVE CVE-2019-11234 | known affected: 156 known not affected: 116 recommended: 763 | 2026-07-31T01:39:44+00:00 | Vulnerability · Source |
| CVE-2019-11356 | suse_vex | SUSE CVE CVE-2019-11356 | known not affected: 18 recommended: 13 | 2026-07-31T01:39:42+00:00 | Vulnerability · Source |
| CVE-2019-11463 | suse_vex | SUSE CVE CVE-2019-11463 | known not affected: 66 | 2026-07-31T01:39:41+00:00 | Vulnerability · Source |
| CVE-2019-11596 | suse_vex | SUSE CVE CVE-2019-11596 | known affected: 18 recommended: 573 | 2026-07-31T01:39:39+00:00 | Vulnerability · Source |
| CVE-2019-11598 | suse_vex | SUSE CVE CVE-2019-11598 | known affected: 142 recommended: 756 | 2026-07-31T01:39:37+00:00 | Vulnerability · Source |
| CVE-2019-11753 | suse_vex | SUSE CVE CVE-2019-11753 | known affected: 20 recommended: 525 | 2026-07-31T01:39:35+00:00 | Vulnerability · Source |
| CVE-2019-11758 | suse_vex | SUSE CVE CVE-2019-11758 | known not affected: 160 recommended: 578 | 2026-07-31T01:39:34+00:00 | Vulnerability · Source |
| CVE-2019-12436 | suse_vex | SUSE CVE CVE-2019-12436 | known affected: 320 known not affected: 2360 recommended: 2167 | 2026-07-31T01:39:31+00:00 | Vulnerability · Source |
| CVE-2019-12455 | suse_vex | SUSE CVE CVE-2019-12455 | known not affected: 485 | 2026-07-31T01:39:29+00:00 | Vulnerability · Source |
| CVE-2019-12520 | suse_vex | SUSE CVE CVE-2019-12520 | known not affected: 20 recommended: 27 | 2026-07-31T01:39:28+00:00 | Vulnerability · Source |
| CVE-2019-12817 | suse_vex | SUSE CVE CVE-2019-12817 | known affected: 48 known not affected: 377 recommended: 436 | 2026-07-31T01:39:26+00:00 | Vulnerability · Source |
| CVE-2019-13133 | suse_vex | SUSE CVE CVE-2019-13133 | known affected: 142 recommended: 712 | 2026-07-31T01:39:24+00:00 | Vulnerability · Source |
| CVE-2019-13135 | suse_vex | SUSE CVE CVE-2019-13135 | known affected: 142 recommended: 712 | 2026-07-31T01:39:22+00:00 | Vulnerability · Source |
| CVE-2019-13136 | suse_vex | SUSE CVE CVE-2019-13136 | known affected: 46 known not affected: 338 recommended: 588 | 2026-07-31T01:39:21+00:00 | Vulnerability · Source |
| CVE-2019-13225 | suse_vex | SUSE CVE CVE-2019-13225 | known affected: 315 recommended: 209 | 2026-07-31T01:39:19+00:00 | Vulnerability · Source |
| CVE-2019-13299 | suse_vex | SUSE CVE CVE-2019-13299 | known affected: 45 known not affected: 393 recommended: 588 | 2026-07-31T01:39:18+00:00 | Vulnerability · Source |
| CVE-2019-13616 | suse_vex | SUSE CVE CVE-2019-13616 | known affected: 46 recommended: 316 | 2026-07-31T01:39:16+00:00 | Vulnerability · Source |
| CVE-2019-14290 | suse_vex | SUSE CVE CVE-2019-14290 | known not affected: 895 | 2026-07-31T01:39:14+00:00 | Vulnerability · Source |
| CVE-2019-14864 | suse_vex | SUSE CVE CVE-2019-14864 | recommended: 248 | 2026-07-31T01:39:12+00:00 | Vulnerability · Source |
| CVE-2019-15666 | suse_vex | SUSE CVE CVE-2019-15666 | known affected: 165 known not affected: 98 recommended: 899 | 2026-07-31T01:39:09+00:00 | Vulnerability · Source |
| CVE-2019-16884 | suse_vex | SUSE CVE CVE-2019-16884 | known affected: 330 recommended: 531 | 2026-07-31T01:39:07+00:00 | Vulnerability · Source |
| CVE-2019-17008 | suse_vex | SUSE CVE CVE-2019-17008 | known affected: 20 known not affected: 176 recommended: 449 | 2026-07-31T01:39:05+00:00 | Vulnerability · Source |
| CVE-2019-17056 | suse_vex | SUSE CVE CVE-2019-17056 | known affected: 111 known not affected: 47 recommended: 820 | 2026-07-31T01:39:03+00:00 | Vulnerability · Source |
| CVE-2019-18218 | suse_vex | SUSE CVE CVE-2019-18218 | known affected: 329 known not affected: 3 recommended: 559 | 2026-07-31T01:39:02+00:00 | Vulnerability · Source |
| CVE-2019-18397 | suse_vex | SUSE CVE CVE-2019-18397 | known affected: 394 known not affected: 113 recommended: 197 | 2026-07-31T01:39:00+00:00 | Vulnerability · Source |
| CVE-2019-18420 | suse_vex | SUSE CVE CVE-2019-18420 | known not affected: 2 recommended: 250 | 2026-07-31T01:38:59+00:00 | Vulnerability · Source |
| CVE-2019-18604 | suse_vex | SUSE CVE CVE-2019-18604 | known not affected: 4612 recommended: 5257 | 2026-07-31T01:38:56+00:00 | Vulnerability · Source |
| CVE-2019-18675 | suse_vex | SUSE CVE CVE-2019-18675 | known affected: 21 known not affected: 154 recommended: 209 | 2026-07-31T01:38:54+00:00 | Vulnerability · Source |
| CVE-2019-18928 | suse_vex | SUSE CVE CVE-2019-18928 | known not affected: 9 recommended: 13 | 2026-07-31T01:38:53+00:00 | Vulnerability · Source |
| CVE-2019-19844 | suse_vex | SUSE CVE CVE-2019-19844 | known affected: 1 recommended: 544 | 2026-07-31T01:38:50+00:00 | Vulnerability · Source |
| CVE-2019-19947 | suse_vex | SUSE CVE CVE-2019-19947 | known affected: 320 known not affected: 320 recommended: 781 | 2026-07-31T01:38:48+00:00 | Vulnerability · Source |
| CVE-2019-19953 | suse_vex | SUSE CVE CVE-2019-19953 | known affected: 20 known not affected: 499 recommended: 16 | 2026-07-31T01:38:46+00:00 | Vulnerability · Source |
| CVE-2019-20386 | suse_vex | SUSE CVE CVE-2019-20386 | known affected: 516 recommended: 1176 | 2026-07-31T01:38:44+00:00 | Vulnerability · Source |
| CVE-2019-20477 | suse_vex | SUSE CVE CVE-2019-20477 | known not affected: 102 recommended: 42 | 2026-07-31T01:38:43+00:00 | Vulnerability · Source |
| CVE-2020-0433 | suse_vex | SUSE CVE CVE-2020-0433 | known affected: 400 known not affected: 59 recommended: 455 | 2026-07-31T01:38:40+00:00 | Vulnerability · Source |
| CVE-2020-0435 | suse_vex | SUSE CVE CVE-2020-0435 | known not affected: 356 | 2026-07-31T01:38:39+00:00 | Vulnerability · Source |
| CVE-2020-0452 | suse_vex | SUSE CVE CVE-2020-0452 | known affected: 2 recommended: 183 | 2026-07-31T01:38:37+00:00 | Vulnerability · Source |
| CVE-2020-2764 | suse_vex | SUSE CVE CVE-2020-2764 | known affected: 60 | 2026-07-31T01:38:35+00:00 | Vulnerability · Source |
| CVE-2020-3868 | suse_vex | SUSE CVE CVE-2020-3868 | known affected: 46 known not affected: 264 recommended: 1090 | 2026-07-31T01:38:33+00:00 | Vulnerability · Source |
| CVE-2020-3894 | suse_vex | SUSE CVE CVE-2020-3894 | known affected: 45 known not affected: 90 recommended: 1018 | 2026-07-31T01:38:31+00:00 | Vulnerability · Source |
| CVE-2020-6750 | suse_vex | SUSE CVE CVE-2020-6750 | known affected: 320 known not affected: 520 recommended: 693 | 2026-07-31T01:38:29+00:00 | Vulnerability · Source |
| CVE-2020-6805 | suse_vex | SUSE CVE CVE-2020-6805 | recommended: 380 | 2026-07-31T01:38:28+00:00 | Vulnerability · Source |
| CVE-2020-6812 | suse_vex | SUSE CVE CVE-2020-6812 | recommended: 380 | 2026-07-31T01:38:26+00:00 | Vulnerability · Source |
| CVE-2020-7211 | suse_vex | SUSE CVE CVE-2020-7211 | known affected: 66 known not affected: 24 recommended: 186 | 2026-07-31T01:38:24+00:00 | Vulnerability · Source |
| CVE-2020-8025 | suse_vex | SUSE CVE CVE-2020-8025 | known affected: 311 known not affected: 534 recommended: 539 | 2026-07-31T01:38:22+00:00 | Vulnerability · Source |
| CVE-2020-8315 | suse_vex | SUSE CVE CVE-2020-8315 | known affected: 14 known not affected: 685 | 2026-07-31T01:38:20+00:00 | Vulnerability · Source |
| CVE-2020-8561 | suse_vex | SUSE CVE CVE-2020-8561 | known affected: 1 recommended: 44 | 2026-07-31T01:38:19+00:00 | Vulnerability · Source |
| CVE-2020-8608 | suse_vex | SUSE CVE CVE-2020-8608 | known affected: 462 known not affected: 285 recommended: 2640 | 2026-07-31T01:38:17+00:00 | Vulnerability · Source |