VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291994 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-9754 | suse_vex | SUSE CVE CVE-2017-9754 | known affected: 8 known not affected: 42 | 2026-07-26T00:38:23+00:00 | Vulnerability · Source |
| CVE-2017-9766 | suse_vex | SUSE CVE CVE-2017-9766 | known affected: 86 recommended: 162 | 2026-07-26T00:38:20+00:00 | Vulnerability · Source |
| CVE-2017-9775 | suse_vex | SUSE CVE CVE-2017-9775 | known affected: 60 known not affected: 39 recommended: 161 | 2026-07-26T00:38:18+00:00 | Vulnerability · Source |
| CVE-2017-9778 | suse_vex | SUSE CVE CVE-2017-9778 | known not affected: 64 | 2026-07-26T00:38:17+00:00 | Vulnerability · Source |
| CVE-2017-9788 | suse_vex | SUSE CVE CVE-2017-9788 | known not affected: 1 recommended: 160 | 2026-07-26T00:38:16+00:00 | Vulnerability · Source |
| CVE-2017-9865 | suse_vex | SUSE CVE CVE-2017-9865 | known affected: 60 known not affected: 39 recommended: 95 | 2026-07-26T00:38:13+00:00 | Vulnerability · Source |
| CVE-2017-9936 | suse_vex | SUSE CVE CVE-2017-9936 | known affected: 403 known not affected: 197 recommended: 232 | 2026-07-26T00:38:12+00:00 | Vulnerability · Source |
| CVE-2017-9954 | suse_vex | SUSE CVE CVE-2017-9954 | known not affected: 20 recommended: 54 | 2026-07-26T00:38:09+00:00 | Vulnerability · Source |
| CVE-2017-9955 | suse_vex | SUSE CVE CVE-2017-9955 | known affected: 1 known not affected: 134 recommended: 54 | 2026-07-26T00:38:08+00:00 | Vulnerability · Source |
| CVE-2017-9984 | suse_vex | SUSE CVE CVE-2017-9984 | known not affected: 235 | 2026-07-26T00:38:06+00:00 | Vulnerability · Source |
| CVE-2017-9986 | suse_vex | SUSE CVE CVE-2017-9986 | known not affected: 343 | 2026-07-26T00:38:05+00:00 | Vulnerability · Source |
| CVE-2017-10053 | suse_vex | SUSE CVE CVE-2017-10053 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:04+00:00 | Vulnerability · Source |
| CVE-2017-10067 | suse_vex | SUSE CVE CVE-2017-10067 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:02+00:00 | Vulnerability · Source |
| CVE-2017-10087 | suse_vex | SUSE CVE CVE-2017-10087 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:38:01+00:00 | Vulnerability · Source |
| CVE-2017-10090 | suse_vex | SUSE CVE CVE-2017-10090 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:59+00:00 | Vulnerability · Source |
| CVE-2017-10101 | suse_vex | SUSE CVE CVE-2017-10101 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:57+00:00 | Vulnerability · Source |
| CVE-2017-10102 | suse_vex | SUSE CVE CVE-2017-10102 | known affected: 409 known not affected: 109 recommended: 690 | 2026-07-26T00:37:56+00:00 | Vulnerability · Source |
| CVE-2017-10108 | suse_vex | SUSE CVE CVE-2017-10108 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:54+00:00 | Vulnerability · Source |
| CVE-2017-10109 | suse_vex | SUSE CVE CVE-2017-10109 | known affected: 409 known not affected: 109 recommended: 690 | 2026-07-26T00:37:52+00:00 | Vulnerability · Source |
| CVE-2017-10114 | suse_vex | SUSE CVE CVE-2017-10114 | recommended: 335 | 2026-07-26T00:37:50+00:00 | Vulnerability · Source |
| CVE-2017-10116 | suse_vex | SUSE CVE CVE-2017-10116 | known affected: 15 known not affected: 109 recommended: 690 | 2026-07-26T00:37:49+00:00 | Vulnerability · Source |
| CVE-2017-10125 | suse_vex | SUSE CVE CVE-2017-10125 | known affected: 15 known not affected: 109 recommended: 667 | 2026-07-26T00:37:47+00:00 | Vulnerability · Source |
| CVE-2017-10135 | suse_vex | SUSE CVE CVE-2017-10135 | recommended: 358 | 2026-07-26T00:37:45+00:00 | Vulnerability · Source |
| CVE-2017-10268 | suse_vex | SUSE CVE CVE-2017-10268 | known affected: 35 known not affected: 104 recommended: 610 | 2026-07-26T00:37:43+00:00 | Vulnerability · Source |
| CVE-2017-10274 | suse_vex | SUSE CVE CVE-2017-10274 | known affected: 66 known not affected: 65 recommended: 358 | 2026-07-26T00:37:42+00:00 | Vulnerability · Source |
| CVE-2017-10281 | suse_vex | SUSE CVE CVE-2017-10281 | known affected: 102 known not affected: 230 recommended: 758 | 2026-07-26T00:37:40+00:00 | Vulnerability · Source |
| CVE-2017-10285 | suse_vex | SUSE CVE CVE-2017-10285 | known affected: 103 known not affected: 225 recommended: 758 | 2026-07-26T00:37:38+00:00 | Vulnerability · Source |
| CVE-2017-10345 | suse_vex | SUSE CVE CVE-2017-10345 | known affected: 497 known not affected: 225 recommended: 758 | 2026-07-26T00:37:37+00:00 | Vulnerability · Source |
| CVE-2017-10346 | suse_vex | SUSE CVE CVE-2017-10346 | known affected: 497 known not affected: 225 recommended: 758 | 2026-07-26T00:37:35+00:00 | Vulnerability · Source |
| CVE-2017-10347 | suse_vex | SUSE CVE CVE-2017-10347 | known affected: 497 known not affected: 225 recommended: 758 | 2026-07-26T00:37:33+00:00 | Vulnerability · Source |
| CVE-2017-10350 | suse_vex | SUSE CVE CVE-2017-10350 | known affected: 87 known not affected: 328 recommended: 758 | 2026-07-26T00:37:31+00:00 | Vulnerability · Source |
| CVE-2017-10355 | suse_vex | SUSE CVE CVE-2017-10355 | known affected: 481 known not affected: 271 recommended: 758 | 2026-07-26T00:37:30+00:00 | Vulnerability · Source |
| CVE-2017-10357 | suse_vex | SUSE CVE CVE-2017-10357 | known affected: 103 known not affected: 225 recommended: 758 | 2026-07-26T00:37:28+00:00 | Vulnerability · Source |
| CVE-2017-10388 | suse_vex | SUSE CVE CVE-2017-10388 | known affected: 103 known not affected: 225 recommended: 758 | 2026-07-26T00:37:23+00:00 | Vulnerability · Source |
| CVE-2017-10661 | suse_vex | SUSE CVE CVE-2017-10661 | known affected: 68 known not affected: 485 recommended: 283 | 2026-07-26T00:37:22+00:00 | Vulnerability · Source |
| CVE-2017-10685 | suse_vex | SUSE CVE CVE-2017-10685 | known affected: 1 recommended: 231 | 2026-07-26T00:37:20+00:00 | Vulnerability · Source |
| CVE-2017-10788 | suse_vex | SUSE CVE CVE-2017-10788 | known affected: 1 known not affected: 24 recommended: 72 | 2026-07-26T00:37:19+00:00 | Vulnerability · Source |
| CVE-2017-10794 | suse_vex | SUSE CVE CVE-2017-10794 | known not affected: 209 recommended: 22 | 2026-07-26T00:37:17+00:00 | Vulnerability · Source |
| CVE-2017-10862 | suse_vex | SUSE CVE CVE-2017-10862 | known affected: 95 | 2026-07-26T00:37:15+00:00 | Vulnerability · Source |
| CVE-2017-10913 | suse_vex | SUSE CVE CVE-2017-10913 | known not affected: 1 recommended: 35 | 2026-07-26T00:37:14+00:00 | Vulnerability · Source |
| CVE-2017-10914 | suse_vex | SUSE CVE CVE-2017-10914 | known not affected: 1 recommended: 35 | 2026-07-26T00:37:12+00:00 | Vulnerability · Source |
| CVE-2017-10916 | suse_vex | SUSE CVE CVE-2017-10916 | known affected: 12 known not affected: 40 recommended: 21 | 2026-07-26T00:37:11+00:00 | Vulnerability · Source |
| CVE-2017-10917 | suse_vex | SUSE CVE CVE-2017-10917 | known affected: 13 known not affected: 3 recommended: 35 | 2026-07-26T00:37:09+00:00 | Vulnerability · Source |
| CVE-2017-10919 | suse_vex | SUSE CVE CVE-2017-10919 | known not affected: 73 | 2026-07-26T00:37:08+00:00 | Vulnerability · Source |
| CVE-2017-10972 | suse_vex | SUSE CVE CVE-2017-10972 | known affected: 11 known not affected: 15 recommended: 254 | 2026-07-26T00:37:07+00:00 | Vulnerability · Source |
| CVE-2017-10982 | suse_vex | SUSE CVE CVE-2017-10982 | known affected: 24 known not affected: 111 recommended: 26 | 2026-07-26T00:37:03+00:00 | Vulnerability · Source |
| CVE-2017-10987 | suse_vex | SUSE CVE CVE-2017-10987 | known affected: 24 known not affected: 111 recommended: 625 | 2026-07-26T00:37:02+00:00 | Vulnerability · Source |
| CVE-2017-10989 | suse_vex | SUSE CVE CVE-2017-10989 | known affected: 464 known not affected: 151 recommended: 119 | 2026-07-26T00:37:00+00:00 | Vulnerability · Source |
| CVE-2017-11102 | suse_vex | SUSE CVE CVE-2017-11102 | known affected: 3 known not affected: 85 recommended: 14 | 2026-07-26T00:36:58+00:00 | Vulnerability · Source |
| CVE-2017-11171 | suse_vex | SUSE CVE CVE-2017-11171 | known not affected: 24 recommended: 8 | 2026-07-26T00:36:57+00:00 | Vulnerability · Source |