VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291913 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-12643 | suse_vex | SUSE CVE CVE-2017-12643 | known affected: 94 recommended: 186 | 2026-07-31T01:44:43+00:00 | Vulnerability · Source |
| CVE-2017-12814 | suse_vex | SUSE CVE CVE-2017-12814 | known not affected: 303 recommended: 15 | 2026-07-31T01:44:41+00:00 | Vulnerability · Source |
| CVE-2017-12902 | suse_vex | SUSE CVE CVE-2017-12902 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:38+00:00 | Vulnerability · Source |
| CVE-2017-13016 | suse_vex | SUSE CVE CVE-2017-13016 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-31T01:44:31+00:00 | Vulnerability · Source |
| CVE-2017-13039 | suse_vex | SUSE CVE CVE-2017-13039 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-31T01:44:30+00:00 | Vulnerability · Source |
| CVE-2017-13133 | suse_vex | SUSE CVE CVE-2017-13133 | known not affected: 14 recommended: 172 | 2026-07-31T01:44:27+00:00 | Vulnerability · Source |
| CVE-2017-13730 | suse_vex | SUSE CVE CVE-2017-13730 | known affected: 157 recommended: 201 | 2026-07-31T01:44:25+00:00 | Vulnerability · Source |
| CVE-2017-13757 | suse_vex | SUSE CVE CVE-2017-13757 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:23+00:00 | Vulnerability · Source |
| CVE-2017-14064 | suse_vex | SUSE CVE CVE-2017-14064 | known not affected: 94 recommended: 98 | 2026-07-31T01:44:21+00:00 | Vulnerability · Source |
| CVE-2017-14519 | suse_vex | SUSE CVE CVE-2017-14519 | known affected: 12 known not affected: 341 | 2026-07-31T01:44:19+00:00 | Vulnerability · Source |
| CVE-2017-14617 | suse_vex | SUSE CVE CVE-2017-14617 | known affected: 50 known not affected: 55 recommended: 102 | 2026-07-31T01:44:17+00:00 | Vulnerability · Source |
| CVE-2017-14626 | suse_vex | SUSE CVE CVE-2017-14626 | known affected: 10 known not affected: 144 | 2026-07-31T01:44:16+00:00 | Vulnerability · Source |
| CVE-2017-14974 | suse_vex | SUSE CVE CVE-2017-14974 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-31T01:44:14+00:00 | Vulnerability · Source |
| CVE-2017-15116 | suse_vex | SUSE CVE CVE-2017-15116 | known not affected: 261 recommended: 12 | 2026-07-31T01:44:12+00:00 | Vulnerability · Source |
| CVE-2017-15298 | suse_vex | SUSE CVE CVE-2017-15298 | known affected: 130 recommended: 762 | 2026-07-31T01:44:10+00:00 | Vulnerability · Source |
| CVE-2017-15652 | suse_vex | SUSE CVE CVE-2017-15652 | known not affected: 233 | 2026-07-31T01:44:07+00:00 | Vulnerability · Source |
| CVE-2017-15715 | suse_vex | SUSE CVE CVE-2017-15715 | known affected: 92 known not affected: 39 recommended: 127 | 2026-07-31T01:44:03+00:00 | Vulnerability · Source |
| CVE-2017-15908 | suse_vex | SUSE CVE CVE-2017-15908 | known affected: 451 known not affected: 240 recommended: 1131 | 2026-07-31T01:43:59+00:00 | Vulnerability · Source |
| CVE-2017-16529 | suse_vex | SUSE CVE CVE-2017-16529 | known not affected: 352 recommended: 485 | 2026-07-31T01:43:56+00:00 | Vulnerability · Source |
| CVE-2017-16531 | suse_vex | SUSE CVE CVE-2017-16531 | known not affected: 319 recommended: 496 | 2026-07-31T01:43:54+00:00 | Vulnerability · Source |
| CVE-2017-16818 | suse_vex | SUSE CVE CVE-2017-16818 | known not affected: 199 recommended: 1177 | 2026-07-31T01:43:50+00:00 | Vulnerability · Source |
| CVE-2017-16899 | suse_vex | SUSE CVE CVE-2017-16899 | known affected: 16 known not affected: 16 recommended: 40 | 2026-07-31T01:43:48+00:00 | Vulnerability · Source |
| CVE-2017-16911 | suse_vex | SUSE CVE CVE-2017-16911 | known affected: 21 known not affected: 215 recommended: 496 | 2026-07-31T01:43:46+00:00 | Vulnerability · Source |
| CVE-2017-17884 | suse_vex | SUSE CVE CVE-2017-17884 | known affected: 94 recommended: 186 | 2026-07-31T01:43:43+00:00 | Vulnerability · Source |
| CVE-2017-18220 | suse_vex | SUSE CVE CVE-2017-18220 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-31T01:43:40+00:00 | Vulnerability · Source |
| 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-18640 | suse_vex | SUSE CVE CVE-2017-18640 | known affected: 408 recommended: 59 | 2026-07-31T01:43:34+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-1068 | suse_vex | SUSE CVE CVE-2018-1068 | known affected: 38 known not affected: 274 recommended: 708 | 2026-07-31T01:43:13+00:00 | Vulnerability · Source |
| CVE-2018-1128 | suse_vex | SUSE CVE CVE-2018-1128 | known affected: 36 known not affected: 243 recommended: 1819 | 2026-07-31T01:43:11+00:00 | Vulnerability · Source |
| CVE-2018-2599 | suse_vex | SUSE CVE CVE-2018-2599 | known affected: 73 known not affected: 263 recommended: 730 | 2026-07-31T01:43:09+00:00 | Vulnerability · Source |
| CVE-2018-3174 | suse_vex | SUSE CVE CVE-2018-3174 | known affected: 106 known not affected: 27 recommended: 633 | 2026-07-31T01:43:07+00:00 | Vulnerability · Source |
| CVE-2018-4129 | suse_vex | SUSE CVE CVE-2018-4129 | known affected: 116 known not affected: 169 recommended: 903 | 2026-07-31T01:43:03+00:00 | Vulnerability · Source |
| CVE-2018-4133 | suse_vex | SUSE CVE CVE-2018-4133 | known affected: 116 known not affected: 169 recommended: 915 | 2026-07-31T01:43:01+00:00 | Vulnerability · Source |
| CVE-2018-4262 | suse_vex | SUSE CVE CVE-2018-4262 | known affected: 108 known not affected: 82 recommended: 957 | 2026-07-31T01:42:57+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-5146 | suse_vex | SUSE CVE CVE-2018-5146 | known affected: 421 known not affected: 229 recommended: 804 | 2026-07-31T01:42:49+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-5390 | suse_vex | SUSE CVE CVE-2018-5390 | known affected: 173 known not affected: 236 recommended: 867 | 2026-07-31T01:42:42+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-5740 | suse_vex | SUSE CVE CVE-2018-5740 | known affected: 102 known not affected: 4 recommended: 979 | 2026-07-31T01:42:37+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 |