VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2018-17977 | suse_vex | SUSE CVE CVE-2018-17977 | known not affected: 138 | 2026-07-31T01:41:11+00:00 | Vulnerability · Source |
| CVE-2018-18023 | suse_vex | SUSE CVE CVE-2018-18023 | known not affected: 176 | 2026-07-31T01:41:09+00:00 | Vulnerability · Source |
| CVE-2018-18024 | suse_vex | SUSE CVE CVE-2018-18024 | known affected: 1 recommended: 736 | 2026-07-31T01:41:08+00:00 | Vulnerability · Source |
| CVE-2018-18313 | suse_vex | SUSE CVE CVE-2018-18313 | known affected: 341 known not affected: 84 recommended: 357 | 2026-07-31T01:41:06+00:00 | Vulnerability · Source |
| CVE-2018-18459 | suse_vex | SUSE CVE CVE-2018-18459 | known not affected: 381 | 2026-07-31T01:41:04+00:00 | Vulnerability · Source |
| CVE-2018-18510 | suse_vex | SUSE CVE CVE-2018-18510 | known not affected: 64 | 2026-07-31T01:41:02+00:00 | Vulnerability · Source |
| CVE-2018-18606 | suse_vex | SUSE CVE CVE-2018-18606 | known affected: 448 recommended: 485 | 2026-07-31T01:41:00+00:00 | Vulnerability · Source |
| CVE-2018-19519 | suse_vex | SUSE CVE CVE-2018-19519 | known affected: 326 known not affected: 6 recommended: 148 | 2026-07-31T01:40:56+00:00 | Vulnerability · Source |
| CVE-2018-19962 | suse_vex | SUSE CVE CVE-2018-19962 | known affected: 68 known not affected: 32 recommended: 457 | 2026-07-31T01:40:52+00:00 | Vulnerability · Source |
| CVE-2018-19963 | suse_vex | SUSE CVE CVE-2018-19963 | known affected: 356 known not affected: 139 recommended: 369 | 2026-07-31T01:40:50+00:00 | Vulnerability · Source |
| CVE-2018-21008 | suse_vex | SUSE CVE CVE-2018-21008 | known not affected: 94 recommended: 803 | 2026-07-31T01:40:44+00:00 | Vulnerability · Source |
| CVE-2018-1000140 | suse_vex | SUSE CVE CVE-2018-1000140 | known affected: 1 known not affected: 70 recommended: 132 | 2026-07-31T01:40:39+00:00 | Vulnerability · Source |
| CVE-2018-1000808 | suse_vex | SUSE CVE CVE-2018-1000808 | known affected: 18 known not affected: 116 recommended: 660 | 2026-07-31T01:40:37+00:00 | Vulnerability · Source |
| CVE-2019-0197 | suse_vex | SUSE CVE CVE-2019-0197 | known affected: 111 known not affected: 65 recommended: 212 | 2026-07-31T01:40:35+00:00 | Vulnerability · Source |
| CVE-2019-0227 | suse_vex | SUSE CVE CVE-2019-0227 | known not affected: 23 | 2026-07-31T01:40:34+00:00 | Vulnerability · Source |
| CVE-2019-1354 | suse_vex | SUSE CVE CVE-2019-1354 | known affected: 65 known not affected: 56 recommended: 1016 | 2026-07-31T01:40:32+00:00 | Vulnerability · Source |
| CVE-2019-2182 | suse_vex | SUSE CVE CVE-2019-2182 | known not affected: 199 | 2026-07-31T01:40:30+00:00 | Vulnerability · Source |
| CVE-2019-2842 | suse_vex | SUSE CVE CVE-2019-2842 | known affected: 17 recommended: 399 | 2026-07-31T01:40:26+00:00 | Vulnerability · Source |
| CVE-2019-2973 | suse_vex | SUSE CVE CVE-2019-2973 | known affected: 525 recommended: 1129 | 2026-07-31T01:40:24+00:00 | Vulnerability · Source |
| CVE-2019-2987 | suse_vex | SUSE CVE CVE-2019-2987 | known affected: 525 recommended: 704 | 2026-07-31T01:40:23+00:00 | Vulnerability · Source |
| CVE-2019-3840 | suse_vex | SUSE CVE CVE-2019-3840 | known affected: 42 known not affected: 128 recommended: 764 | 2026-07-31T01:40:18+00:00 | Vulnerability · Source |
| CVE-2019-3887 | suse_vex | SUSE CVE CVE-2019-3887 | known not affected: 437 recommended: 26 | 2026-07-31T01:40:17+00:00 | Vulnerability · Source |
| CVE-2019-5849 | suse_vex | SUSE CVE CVE-2019-5849 | known not affected: 97 recommended: 9 | 2026-07-31T01:40:15+00:00 | Vulnerability · Source |
| CVE-2019-6229 | suse_vex | SUSE CVE CVE-2019-6229 | known not affected: 82 recommended: 995 | 2026-07-31T01:40:13+00:00 | Vulnerability · Source |
| CVE-2019-7308 | suse_vex | SUSE CVE CVE-2019-7308 | known affected: 19 known not affected: 347 recommended: 417 | 2026-07-31T01:40:11+00:00 | Vulnerability · Source |
| CVE-2019-7663 | suse_vex | SUSE CVE CVE-2019-7663 | known affected: 394 known not affected: 21 recommended: 260 | 2026-07-31T01:40:07+00:00 | Vulnerability · Source |
| CVE-2019-8609 | suse_vex | SUSE CVE CVE-2019-8609 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-31T01:40:05+00:00 | Vulnerability · Source |
| CVE-2019-8610 | suse_vex | SUSE CVE CVE-2019-8610 | known affected: 153 known not affected: 82 recommended: 298 | 2026-07-31T01:40:03+00:00 | Vulnerability · Source |
| CVE-2019-8743 | suse_vex | SUSE CVE CVE-2019-8743 | known not affected: 10 recommended: 1090 | 2026-07-31T01:40:01+00:00 | Vulnerability · Source |
| CVE-2019-8921 | suse_vex | SUSE CVE CVE-2019-8921 | known affected: 6 known not affected: 80 recommended: 98 | 2026-07-31T01:39:59+00:00 | Vulnerability · Source |
| CVE-2019-9325 | suse_vex | SUSE CVE CVE-2019-9325 | known affected: 21 known not affected: 55 recommended: 163 | 2026-07-31T01:39:57+00:00 | Vulnerability · Source |
| CVE-2019-9475 | suse_vex | SUSE CVE CVE-2019-9475 | known not affected: 360 | 2026-07-31T01:39:56+00:00 | Vulnerability · Source |
| CVE-2019-10082 | suse_vex | SUSE CVE CVE-2019-10082 | known affected: 516 known not affected: 88 recommended: 382 | 2026-07-31T01:39:52+00:00 | Vulnerability · Source |
| CVE-2019-10897 | suse_vex | SUSE CVE CVE-2019-10897 | known affected: 80 recommended: 677 | 2026-07-31T01:39:50+00:00 | Vulnerability · Source |
| 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-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-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-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 |