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-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-17681 | suse_vex | SUSE CVE CVE-2017-17681 | known not affected: 481 recommended: 130 | 2026-07-28T00:06:00+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-17840 | suse_vex | SUSE CVE CVE-2017-17840 | known affected: 1 known not affected: 97 recommended: 1 | 2026-07-28T00:05:55+00:00 | Vulnerability · Source |
| CVE-2017-17853 | suse_vex | SUSE CVE CVE-2017-17853 | known not affected: 174 recommended: 290 | 2026-07-28T00:05:54+00:00 | Vulnerability · Source |
| CVE-2017-18206 | suse_vex | SUSE CVE CVE-2017-18206 | known not affected: 49 recommended: 9 | 2026-07-28T00:05:52+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-18230 | suse_vex | SUSE CVE CVE-2017-18230 | known affected: 3 known not affected: 108 recommended: 14 | 2026-07-28T00:05:49+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-18258 | suse_vex | SUSE CVE CVE-2017-18258 | known affected: 58 known not affected: 66 recommended: 196 | 2026-07-28T00:05:46+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-2017-1000128 | suse_vex | SUSE CVE CVE-2017-1000128 | known affected: 2 known not affected: 88 recommended: 114 | 2026-07-28T00:05:41+00:00 | Vulnerability · Source |
| CVE-2018-0502 | suse_vex | SUSE CVE CVE-2018-0502 | known affected: 397 known not affected: 46 recommended: 85 | 2026-07-28T00:05:38+00:00 | Vulnerability · Source |
| CVE-2018-1052 | suse_vex | SUSE CVE CVE-2018-1052 | known affected: 36 known not affected: 776 recommended: 257 | 2026-07-28T00:05:35+00:00 | Vulnerability · Source |
| CVE-2018-1116 | suse_vex | SUSE CVE CVE-2018-1116 | known affected: 426 known not affected: 36 recommended: 351 | 2026-07-28T00:05:32+00:00 | Vulnerability · Source |
| CVE-2018-2797 | suse_vex | SUSE CVE CVE-2018-2797 | known affected: 481 known not affected: 160 recommended: 1051 | 2026-07-28T00:05:28+00:00 | Vulnerability · Source |
| CVE-2018-2799 | suse_vex | SUSE CVE CVE-2018-2799 | known affected: 489 known not affected: 160 recommended: 1051 | 2026-07-28T00:05:26+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-3156 | suse_vex | SUSE CVE CVE-2018-3156 | known affected: 91 known not affected: 46 recommended: 562 | 2026-07-28T00:05:22+00:00 | Vulnerability · Source |
| CVE-2018-3185 | suse_vex | SUSE CVE CVE-2018-3185 | known affected: 74 known not affected: 38 recommended: 433 | 2026-07-28T00:05:21+00:00 | Vulnerability · Source |
| CVE-2018-4261 | suse_vex | SUSE CVE CVE-2018-4261 | known affected: 76 known not affected: 82 recommended: 936 | 2026-07-28T00:05:15+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-4441 | suse_vex | SUSE CVE CVE-2018-4441 | known affected: 84 recommended: 977 | 2026-07-28T00:05:12+00:00 | Vulnerability · Source |
| CVE-2018-4443 | suse_vex | SUSE CVE CVE-2018-4443 | known affected: 76 recommended: 959 | 2026-07-28T00:05:10+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-5154 | suse_vex | SUSE CVE CVE-2018-5154 | known affected: 24 recommended: 443 | 2026-07-28T00:05:03+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-5732 | suse_vex | SUSE CVE CVE-2018-5732 | known affected: 391 known not affected: 96 recommended: 399 | 2026-07-28T00:04:58+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-6969 | suse_vex | SUSE CVE CVE-2018-6969 | known not affected: 3 | 2026-07-28T00:04:47+00:00 | Vulnerability · Source |
| CVE-2018-7254 | suse_vex | SUSE CVE CVE-2018-7254 | known affected: 394 known not affected: 85 recommended: 227 | 2026-07-28T00:04:45+00:00 | Vulnerability · Source |
| CVE-2018-7327 | suse_vex | SUSE CVE CVE-2018-7327 | known affected: 1 known not affected: 103 recommended: 559 | 2026-07-28T00:04:44+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-8106 | suse_vex | SUSE CVE CVE-2018-8106 | known not affected: 328 | 2026-07-28T00:04:39+00:00 | Vulnerability · Source |
| CVE-2018-9056 | suse_vex | SUSE CVE CVE-2018-9056 | known not affected: 209 | 2026-07-28T00:04:36+00:00 | Vulnerability · Source |
| CVE-2018-10536 | suse_vex | SUSE CVE CVE-2018-10536 | known not affected: 78 recommended: 172 | 2026-07-28T00:04:31+00:00 | Vulnerability · Source |
| CVE-2018-10846 | suse_vex | SUSE CVE CVE-2018-10846 | known affected: 386 known not affected: 21 recommended: 654 | 2026-07-28T00:04:28+00:00 | Vulnerability · Source |