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-12434 | suse_vex | SUSE CVE CVE-2017-12434 | known not affected: 14 recommended: 172 | 2026-07-26T00:35:22+00:00 | Vulnerability · Source |
| 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-12566 | suse_vex | SUSE CVE CVE-2017-12566 | known affected: 95 recommended: 186 | 2026-07-26T00:35:15+00:00 | Vulnerability · Source |
| CVE-2017-12588 | suse_vex | SUSE CVE CVE-2017-12588 | known affected: 30 known not affected: 229 | 2026-07-26T00:35:13+00:00 | Vulnerability · Source |
| CVE-2017-12613 | suse_vex | SUSE CVE CVE-2017-12613 | known affected: 18 recommended: 46 | 2026-07-26T00:35:10+00:00 | Vulnerability · Source |
| CVE-2017-12615 | suse_vex | SUSE CVE CVE-2017-12615 | known affected: 46 known not affected: 179 recommended: 19 | 2026-07-26T00:35:09+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-12664 | suse_vex | SUSE CVE CVE-2017-12664 | known affected: 95 known not affected: 14 recommended: 172 | 2026-07-26T00:35:00+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-12669 | suse_vex | SUSE CVE CVE-2017-12669 | known affected: 94 known not affected: 15 recommended: 172 | 2026-07-26T00:34:53+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-12675 | suse_vex | SUSE CVE CVE-2017-12675 | known not affected: 276 recommended: 172 | 2026-07-26T00:34:48+00:00 | Vulnerability · Source |
| CVE-2017-12676 | suse_vex | SUSE CVE CVE-2017-12676 | known affected: 94 recommended: 186 | 2026-07-26T00:34:46+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-12985 | suse_vex | SUSE CVE CVE-2017-12985 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:34:20+00:00 | Vulnerability · Source |
| CVE-2017-12993 | suse_vex | SUSE CVE CVE-2017-12993 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:34:12+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-13007 | suse_vex | SUSE CVE CVE-2017-13007 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:33:56+00:00 | Vulnerability · Source |
| CVE-2017-13011 | suse_vex | SUSE CVE CVE-2017-13011 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:52+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-13026 | suse_vex | SUSE CVE CVE-2017-13026 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:33:43+00:00 | Vulnerability · Source |
| CVE-2017-13029 | suse_vex | SUSE CVE CVE-2017-13029 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:41+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-13036 | suse_vex | SUSE CVE CVE-2017-13036 | known affected: 336 known not affected: 24 recommended: 151 | 2026-07-26T00:33:37+00:00 | Vulnerability · Source |
| CVE-2017-13042 | suse_vex | SUSE CVE CVE-2017-13042 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T00:33:31+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-13142 | suse_vex | SUSE CVE CVE-2017-13142 | known affected: 94 recommended: 186 | 2026-07-26T00:33:11+00:00 | Vulnerability · Source |
| CVE-2017-13167 | suse_vex | SUSE CVE CVE-2017-13167 | known affected: 2 known not affected: 51 recommended: 209 | 2026-07-26T00:33:09+00:00 | Vulnerability · Source |
| CVE-2017-13194 | suse_vex | SUSE CVE CVE-2017-13194 | known not affected: 69 recommended: 206 | 2026-07-26T00:33:08+00:00 | Vulnerability · Source |
| CVE-2017-13305 | suse_vex | SUSE CVE CVE-2017-13305 | known affected: 36 known not affected: 111 recommended: 257 | 2026-07-26T00:33:05+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-13685 | suse_vex | SUSE CVE CVE-2017-13685 | known not affected: 162 | 2026-07-26T00:33:02+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-13720 | suse_vex | SUSE CVE CVE-2017-13720 | known affected: 394 known not affected: 215 recommended: 165 | 2026-07-26T00:32:54+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 |