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-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 |
| CVE-2018-6080 | suse_vex | SUSE CVE CVE-2018-6080 | recommended: 10 | 2026-07-31T01:42:34+00:00 | Vulnerability · Source |
| CVE-2018-6559 | suse_vex | SUSE CVE CVE-2018-6559 | known not affected: 407 | 2026-07-31T01:42:29+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-7208 | suse_vex | SUSE CVE CVE-2018-7208 | known affected: 394 known not affected: 244 recommended: 586 | 2026-07-31T01:42:22+00:00 | Vulnerability · Source |
| CVE-2018-7542 | suse_vex | SUSE CVE CVE-2018-7542 | known affected: 320 known not affected: 107 recommended: 411 | 2026-07-31T01:42:19+00:00 | Vulnerability · Source |
| CVE-2018-8043 | suse_vex | SUSE CVE CVE-2018-8043 | known not affected: 124 recommended: 423 | 2026-07-31T01:42:16+00:00 | Vulnerability · Source |
| CVE-2018-8778 | suse_vex | SUSE CVE CVE-2018-8778 | known affected: 320 known not affected: 2 recommended: 491 | 2026-07-31T01:42:15+00:00 | Vulnerability · Source |
| CVE-2018-8822 | suse_vex | SUSE CVE CVE-2018-8822 | known not affected: 223 recommended: 658 | 2026-07-31T01:42:13+00:00 | Vulnerability · Source |
| CVE-2018-8956 | suse_vex | SUSE CVE CVE-2018-8956 | known affected: 18 recommended: 107 | 2026-07-31T01:42:09+00:00 | Vulnerability · Source |
| CVE-2018-9260 | suse_vex | SUSE CVE CVE-2018-9260 | known affected: 89 known not affected: 115 recommended: 555 | 2026-07-31T01:42:08+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-11684 | suse_vex | SUSE CVE CVE-2018-11684 | known affected: 44 known not affected: 128 recommended: 316 | 2026-07-31T01:42:00+00:00 | Vulnerability · Source |
| CVE-2018-12386 | suse_vex | SUSE CVE CVE-2018-12386 | known affected: 1 recommended: 728 | 2026-07-31T01:41:51+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-13419 | suse_vex | SUSE CVE CVE-2018-13419 | known not affected: 62 | 2026-07-31T01:41:47+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-14567 | suse_vex | SUSE CVE CVE-2018-14567 | known affected: 418 known not affected: 6 recommended: 550 | 2026-07-31T01:41:43+00:00 | Vulnerability · Source |
| CVE-2018-14625 | suse_vex | SUSE CVE CVE-2018-14625 | known affected: 52 known not affected: 628 recommended: 430 | 2026-07-31T01:41:41+00:00 | Vulnerability · Source |
| CVE-2018-16152 | suse_vex | SUSE CVE CVE-2018-16152 | known affected: 26 known not affected: 135 recommended: 440 | 2026-07-31T01:41:32+00:00 | Vulnerability · Source |
| CVE-2018-16427 | suse_vex | SUSE CVE CVE-2018-16427 | known affected: 16 known not affected: 19 recommended: 106 | 2026-07-31T01:41:28+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-16882 | suse_vex | SUSE CVE CVE-2018-16882 | known affected: 394 known not affected: 144 recommended: 103 | 2026-07-31T01:41:21+00:00 | Vulnerability · Source |
| CVE-2018-16885 | suse_vex | SUSE CVE CVE-2018-16885 | known not affected: 239 recommended: 26 | 2026-07-31T01:41:19+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-17282 | suse_vex | SUSE CVE CVE-2018-17282 | known affected: 68 known not affected: 50 recommended: 161 | 2026-07-31T01:41:15+00:00 | Vulnerability · Source |