VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-8281 | suse_vex | SUSE CVE CVE-2017-8281 | known not affected: 78 | 2026-07-26T00:39:56+00:00 | Vulnerability · Source |
| CVE-2017-8343 | suse_vex | SUSE CVE CVE-2017-8343 | known not affected: 50 recommended: 134 | 2026-07-26T00:39:53+00:00 | Vulnerability · Source |
| CVE-2017-8352 | suse_vex | SUSE CVE CVE-2017-8352 | recommended: 184 | 2026-07-26T00:39:51+00:00 | Vulnerability · Source |
| CVE-2017-8422 | suse_vex | SUSE CVE CVE-2017-8422 | known affected: 1 known not affected: 10 recommended: 165 | 2026-07-26T00:39:41+00:00 | Vulnerability · Source |
| CVE-2017-8765 | suse_vex | SUSE CVE CVE-2017-8765 | recommended: 184 | 2026-07-26T00:39:39+00:00 | Vulnerability · Source |
| CVE-2017-8804 | suse_vex | SUSE CVE CVE-2017-8804 | known affected: 62 recommended: 265 | 2026-07-26T00:39:36+00:00 | Vulnerability · Source |
| CVE-2017-9059 | suse_vex | SUSE CVE CVE-2017-9059 | known not affected: 136 recommended: 89 | 2026-07-26T00:39:20+00:00 | Vulnerability · Source |
| CVE-2017-9083 | suse_vex | SUSE CVE CVE-2017-9083 | known affected: 14 recommended: 12 | 2026-07-26T00:39:16+00:00 | Vulnerability · Source |
| CVE-2017-9147 | suse_vex | SUSE CVE CVE-2017-9147 | known not affected: 13 recommended: 22 | 2026-07-26T00:39:06+00:00 | Vulnerability · Source |
| CVE-2017-9150 | suse_vex | SUSE CVE CVE-2017-9150 | known not affected: 585 recommended: 101 | 2026-07-26T00:39:04+00:00 | Vulnerability · Source |
| CVE-2017-9217 | suse_vex | SUSE CVE CVE-2017-9217 | known affected: 130 known not affected: 71 recommended: 172 | 2026-07-26T00:39:00+00:00 | Vulnerability · Source |
| CVE-2017-9226 | suse_vex | SUSE CVE CVE-2017-9226 | known not affected: 2 recommended: 1295 | 2026-07-26T00:38:59+00:00 | Vulnerability · Source |
| CVE-2017-9347 | suse_vex | SUSE CVE CVE-2017-9347 | known affected: 3 known not affected: 217 recommended: 559 | 2026-07-26T00:38:49+00:00 | Vulnerability · Source |
| CVE-2017-9373 | suse_vex | SUSE CVE CVE-2017-9373 | known affected: 26 recommended: 124 | 2026-07-26T00:38:45+00:00 | Vulnerability · Source |
| CVE-2017-9405 | suse_vex | SUSE CVE CVE-2017-9405 | known affected: 94 recommended: 186 | 2026-07-26T00:38:43+00:00 | Vulnerability · Source |
| CVE-2017-9409 | suse_vex | SUSE CVE CVE-2017-9409 | known affected: 94 known not affected: 37 recommended: 172 | 2026-07-26T00:38:42+00:00 | Vulnerability · Source |
| CVE-2017-9439 | suse_vex | SUSE CVE CVE-2017-9439 | known affected: 60 recommended: 186 | 2026-07-26T00:38:40+00:00 | Vulnerability · Source |
| CVE-2017-9440 | suse_vex | SUSE CVE CVE-2017-9440 | known affected: 60 known not affected: 50 recommended: 136 | 2026-07-26T00:38:39+00:00 | Vulnerability · Source |
| CVE-2017-9461 | suse_vex | SUSE CVE CVE-2017-9461 | known not affected: 94 recommended: 26 | 2026-07-26T00:38:38+00:00 | Vulnerability · Source |
| CVE-2017-9499 | suse_vex | SUSE CVE CVE-2017-9499 | known not affected: 94 | 2026-07-26T00:38:37+00:00 | Vulnerability · Source |
| CVE-2017-9501 | suse_vex | SUSE CVE CVE-2017-9501 | known affected: 60 recommended: 186 | 2026-07-26T00:38:35+00:00 | Vulnerability · Source |
| CVE-2017-9606 | suse_vex | SUSE CVE CVE-2017-9606 | known not affected: 10 | 2026-07-26T00:38:34+00:00 | Vulnerability · Source |
| CVE-2017-9726 | suse_vex | SUSE CVE CVE-2017-9726 | known affected: 1 recommended: 85 | 2026-07-26T00:38:29+00:00 | Vulnerability · Source |
| CVE-2017-9727 | suse_vex | SUSE CVE CVE-2017-9727 | known affected: 1 recommended: 85 | 2026-07-26T00:38:27+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-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-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-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-10135 | suse_vex | SUSE CVE CVE-2017-10135 | recommended: 358 | 2026-07-26T00:37:45+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-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-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-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-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-11171 | suse_vex | SUSE CVE CVE-2017-11171 | known not affected: 24 recommended: 8 | 2026-07-26T00:36:57+00:00 | Vulnerability · Source |
| CVE-2017-11176 | suse_vex | SUSE CVE CVE-2017-11176 | known affected: 16 known not affected: 514 recommended: 243 | 2026-07-26T00:36:55+00:00 | Vulnerability · Source |
| CVE-2017-11360 | suse_vex | SUSE CVE CVE-2017-11360 | known affected: 47 known not affected: 79 | 2026-07-26T00:36:49+00:00 | Vulnerability · Source |