VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-18231 | suse_vex | SUSE CVE CVE-2017-18231 | known affected: 10 known not affected: 144 | 2026-07-31T01:43:38+00:00 | Vulnerability · Source |
| CVE-2017-18271 | suse_vex | SUSE CVE CVE-2017-18271 | recommended: 184 | 2026-07-31T01:43:37+00:00 | Vulnerability · Source |
| CVE-2017-18552 | suse_vex | SUSE CVE CVE-2017-18552 | known not affected: 205 | 2026-07-31T01:43:35+00:00 | Vulnerability · Source |
| CVE-2017-1000200 | suse_vex | SUSE CVE CVE-2017-1000200 | known not affected: 9 | 2026-07-31T01:43:29+00:00 | Vulnerability · Source |
| CVE-2017-1000250 | suse_vex | SUSE CVE CVE-2017-1000250 | known affected: 9 known not affected: 122 recommended: 59 | 2026-07-31T01:43:28+00:00 | Vulnerability · Source |
| CVE-2017-1000371 | suse_vex | SUSE CVE CVE-2017-1000371 | known not affected: 228 | 2026-07-31T01:43:25+00:00 | Vulnerability · Source |
| CVE-2017-1000379 | suse_vex | SUSE CVE CVE-2017-1000379 | known not affected: 71 | 2026-07-31T01:43:23+00:00 | Vulnerability · Source |
| CVE-2018-5111 | suse_vex | SUSE CVE CVE-2018-5111 | known affected: 1 known not affected: 42 recommended: 12 | 2026-07-31T01:42:54+00:00 | Vulnerability · Source |
| CVE-2018-5126 | suse_vex | SUSE CVE CVE-2018-5126 | known affected: 1 known not affected: 54 recommended: 12 | 2026-07-31T01:42:52+00:00 | Vulnerability · Source |
| CVE-2018-5128 | suse_vex | SUSE CVE CVE-2018-5128 | known affected: 1 known not affected: 54 recommended: 12 | 2026-07-31T01:42:51+00:00 | Vulnerability · Source |
| CVE-2018-5357 | suse_vex | SUSE CVE CVE-2018-5357 | known not affected: 540 recommended: 136 | 2026-07-31T01:42:46+00:00 | Vulnerability · Source |
| CVE-2018-5388 | suse_vex | SUSE CVE CVE-2018-5388 | known affected: 26 recommended: 444 | 2026-07-31T01:42:44+00:00 | Vulnerability · Source |
| CVE-2018-5709 | suse_vex | SUSE CVE CVE-2018-5709 | known not affected: 215 | 2026-07-31T01:42:41+00:00 | Vulnerability · Source |
| CVE-2018-5953 | suse_vex | SUSE CVE CVE-2018-5953 | known not affected: 190 | 2026-07-31T01:42:35+00:00 | Vulnerability · Source |
| CVE-2018-6080 | suse_vex | SUSE CVE CVE-2018-6080 | recommended: 10 | 2026-07-31T01:42:34+00:00 | Vulnerability · Source |
| CVE-2018-7174 | suse_vex | SUSE CVE CVE-2018-7174 | known not affected: 381 | 2026-07-31T01:42:24+00:00 | Vulnerability · Source |
| CVE-2018-9306 | suse_vex | SUSE CVE CVE-2018-9306 | known affected: 4 known not affected: 53 recommended: 8 | 2026-07-31T01:42:06+00:00 | Vulnerability · Source |
| CVE-2018-10804 | suse_vex | SUSE CVE CVE-2018-10804 | known affected: 6 known not affected: 36 recommended: 134 | 2026-07-31T01:42:04+00:00 | Vulnerability · Source |
| CVE-2018-11251 | suse_vex | SUSE CVE CVE-2018-11251 | known not affected: 2 recommended: 136 | 2026-07-31T01:42:02+00:00 | Vulnerability · Source |
| CVE-2018-12613 | suse_vex | SUSE CVE CVE-2018-12613 | known affected: 71 known not affected: 391 recommended: 5 | 2026-07-31T01:41:49+00:00 | Vulnerability · Source |
| CVE-2018-14348 | suse_vex | SUSE CVE CVE-2018-14348 | known affected: 395 recommended: 171 | 2026-07-31T01:41:45+00:00 | Vulnerability · Source |
| CVE-2018-16470 | suse_vex | SUSE CVE CVE-2018-16470 | known not affected: 38 recommended: 114 | 2026-07-31T01:41:27+00:00 | Vulnerability · Source |
| CVE-2018-16888 | suse_vex | SUSE CVE CVE-2018-16888 | recommended: 10 | 2026-07-31T01:41:18+00:00 | Vulnerability · Source |
| 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-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-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-2182 | suse_vex | SUSE CVE CVE-2019-2182 | known not affected: 199 | 2026-07-31T01:40:30+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-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-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-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-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-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-14290 | suse_vex | SUSE CVE CVE-2019-14290 | known not affected: 895 | 2026-07-31T01:39:14+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-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-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-20477 | suse_vex | SUSE CVE CVE-2019-20477 | known not affected: 102 recommended: 42 | 2026-07-31T01:38:43+00:00 | Vulnerability · Source |