VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294016 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-12565 | suse_vex | SUSE CVE CVE-2017-12565 | known affected: 94 recommended: 186 | 2026-07-26T00:35:17+00:00 | Vulnerability · Source |
| CVE-2017-12616 | suse_vex | SUSE CVE CVE-2017-12616 | known not affected: 73 recommended: 9 | 2026-07-26T00:35:07+00:00 | Vulnerability · Source |
| CVE-2017-12640 | suse_vex | SUSE CVE CVE-2017-12640 | known affected: 94 recommended: 186 | 2026-07-26T00:35:04+00:00 | Vulnerability · Source |
| CVE-2017-12644 | suse_vex | SUSE CVE CVE-2017-12644 | known affected: 94 known not affected: 20 recommended: 186 | 2026-07-26T00:35:02+00:00 | Vulnerability · Source |
| CVE-2017-12665 | suse_vex | SUSE CVE CVE-2017-12665 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T00:34:58+00:00 | Vulnerability · Source |
| CVE-2017-12666 | suse_vex | SUSE CVE CVE-2017-12666 | known affected: 94 known not affected: 50 | 2026-07-26T00:34:55+00:00 | Vulnerability · Source |
| CVE-2017-12672 | suse_vex | SUSE CVE CVE-2017-12672 | known not affected: 276 recommended: 172 | 2026-07-26T00:34:51+00:00 | Vulnerability · Source |
| CVE-2017-12691 | suse_vex | SUSE CVE CVE-2017-12691 | known affected: 16 known not affected: 170 recommended: 186 | 2026-07-26T00:34:43+00:00 | Vulnerability · Source |
| CVE-2017-12692 | suse_vex | SUSE CVE CVE-2017-12692 | known affected: 94 recommended: 172 | 2026-07-26T00:34:41+00:00 | Vulnerability · Source |
| CVE-2017-12805 | suse_vex | SUSE CVE CVE-2017-12805 | known affected: 96 known not affected: 46 recommended: 168 | 2026-07-26T00:34:39+00:00 | Vulnerability · Source |
| CVE-2017-12843 | suse_vex | SUSE CVE CVE-2017-12843 | known not affected: 34 | 2026-07-26T00:34:34+00:00 | Vulnerability · Source |
| CVE-2017-12997 | suse_vex | SUSE CVE CVE-2017-12997 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:34:07+00:00 | Vulnerability · Source |
| CVE-2017-13019 | suse_vex | SUSE CVE CVE-2017-13019 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:47+00:00 | Vulnerability · Source |
| CVE-2017-13030 | suse_vex | SUSE CVE CVE-2017-13030 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:38+00:00 | Vulnerability · Source |
| CVE-2017-13058 | suse_vex | SUSE CVE CVE-2017-13058 | known affected: 1 recommended: 188 | 2026-07-26T00:33:25+00:00 | Vulnerability · Source |
| CVE-2017-13060 | suse_vex | SUSE CVE CVE-2017-13060 | known not affected: 14 recommended: 172 | 2026-07-26T00:33:23+00:00 | Vulnerability · Source |
| CVE-2017-13062 | suse_vex | SUSE CVE CVE-2017-13062 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T00:33:22+00:00 | Vulnerability · Source |
| CVE-2017-13063 | suse_vex | SUSE CVE CVE-2017-13063 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:33:21+00:00 | Vulnerability · Source |
| CVE-2017-13065 | suse_vex | SUSE CVE CVE-2017-13065 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:33:19+00:00 | Vulnerability · Source |
| CVE-2017-13131 | suse_vex | SUSE CVE CVE-2017-13131 | known affected: 95 known not affected: 1 recommended: 186 | 2026-07-26T00:33:16+00:00 | Vulnerability · Source |
| CVE-2017-13139 | suse_vex | SUSE CVE CVE-2017-13139 | recommended: 186 | 2026-07-26T00:33:14+00:00 | Vulnerability · Source |
| CVE-2017-13141 | suse_vex | SUSE CVE CVE-2017-13141 | known affected: 94 recommended: 186 | 2026-07-26T00:33:12+00:00 | Vulnerability · Source |
| CVE-2017-13658 | suse_vex | SUSE CVE CVE-2017-13658 | known not affected: 14 recommended: 172 | 2026-07-26T00:33:03+00:00 | Vulnerability · Source |
| CVE-2017-13695 | suse_vex | SUSE CVE CVE-2017-13695 | known affected: 405 known not affected: 287 recommended: 305 | 2026-07-26T00:32:58+00:00 | Vulnerability · Source |
| CVE-2017-13715 | suse_vex | SUSE CVE CVE-2017-13715 | known not affected: 289 | 2026-07-26T00:32:56+00:00 | Vulnerability · Source |
| CVE-2017-13722 | suse_vex | SUSE CVE CVE-2017-13722 | known affected: 394 known not affected: 60 recommended: 165 | 2026-07-26T00:32:53+00:00 | Vulnerability · Source |
| CVE-2017-13731 | suse_vex | SUSE CVE CVE-2017-13731 | known affected: 157 recommended: 201 | 2026-07-26T00:32:51+00:00 | Vulnerability · Source |
| CVE-2017-13732 | suse_vex | SUSE CVE CVE-2017-13732 | known affected: 157 recommended: 201 | 2026-07-26T00:32:49+00:00 | Vulnerability · Source |
| CVE-2017-13769 | suse_vex | SUSE CVE CVE-2017-13769 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T00:32:36+00:00 | Vulnerability · Source |
| CVE-2017-14042 | suse_vex | SUSE CVE CVE-2017-14042 | known affected: 95 recommended: 186 | 2026-07-26T00:32:28+00:00 | Vulnerability · Source |
| CVE-2017-14103 | suse_vex | SUSE CVE CVE-2017-14103 | known affected: 94 recommended: 186 | 2026-07-26T00:32:26+00:00 | Vulnerability · Source |
| CVE-2017-14121 | suse_vex | SUSE CVE CVE-2017-14121 | known not affected: 37 | 2026-07-26T00:32:22+00:00 | Vulnerability · Source |
| CVE-2017-14137 | suse_vex | SUSE CVE CVE-2017-14137 | known affected: 10 known not affected: 84 | 2026-07-26T00:32:19+00:00 | Vulnerability · Source |
| CVE-2017-14224 | suse_vex | SUSE CVE CVE-2017-14224 | known affected: 95 recommended: 186 | 2026-07-26T00:32:10+00:00 | Vulnerability · Source |
| CVE-2017-14249 | suse_vex | SUSE CVE CVE-2017-14249 | known affected: 94 recommended: 186 | 2026-07-26T00:32:07+00:00 | Vulnerability · Source |
| CVE-2017-14317 | suse_vex | SUSE CVE CVE-2017-14317 | known affected: 32 known not affected: 85 recommended: 173 | 2026-07-26T00:32:04+00:00 | Vulnerability · Source |
| CVE-2017-14319 | suse_vex | SUSE CVE CVE-2017-14319 | known affected: 32 known not affected: 85 recommended: 173 | 2026-07-26T00:32:03+00:00 | Vulnerability · Source |
| CVE-2017-14343 | suse_vex | SUSE CVE CVE-2017-14343 | known affected: 98 known not affected: 37 recommended: 186 | 2026-07-26T00:32:00+00:00 | Vulnerability · Source |
| CVE-2017-14348 | suse_vex | SUSE CVE CVE-2017-14348 | known not affected: 91 recommended: 76 | 2026-07-26T00:31:58+00:00 | Vulnerability · Source |
| CVE-2017-14431 | suse_vex | SUSE CVE CVE-2017-14431 | known affected: 13 known not affected: 6 | 2026-07-26T00:31:57+00:00 | Vulnerability · Source |
| CVE-2017-14505 | suse_vex | SUSE CVE CVE-2017-14505 | known affected: 94 recommended: 186 | 2026-07-26T00:31:43+00:00 | Vulnerability · Source |
| CVE-2017-14604 | suse_vex | SUSE CVE CVE-2017-14604 | known affected: 49 recommended: 102 | 2026-07-26T00:31:37+00:00 | Vulnerability · Source |
| CVE-2017-14607 | suse_vex | SUSE CVE CVE-2017-14607 | known affected: 94 known not affected: 21 recommended: 172 | 2026-07-26T00:31:35+00:00 | Vulnerability · Source |
| CVE-2017-14625 | suse_vex | SUSE CVE CVE-2017-14625 | known affected: 10 known not affected: 144 | 2026-07-26T00:31:34+00:00 | Vulnerability · Source |
| CVE-2017-14682 | suse_vex | SUSE CVE CVE-2017-14682 | known affected: 94 known not affected: 36 recommended: 136 | 2026-07-26T00:31:32+00:00 | Vulnerability · Source |
| CVE-2017-14862 | suse_vex | SUSE CVE CVE-2017-14862 | known affected: 13 known not affected: 108 recommended: 186 | 2026-07-26T00:31:25+00:00 | Vulnerability · Source |
| CVE-2017-14866 | suse_vex | SUSE CVE CVE-2017-14866 | known affected: 5 known not affected: 99 | 2026-07-26T00:31:24+00:00 | Vulnerability · Source |
| CVE-2017-14927 | suse_vex | SUSE CVE CVE-2017-14927 | known not affected: 127 | 2026-07-26T00:31:20+00:00 | Vulnerability · Source |
| CVE-2017-14938 | suse_vex | SUSE CVE CVE-2017-14938 | known not affected: 20 | 2026-07-26T00:31:17+00:00 | Vulnerability · Source |
| CVE-2017-14976 | suse_vex | SUSE CVE CVE-2017-14976 | known affected: 50 known not affected: 94 recommended: 95 | 2026-07-26T00:31:12+00:00 | Vulnerability · Source |