VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294140 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-10053 | suse_vex | SUSE CVE CVE-2016-10053 | known not affected: 99 | 2026-07-26T00:49:57+00:00 | Vulnerability · Source |
| CVE-2016-10056 | suse_vex | SUSE CVE CVE-2016-10056 | known affected: 10 known not affected: 113 | 2026-07-26T00:49:55+00:00 | Vulnerability · Source |
| CVE-2016-10062 | suse_vex | SUSE CVE CVE-2016-10062 | known affected: 1 known not affected: 14 recommended: 168 | 2026-07-26T00:49:54+00:00 | Vulnerability · Source |
| CVE-2016-10063 | suse_vex | SUSE CVE CVE-2016-10063 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:49:52+00:00 | Vulnerability · Source |
| CVE-2016-10068 | suse_vex | SUSE CVE CVE-2016-10068 | known affected: 1 recommended: 218 | 2026-07-26T00:49:51+00:00 | Vulnerability · Source |
| CVE-2016-10069 | suse_vex | SUSE CVE CVE-2016-10069 | known not affected: 49 recommended: 168 | 2026-07-26T00:49:49+00:00 | Vulnerability · Source |
| CVE-2016-10094 | suse_vex | SUSE CVE CVE-2016-10094 | known affected: 62 known not affected: 13 recommended: 289 | 2026-07-26T00:49:41+00:00 | Vulnerability · Source |
| CVE-2016-10109 | suse_vex | SUSE CVE CVE-2016-10109 | known affected: 394 known not affected: 13 recommended: 339 | 2026-07-26T00:49:38+00:00 | Vulnerability · Source |
| CVE-2016-10145 | suse_vex | SUSE CVE CVE-2016-10145 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:49:36+00:00 | Vulnerability · Source |
| CVE-2016-10147 | suse_vex | SUSE CVE CVE-2016-10147 | known affected: 14 known not affected: 421 recommended: 12 | 2026-07-26T00:49:35+00:00 | Vulnerability · Source |
| CVE-2016-10171 | suse_vex | SUSE CVE CVE-2016-10171 | known affected: 30 recommended: 57 | 2026-07-26T00:49:27+00:00 | Vulnerability · Source |
| CVE-2016-10209 | suse_vex | SUSE CVE CVE-2016-10209 | known affected: 24 known not affected: 16 recommended: 25 | 2026-07-26T00:49:25+00:00 | Vulnerability · Source |
| CVE-2016-10254 | suse_vex | SUSE CVE CVE-2016-10254 | known affected: 136 recommended: 172 | 2026-07-26T00:48:50+00:00 | Vulnerability · Source |
| CVE-2016-10328 | suse_vex | SUSE CVE CVE-2016-10328 | known affected: 9 known not affected: 63 recommended: 22 | 2026-07-26T00:48:47+00:00 | Vulnerability · Source |
| CVE-2017-0605 | suse_vex | SUSE CVE CVE-2017-0605 | known not affected: 64 | 2026-07-26T00:48:35+00:00 | Vulnerability · Source |
| CVE-2017-0627 | suse_vex | SUSE CVE CVE-2017-0627 | known not affected: 64 | 2026-07-26T00:48:33+00:00 | Vulnerability · Source |
| CVE-2017-0630 | suse_vex | SUSE CVE CVE-2017-0630 | known not affected: 64 | 2026-07-26T00:48:32+00:00 | Vulnerability · Source |
| CVE-2017-1376 | suse_vex | SUSE CVE CVE-2017-1376 | known affected: 72 known not affected: 65 | 2026-07-26T00:48:27+00:00 | Vulnerability · Source |
| CVE-2017-2581 | suse_vex | SUSE CVE CVE-2017-2581 | known affected: 16 recommended: 78 | 2026-07-26T00:48:15+00:00 | Vulnerability · Source |
| CVE-2017-2618 | suse_vex | SUSE CVE CVE-2017-2618 | known not affected: 781 recommended: 12 | 2026-07-26T00:48:11+00:00 | Vulnerability · Source |
| CVE-2017-2628 | suse_vex | SUSE CVE CVE-2017-2628 | known not affected: 63 | 2026-07-26T00:48:07+00:00 | Vulnerability · Source |
| CVE-2017-2634 | suse_vex | SUSE CVE CVE-2017-2634 | known not affected: 54 | 2026-07-26T00:48:05+00:00 | Vulnerability · Source |
| CVE-2017-2669 | suse_vex | SUSE CVE CVE-2017-2669 | recommended: 82 | 2026-07-26T00:48:02+00:00 | Vulnerability · Source |
| CVE-2017-2671 | suse_vex | SUSE CVE CVE-2017-2671 | known affected: 14 known not affected: 320 recommended: 335 | 2026-07-26T00:48:00+00:00 | Vulnerability · Source |
| CVE-2017-3135 | suse_vex | SUSE CVE CVE-2017-3135 | known affected: 377 known not affected: 387 recommended: 958 | 2026-07-26T00:47:57+00:00 | Vulnerability · Source |
| CVE-2017-3139 | suse_vex | SUSE CVE CVE-2017-3139 | known affected: 63 known not affected: 118 | 2026-07-26T00:47:54+00:00 | Vulnerability · Source |
| CVE-2017-3256 | suse_vex | SUSE CVE CVE-2017-3256 | known not affected: 93 | 2026-07-26T00:47:43+00:00 | Vulnerability · Source |
| CVE-2017-3305 | suse_vex | SUSE CVE CVE-2017-3305 | known not affected: 93 recommended: 28 | 2026-07-26T00:47:37+00:00 | Vulnerability · Source |
| CVE-2017-3452 | suse_vex | SUSE CVE CVE-2017-3452 | known affected: 35 known not affected: 66 | 2026-07-26T00:47:28+00:00 | Vulnerability · Source |
| CVE-2017-3453 | suse_vex | SUSE CVE CVE-2017-3453 | known affected: 35 known not affected: 104 recommended: 639 | 2026-07-26T00:47:26+00:00 | Vulnerability · Source |
| CVE-2017-3600 | suse_vex | SUSE CVE CVE-2017-3600 | known affected: 35 known not affected: 104 recommended: 36 | 2026-07-26T00:47:18+00:00 | Vulnerability · Source |
| CVE-2017-3633 | suse_vex | SUSE CVE CVE-2017-3633 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:15+00:00 | Vulnerability · Source |
| CVE-2017-3637 | suse_vex | SUSE CVE CVE-2017-3637 | known affected: 1 known not affected: 64 | 2026-07-26T00:47:14+00:00 | Vulnerability · Source |
| CVE-2017-3738 | suse_vex | SUSE CVE CVE-2017-3738 | known affected: 320 known not affected: 398 recommended: 972 | 2026-07-26T00:46:49+00:00 | Vulnerability · Source |
| CVE-2017-5130 | suse_vex | SUSE CVE CVE-2017-5130 | recommended: 116 | 2026-07-26T00:46:46+00:00 | Vulnerability · Source |
| CVE-2017-5335 | suse_vex | SUSE CVE CVE-2017-5335 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-26T00:46:41+00:00 | Vulnerability · Source |
| CVE-2017-5341 | suse_vex | SUSE CVE CVE-2017-5341 | known affected: 320 recommended: 182 | 2026-07-26T00:46:40+00:00 | Vulnerability · Source |
| CVE-2017-5387 | suse_vex | SUSE CVE CVE-2017-5387 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5396 | suse_vex | SUSE CVE CVE-2017-5396 | known affected: 1 recommended: 416 | 2026-07-26T00:46:24+00:00 | Vulnerability · Source |
| CVE-2017-5425 | suse_vex | SUSE CVE CVE-2017-5425 | known affected: 1 | 2026-07-26T00:46:09+00:00 | Vulnerability · Source |
| CVE-2017-5426 | suse_vex | SUSE CVE CVE-2017-5426 | known affected: 1 recommended: 333 | 2026-07-26T00:46:08+00:00 | Vulnerability · Source |
| CVE-2017-5506 | suse_vex | SUSE CVE CVE-2017-5506 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:36+00:00 | Vulnerability · Source |
| CVE-2017-5508 | suse_vex | SUSE CVE CVE-2017-5508 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:35+00:00 | Vulnerability · Source |
| CVE-2017-5509 | suse_vex | SUSE CVE CVE-2017-5509 | known not affected: 113 | 2026-07-26T00:45:34+00:00 | Vulnerability · Source |
| CVE-2017-5510 | suse_vex | SUSE CVE CVE-2017-5510 | known not affected: 49 recommended: 168 | 2026-07-26T00:45:33+00:00 | Vulnerability · Source |
| CVE-2017-5511 | suse_vex | SUSE CVE CVE-2017-5511 | known affected: 1 recommended: 218 | 2026-07-26T00:45:31+00:00 | Vulnerability · Source |
| CVE-2017-5548 | suse_vex | SUSE CVE CVE-2017-5548 | known not affected: 34 | 2026-07-26T00:45:29+00:00 | Vulnerability · Source |
| CVE-2017-5577 | suse_vex | SUSE CVE CVE-2017-5577 | known affected: 12 known not affected: 258 recommended: 101 | 2026-07-26T00:45:24+00:00 | Vulnerability · Source |
| CVE-2017-5579 | suse_vex | SUSE CVE CVE-2017-5579 | known affected: 420 known not affected: 804 recommended: 1875 | 2026-07-26T00:45:21+00:00 | Vulnerability · Source |
| CVE-2017-5754 | suse_vex | SUSE CVE CVE-2017-5754 | known affected: 358 known not affected: 198 recommended: 2030 | 2026-07-26T00:45:06+00:00 | Vulnerability · Source |