VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-14151 | suse_vex | SUSE CVE CVE-2017-14151 | known not affected: 110 recommended: 184 | 2026-07-26T00:32:17+00:00 | Vulnerability · Source |
| CVE-2017-14174 | suse_vex | SUSE CVE CVE-2017-14174 | known affected: 95 recommended: 186 | 2026-07-26T00:32:13+00:00 | Vulnerability · Source |
| CVE-2017-14175 | suse_vex | SUSE CVE CVE-2017-14175 | known affected: 94 recommended: 172 | 2026-07-26T00:32:12+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-14246 | suse_vex | SUSE CVE CVE-2017-14246 | known affected: 394 known not affected: 68 recommended: 179 | 2026-07-26T00:32:09+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-14316 | suse_vex | SUSE CVE CVE-2017-14316 | known affected: 32 known not affected: 237 recommended: 165 | 2026-07-26T00:32:06+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-14461 | suse_vex | SUSE CVE CVE-2017-14461 | known affected: 8 known not affected: 37 recommended: 425 | 2026-07-26T00:31:56+00:00 | Vulnerability · Source |
| CVE-2017-14495 | suse_vex | SUSE CVE CVE-2017-14495 | known affected: 22 known not affected: 6 recommended: 100 | 2026-07-26T00:31:51+00:00 | Vulnerability · Source |
| CVE-2017-14502 | suse_vex | SUSE CVE CVE-2017-14502 | known affected: 423 known not affected: 53 recommended: 255 | 2026-07-26T00:31:46+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-14529 | suse_vex | SUSE CVE CVE-2017-14529 | known affected: 434 known not affected: 137 recommended: 330 | 2026-07-26T00:31:38+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-14729 | suse_vex | SUSE CVE CVE-2017-14729 | known affected: 394 known not affected: 41 recommended: 330 | 2026-07-26T00:31:31+00:00 | Vulnerability · Source |
| CVE-2017-14746 | suse_vex | SUSE CVE CVE-2017-14746 | known affected: 853 known not affected: 567 recommended: 3799 | 2026-07-26T00:31:28+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-14867 | suse_vex | SUSE CVE CVE-2017-14867 | known affected: 130 known not affected: 205 recommended: 898 | 2026-07-26T00:31:22+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-14928 | suse_vex | SUSE CVE CVE-2017-14928 | known not affected: 189 recommended: 95 | 2026-07-26T00:31:19+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-14939 | suse_vex | SUSE CVE CVE-2017-14939 | known not affected: 20 | 2026-07-26T00:31:15+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-15087 | suse_vex | SUSE CVE CVE-2017-15087 | known not affected: 180 | 2026-07-26T00:31:09+00:00 | Vulnerability · Source |
| CVE-2017-15088 | suse_vex | SUSE CVE CVE-2017-15088 | known affected: 114 known not affected: 27 recommended: 141 | 2026-07-26T00:31:07+00:00 | Vulnerability · Source |
| CVE-2017-15099 | suse_vex | SUSE CVE CVE-2017-15099 | known not affected: 730 recommended: 380 | 2026-07-26T00:31:05+00:00 | Vulnerability · Source |
| CVE-2017-15102 | suse_vex | SUSE CVE CVE-2017-15102 | known not affected: 365 recommended: 203 | 2026-07-26T00:31:04+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-15129 | suse_vex | SUSE CVE CVE-2017-15129 | known affected: 36 known not affected: 144 recommended: 436 | 2026-07-26T00:30:57+00:00 | Vulnerability · Source |
| CVE-2017-15189 | suse_vex | SUSE CVE CVE-2017-15189 | known not affected: 115 recommended: 444 | 2026-07-26T00:30:54+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-15274 | suse_vex | SUSE CVE CVE-2017-15274 | known not affected: 529 recommended: 284 | 2026-07-26T00:30:48+00:00 | Vulnerability · Source |
| CVE-2017-15277 | suse_vex | SUSE CVE CVE-2017-15277 | known affected: 95 recommended: 186 | 2026-07-26T00:30:46+00:00 | Vulnerability · Source |
| CVE-2017-15299 | suse_vex | SUSE CVE CVE-2017-15299 | known not affected: 530 recommended: 80 | 2026-07-26T00:30:44+00:00 | Vulnerability · Source |
| CVE-2017-15422 | suse_vex | SUSE CVE CVE-2017-15422 | known not affected: 6 recommended: 146 | 2026-07-26T00:30:38+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-15649 | suse_vex | SUSE CVE CVE-2017-15649 | known affected: 24 known not affected: 614 recommended: 596 | 2026-07-26T00:30:27+00:00 | Vulnerability · Source |