VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292142 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-8309 | suse_vex | SUSE CVE CVE-2017-8309 | known affected: 340 known not affected: 191 recommended: 2256 | 2026-07-19T18:33:08+00:00 | Vulnerability · Source |
| CVE-2017-8393 | suse_vex | SUSE CVE CVE-2017-8393 | known affected: 436 known not affected: 185 recommended: 336 | 2026-07-19T18:33:03+00:00 | Vulnerability · Source |
| CVE-2017-8932 | suse_vex | SUSE CVE CVE-2017-8932 | known not affected: 147 recommended: 108 | 2026-07-19T18:33:00+00:00 | Vulnerability · Source |
| CVE-2017-10196 | suse_vex | SUSE CVE CVE-2017-10196 | known not affected: 42 | 2026-07-19T18:32:45+00:00 | Vulnerability · Source |
| CVE-2017-11108 | suse_vex | SUSE CVE CVE-2017-11108 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:36+00:00 | Vulnerability · Source |
| CVE-2017-11185 | suse_vex | SUSE CVE CVE-2017-11185 | known affected: 59 known not affected: 51 recommended: 374 | 2026-07-19T18:32:34+00:00 | Vulnerability · Source |
| CVE-2017-11625 | suse_vex | SUSE CVE CVE-2017-11625 | known affected: 2 known not affected: 33 recommended: 316 | 2026-07-19T18:32:21+00:00 | Vulnerability · Source |
| CVE-2017-12794 | suse_vex | SUSE CVE CVE-2017-12794 | known not affected: 3 recommended: 21 | 2026-07-19T18:32:11+00:00 | Vulnerability · Source |
| CVE-2017-13012 | suse_vex | SUSE CVE CVE-2017-13012 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:32:00+00:00 | Vulnerability · Source |
| CVE-2017-13028 | suse_vex | SUSE CVE CVE-2017-13028 | known affected: 334 known not affected: 24 recommended: 148 | 2026-07-19T18:31:56+00:00 | Vulnerability · Source |
| CVE-2017-13735 | suse_vex | SUSE CVE CVE-2017-13735 | known not affected: 49 recommended: 151 | 2026-07-19T18:31:43+00:00 | Vulnerability · Source |
| CVE-2017-16548 | suse_vex | SUSE CVE CVE-2017-16548 | known affected: 406 known not affected: 27 recommended: 86 | 2026-07-19T18:31:01+00:00 | Vulnerability · Source |
| CVE-2017-16997 | suse_vex | SUSE CVE CVE-2017-16997 | known affected: 369 known not affected: 266 recommended: 1165 | 2026-07-19T18:30:57+00:00 | Vulnerability · Source |
| CVE-2017-17521 | suse_vex | SUSE CVE CVE-2017-17521 | known not affected: 33 recommended: 20 | 2026-07-19T18:30:56+00:00 | Vulnerability · Source |
| CVE-2017-18922 | suse_vex | SUSE CVE CVE-2017-18922 | known affected: 22 known not affected: 3 recommended: 113 | 2026-07-19T18:30:51+00:00 | Vulnerability · Source |
| CVE-2017-1000116 | suse_vex | SUSE CVE CVE-2017-1000116 | known not affected: 24 recommended: 58 | 2026-07-19T18:30:48+00:00 | Vulnerability · Source |
| CVE-2018-0886 | suse_vex | SUSE CVE CVE-2018-0886 | recommended: 221 | 2026-07-19T18:30:35+00:00 | Vulnerability · Source |
| CVE-2018-3173 | suse_vex | SUSE CVE CVE-2018-3173 | known affected: 84 known not affected: 46 recommended: 430 | 2026-07-19T18:30:23+00:00 | Vulnerability · Source |
| CVE-2018-4096 | suse_vex | SUSE CVE CVE-2018-4096 | known affected: 135 known not affected: 87 recommended: 893 | 2026-07-19T18:30:17+00:00 | Vulnerability · Source |
| CVE-2018-4266 | suse_vex | SUSE CVE CVE-2018-4266 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:03+00:00 | Vulnerability · Source |
| CVE-2018-4278 | suse_vex | SUSE CVE CVE-2018-4278 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-19T18:30:01+00:00 | Vulnerability · Source |
| CVE-2018-5166 | suse_vex | SUSE CVE CVE-2018-5166 | known affected: 24 recommended: 74 | 2026-07-19T18:29:37+00:00 | Vulnerability · Source |
| CVE-2018-5175 | suse_vex | SUSE CVE CVE-2018-5175 | known affected: 24 recommended: 74 | 2026-07-19T18:29:34+00:00 | Vulnerability · Source |
| CVE-2018-5815 | suse_vex | SUSE CVE CVE-2018-5815 | known not affected: 18 recommended: 98 | 2026-07-19T18:29:26+00:00 | Vulnerability · Source |
| CVE-2018-6767 | suse_vex | SUSE CVE CVE-2018-6767 | known affected: 394 known not affected: 24 recommended: 227 | 2026-07-19T18:29:22+00:00 | Vulnerability · Source |
| CVE-2018-7536 | suse_vex | SUSE CVE CVE-2018-7536 | recommended: 23 | 2026-07-19T18:29:04+00:00 | Vulnerability · Source |
| CVE-2018-7537 | suse_vex | SUSE CVE CVE-2018-7537 | recommended: 23 | 2026-07-19T18:29:03+00:00 | Vulnerability · Source |
| CVE-2018-7550 | suse_vex | SUSE CVE CVE-2018-7550 | known affected: 57 known not affected: 376 recommended: 1774 | 2026-07-19T18:29:01+00:00 | Vulnerability · Source |
| CVE-2018-7999 | suse_vex | SUSE CVE CVE-2018-7999 | known affected: 394 known not affected: 78 recommended: 224 | 2026-07-19T18:28:59+00:00 | Vulnerability · Source |
| CVE-2018-8787 | suse_vex | SUSE CVE CVE-2018-8787 | recommended: 219 | 2026-07-19T18:28:56+00:00 | Vulnerability · Source |
| CVE-2018-8789 | suse_vex | SUSE CVE CVE-2018-8789 | recommended: 215 | 2026-07-19T18:28:55+00:00 | Vulnerability · Source |
| CVE-2018-10888 | suse_vex | SUSE CVE CVE-2018-10888 | known affected: 16 known not affected: 38 recommended: 163 | 2026-07-19T18:28:37+00:00 | Vulnerability · Source |
| CVE-2018-11712 | suse_vex | SUSE CVE CVE-2018-11712 | known affected: 93 known not affected: 100 recommended: 1271 | 2026-07-19T18:28:27+00:00 | Vulnerability · Source |
| CVE-2018-11813 | suse_vex | SUSE CVE CVE-2018-11813 | known affected: 429 recommended: 527 | 2026-07-19T18:28:25+00:00 | Vulnerability · Source |
| CVE-2018-12367 | suse_vex | SUSE CVE CVE-2018-12367 | known affected: 21 recommended: 105 | 2026-07-19T18:28:16+00:00 | Vulnerability · Source |
| CVE-2018-12371 | suse_vex | SUSE CVE CVE-2018-12371 | known affected: 21 recommended: 105 | 2026-07-19T18:28:15+00:00 | Vulnerability · Source |
| CVE-2018-14447 | suse_vex | SUSE CVE CVE-2018-14447 | known not affected: 52 recommended: 9 | 2026-07-19T18:27:58+00:00 | Vulnerability · Source |
| CVE-2018-14465 | suse_vex | SUSE CVE CVE-2018-14465 | known affected: 332 recommended: 143 | 2026-07-19T18:27:56+00:00 | Vulnerability · Source |
| CVE-2018-14721 | suse_vex | SUSE CVE CVE-2018-14721 | known affected: 29 recommended: 47 | 2026-07-19T18:27:48+00:00 | Vulnerability · Source |
| CVE-2018-16984 | suse_vex | SUSE CVE CVE-2018-16984 | recommended: 17 | 2026-07-19T18:27:15+00:00 | Vulnerability · Source |
| CVE-2018-19198 | suse_vex | SUSE CVE CVE-2018-19198 | recommended: 62 | 2026-07-19T18:26:52+00:00 | Vulnerability · Source |
| CVE-2018-19567 | suse_vex | SUSE CVE CVE-2018-19567 | known not affected: 85 recommended: 24 | 2026-07-19T18:26:47+00:00 | Vulnerability · Source |
| CVE-2018-19644 | suse_vex | SUSE CVE CVE-2018-19644 | recommended: 167 | 2026-07-19T18:26:44+00:00 | Vulnerability · Source |
| CVE-2018-19655 | suse_vex | SUSE CVE CVE-2018-19655 | known not affected: 85 recommended: 29 | 2026-07-19T18:26:43+00:00 | Vulnerability · Source |
| CVE-2018-19664 | suse_vex | SUSE CVE CVE-2018-19664 | known not affected: 172 recommended: 167 | 2026-07-19T18:26:42+00:00 | Vulnerability · Source |
| CVE-2018-19935 | suse_vex | SUSE CVE CVE-2018-19935 | known affected: 1080 known not affected: 1493 recommended: 2503 | 2026-07-19T18:26:38+00:00 | Vulnerability · Source |
| CVE-2018-20657 | suse_vex | SUSE CVE CVE-2018-20657 | known not affected: 163 recommended: 4 | 2026-07-19T18:26:22+00:00 | Vulnerability · Source |
| CVE-2018-20721 | suse_vex | SUSE CVE CVE-2018-20721 | recommended: 58 | 2026-07-19T18:26:18+00:00 | Vulnerability · Source |
| CVE-2019-2228 | suse_vex | SUSE CVE CVE-2019-2228 | recommended: 28 | 2026-07-19T18:25:55+00:00 | Vulnerability · Source |
| CVE-2019-2737 | suse_vex | SUSE CVE CVE-2019-2737 | known affected: 1 known not affected: 123 recommended: 912 | 2026-07-19T18:25:54+00:00 | Vulnerability · Source |