VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294121 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9060 | suse_vex | SUSE CVE CVE-2017-9060 | known not affected: 57 | 2026-07-28T00:07:49+00:00 | Vulnerability · Source |
| CVE-2017-9144 | suse_vex | SUSE CVE CVE-2017-9144 | recommended: 178 | 2026-07-28T00:07:47+00:00 | Vulnerability · Source |
| CVE-2017-9262 | suse_vex | SUSE CVE CVE-2017-9262 | known affected: 75 recommended: 180 | 2026-07-28T00:07:44+00:00 | Vulnerability · Source |
| CVE-2017-9375 | suse_vex | SUSE CVE CVE-2017-9375 | known affected: 13 recommended: 108 | 2026-07-28T00:07:40+00:00 | Vulnerability · Source |
| CVE-2017-10800 | suse_vex | SUSE CVE CVE-2017-10800 | recommended: 188 | 2026-07-28T00:07:28+00:00 | Vulnerability · Source |
| CVE-2017-10810 | suse_vex | SUSE CVE CVE-2017-10810 | known not affected: 277 recommended: 102 | 2026-07-28T00:07:26+00:00 | Vulnerability · Source |
| CVE-2017-10923 | suse_vex | SUSE CVE CVE-2017-10923 | known not affected: 46 | 2026-07-28T00:07:23+00:00 | Vulnerability · Source |
| CVE-2017-11449 | suse_vex | SUSE CVE CVE-2017-11449 | known affected: 75 recommended: 180 | 2026-07-28T00:07:20+00:00 | Vulnerability · Source |
| CVE-2017-11465 | suse_vex | SUSE CVE CVE-2017-11465 | known not affected: 48 | 2026-07-28T00:07:18+00:00 | Vulnerability · Source |
| CVE-2017-11544 | suse_vex | SUSE CVE CVE-2017-11544 | known affected: 13 known not affected: 22 | 2026-07-28T00:07:15+00:00 | Vulnerability · Source |
| CVE-2017-12136 | suse_vex | SUSE CVE CVE-2017-12136 | known affected: 325 known not affected: 41 recommended: 418 | 2026-07-28T00:07:12+00:00 | Vulnerability · Source |
| CVE-2017-12151 | suse_vex | SUSE CVE CVE-2017-12151 | known affected: 708 known not affected: 272 recommended: 3640 | 2026-07-28T00:07:08+00:00 | Vulnerability · Source |
| CVE-2017-12877 | suse_vex | SUSE CVE CVE-2017-12877 | known not affected: 220 | 2026-07-28T00:06:58+00:00 | Vulnerability · Source |
| CVE-2017-13145 | suse_vex | SUSE CVE CVE-2017-13145 | known affected: 5 known not affected: 56 | 2026-07-28T00:06:42+00:00 | Vulnerability · Source |
| CVE-2017-14497 | suse_vex | SUSE CVE CVE-2017-14497 | known not affected: 517 | 2026-07-28T00:06:30+00:00 | Vulnerability · Source |
| CVE-2017-14533 | suse_vex | SUSE CVE CVE-2017-14533 | recommended: 166 | 2026-07-28T00:06:29+00:00 | Vulnerability · Source |
| CVE-2017-14624 | suse_vex | SUSE CVE CVE-2017-14624 | known affected: 5 known not affected: 124 | 2026-07-28T00:06:28+00:00 | Vulnerability · Source |
| CVE-2017-14970 | suse_vex | SUSE CVE CVE-2017-14970 | known affected: 2 known not affected: 20 recommended: 16 | 2026-07-28T00:06:25+00:00 | Vulnerability · Source |
| CVE-2017-15016 | suse_vex | SUSE CVE CVE-2017-15016 | known affected: 75 recommended: 180 | 2026-07-28T00:06:24+00:00 | Vulnerability · Source |
| CVE-2017-15706 | suse_vex | SUSE CVE CVE-2017-15706 | known affected: 37 known not affected: 67 recommended: 108 | 2026-07-28T00:06:14+00:00 | Vulnerability · Source |
| CVE-2017-15994 | suse_vex | SUSE CVE CVE-2017-15994 | known affected: 1 known not affected: 10 | 2026-07-28T00:06:11+00:00 | Vulnerability · Source |
| CVE-2017-16546 | suse_vex | SUSE CVE CVE-2017-16546 | known affected: 75 recommended: 180 | 2026-07-28T00:06:09+00:00 | Vulnerability · Source |
| CVE-2017-16996 | suse_vex | SUSE CVE CVE-2017-16996 | known not affected: 174 recommended: 290 | 2026-07-28T00:06:06+00:00 | Vulnerability · Source |
| CVE-2017-17434 | suse_vex | SUSE CVE CVE-2017-17434 | known affected: 11 known not affected: 3 recommended: 16 | 2026-07-28T00:06:04+00:00 | Vulnerability · Source |
| CVE-2017-17563 | suse_vex | SUSE CVE CVE-2017-17563 | known affected: 26 known not affected: 31 recommended: 140 | 2026-07-28T00:06:01+00:00 | Vulnerability · Source |
| CVE-2017-17742 | suse_vex | SUSE CVE CVE-2017-17742 | known affected: 308 recommended: 478 | 2026-07-28T00:05:58+00:00 | Vulnerability · Source |
| CVE-2017-17807 | suse_vex | SUSE CVE CVE-2017-17807 | known affected: 7 known not affected: 438 recommended: 13 | 2026-07-28T00:05:56+00:00 | Vulnerability · Source |
| CVE-2017-18222 | suse_vex | SUSE CVE CVE-2017-18222 | known not affected: 441 | 2026-07-28T00:05:50+00:00 | Vulnerability · Source |
| CVE-2017-18252 | suse_vex | SUSE CVE CVE-2017-18252 | known affected: 79 known not affected: 14 recommended: 166 | 2026-07-28T00:05:48+00:00 | Vulnerability · Source |
| CVE-2017-18272 | suse_vex | SUSE CVE CVE-2017-18272 | known not affected: 47 | 2026-07-28T00:05:45+00:00 | Vulnerability · Source |
| CVE-2018-2825 | suse_vex | SUSE CVE CVE-2018-2825 | known affected: 387 known not affected: 212 recommended: 561 | 2026-07-28T00:05:24+00:00 | Vulnerability · Source |
| CVE-2018-4263 | suse_vex | SUSE CVE CVE-2018-4263 | known affected: 84 known not affected: 82 recommended: 942 | 2026-07-28T00:05:14+00:00 | Vulnerability · Source |
| CVE-2018-5090 | suse_vex | SUSE CVE CVE-2018-5090 | known affected: 1 known not affected: 34 recommended: 12 | 2026-07-28T00:05:09+00:00 | Vulnerability · Source |
| CVE-2018-5110 | suse_vex | SUSE CVE CVE-2018-5110 | known affected: 1 known not affected: 34 recommended: 12 | 2026-07-28T00:05:07+00:00 | Vulnerability · Source |
| CVE-2018-5141 | suse_vex | SUSE CVE CVE-2018-5141 | known affected: 1 known not affected: 40 recommended: 12 | 2026-07-28T00:05:06+00:00 | Vulnerability · Source |
| CVE-2018-5142 | suse_vex | SUSE CVE CVE-2018-5142 | known affected: 1 known not affected: 40 recommended: 12 | 2026-07-28T00:05:04+00:00 | Vulnerability · Source |
| CVE-2018-5246 | suse_vex | SUSE CVE CVE-2018-5246 | recommended: 166 | 2026-07-28T00:05:01+00:00 | Vulnerability · Source |
| CVE-2018-5383 | suse_vex | SUSE CVE CVE-2018-5383 | known not affected: 48 recommended: 48 | 2026-07-28T00:05:00+00:00 | Vulnerability · Source |
| CVE-2018-6063 | suse_vex | SUSE CVE CVE-2018-6063 | recommended: 10 | 2026-07-28T00:04:55+00:00 | Vulnerability · Source |
| CVE-2018-6836 | suse_vex | SUSE CVE CVE-2018-6836 | known not affected: 395 | 2026-07-28T00:04:52+00:00 | Vulnerability · Source |
| CVE-2018-6871 | suse_vex | SUSE CVE CVE-2018-6871 | known not affected: 196 recommended: 3958 | 2026-07-28T00:04:50+00:00 | Vulnerability · Source |
| CVE-2018-7328 | suse_vex | SUSE CVE CVE-2018-7328 | known affected: 1 known not affected: 115 recommended: 565 | 2026-07-28T00:04:43+00:00 | Vulnerability · Source |
| CVE-2018-8105 | suse_vex | SUSE CVE CVE-2018-8105 | known not affected: 328 | 2026-07-28T00:04:41+00:00 | Vulnerability · Source |
| CVE-2018-11355 | suse_vex | SUSE CVE CVE-2018-11355 | known affected: 70 recommended: 842 | 2026-07-28T00:04:15+00:00 | Vulnerability · Source |
| CVE-2018-14362 | suse_vex | SUSE CVE CVE-2018-14362 | known affected: 27 recommended: 199 | 2026-07-28T00:04:05+00:00 | Vulnerability · Source |
| CVE-2018-14423 | suse_vex | SUSE CVE CVE-2018-14423 | recommended: 325 | 2026-07-28T00:04:01+00:00 | Vulnerability · Source |
| CVE-2018-16588 | suse_vex | SUSE CVE CVE-2018-16588 | known affected: 10 known not affected: 18 recommended: 1 | 2026-07-28T00:03:41+00:00 | Vulnerability · Source |
| CVE-2018-16881 | suse_vex | SUSE CVE CVE-2018-16881 | known affected: 412 known not affected: 107 recommended: 104 | 2026-07-28T00:03:37+00:00 | Vulnerability · Source |
| CVE-2018-17965 | suse_vex | SUSE CVE CVE-2018-17965 | known affected: 1 known not affected: 46 recommended: 148 | 2026-07-28T00:03:32+00:00 | Vulnerability · Source |
| CVE-2018-18016 | suse_vex | SUSE CVE CVE-2018-18016 | known affected: 1 recommended: 284 | 2026-07-28T00:03:29+00:00 | Vulnerability · Source |