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-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-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-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-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 |
| CVE-2017-15015 | suse_vex | SUSE CVE CVE-2017-15015 | known affected: 10 known not affected: 144 | 2026-07-26T00:31:11+00:00 | Vulnerability · Source |
| CVE-2017-15121 | suse_vex | SUSE CVE CVE-2017-15121 | known not affected: 36 recommended: 12 | 2026-07-26T00:31:00+00:00 | Vulnerability · Source |
| CVE-2017-15127 | suse_vex | SUSE CVE CVE-2017-15127 | known not affected: 116 recommended: 305 | 2026-07-26T00:30:59+00:00 | Vulnerability · Source |
| CVE-2017-15217 | suse_vex | SUSE CVE CVE-2017-15217 | known affected: 94 known not affected: 50 recommended: 136 | 2026-07-26T00:30:52+00:00 | Vulnerability · Source |
| CVE-2017-15565 | suse_vex | SUSE CVE CVE-2017-15565 | known affected: 50 recommended: 140 | 2026-07-26T00:30:35+00:00 | Vulnerability · Source |
| CVE-2017-15590 | suse_vex | SUSE CVE CVE-2017-15590 | known affected: 32 known not affected: 85 recommended: 141 | 2026-07-26T00:30:33+00:00 | Vulnerability · Source |
| CVE-2017-15596 | suse_vex | SUSE CVE CVE-2017-15596 | known not affected: 21 | 2026-07-26T00:30:31+00:00 | Vulnerability · Source |
| CVE-2017-15638 | suse_vex | SUSE CVE CVE-2017-15638 | known affected: 16 recommended: 19 | 2026-07-26T00:30:29+00:00 | Vulnerability · Source |
| CVE-2017-16532 | suse_vex | SUSE CVE CVE-2017-16532 | known not affected: 368 | 2026-07-26T00:30:15+00:00 | Vulnerability · Source |
| CVE-2017-16643 | suse_vex | SUSE CVE CVE-2017-16643 | known not affected: 341 | 2026-07-26T00:30:07+00:00 | Vulnerability · Source |
| CVE-2017-16645 | suse_vex | SUSE CVE CVE-2017-16645 | known not affected: 291 recommended: 413 | 2026-07-26T00:30:05+00:00 | Vulnerability · Source |
| CVE-2017-16646 | suse_vex | SUSE CVE CVE-2017-16646 | known affected: 320 known not affected: 180 recommended: 1162 | 2026-07-26T00:30:03+00:00 | Vulnerability · Source |
| CVE-2017-16648 | suse_vex | SUSE CVE CVE-2017-16648 | known affected: 341 known not affected: 243 recommended: 787 | 2026-07-26T00:30:01+00:00 | Vulnerability · Source |
| CVE-2017-16932 | suse_vex | SUSE CVE CVE-2017-16932 | known affected: 395 known not affected: 39 recommended: 129 | 2026-07-26T00:29:47+00:00 | Vulnerability · Source |
| CVE-2017-16942 | suse_vex | SUSE CVE CVE-2017-16942 | recommended: 58 | 2026-07-26T00:29:45+00:00 | Vulnerability · Source |
| CVE-2017-16994 | suse_vex | SUSE CVE CVE-2017-16994 | known not affected: 188 recommended: 407 | 2026-07-26T00:29:43+00:00 | Vulnerability · Source |
| CVE-2017-17046 | suse_vex | SUSE CVE CVE-2017-17046 | known not affected: 94 | 2026-07-26T00:29:41+00:00 | Vulnerability · Source |
| CVE-2017-17053 | suse_vex | SUSE CVE CVE-2017-17053 | known not affected: 283 recommended: 3 | 2026-07-26T00:29:40+00:00 | Vulnerability · Source |
| CVE-2017-17121 | suse_vex | SUSE CVE CVE-2017-17121 | known affected: 3 known not affected: 219 | 2026-07-26T00:29:37+00:00 | Vulnerability · Source |
| CVE-2017-17126 | suse_vex | SUSE CVE CVE-2017-17126 | known affected: 8 known not affected: 54 | 2026-07-26T00:29:36+00:00 | Vulnerability · Source |
| CVE-2017-17405 | suse_vex | SUSE CVE CVE-2017-17405 | known affected: 1 known not affected: 77 recommended: 98 | 2026-07-26T00:29:34+00:00 | Vulnerability · Source |
| CVE-2017-17480 | suse_vex | SUSE CVE CVE-2017-17480 | recommended: 10 | 2026-07-26T00:29:24+00:00 | Vulnerability · Source |