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-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 |
| CVE-2017-15705 | suse_vex | SUSE CVE CVE-2017-15705 | known affected: 1 known not affected: 118 recommended: 193 | 2026-07-26T00:30:25+00:00 | Vulnerability · Source |
| CVE-2017-15874 | suse_vex | SUSE CVE CVE-2017-15874 | known affected: 1 known not affected: 16 recommended: 136 | 2026-07-26T00:30:23+00:00 | Vulnerability · Source |
| CVE-2017-16231 | suse_vex | SUSE CVE CVE-2017-16231 | known affected: 14 | 2026-07-26T00:30:17+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-16537 | suse_vex | SUSE CVE CVE-2017-16537 | known affected: 323 known not affected: 255 recommended: 1354 | 2026-07-26T00:30:13+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-16828 | suse_vex | SUSE CVE CVE-2017-16828 | known affected: 452 known not affected: 76 recommended: 343 | 2026-07-26T00:29:57+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-17426 | suse_vex | SUSE CVE CVE-2017-17426 | known affected: 320 known not affected: 464 recommended: 1007 | 2026-07-26T00:29:32+00:00 | Vulnerability · Source |
| CVE-2017-17448 | suse_vex | SUSE CVE CVE-2017-17448 | known not affected: 182 recommended: 503 | 2026-07-26T00:29:30+00:00 | Vulnerability · Source |
| CVE-2017-17449 | suse_vex | SUSE CVE CVE-2017-17449 | known affected: 36 known not affected: 108 recommended: 503 | 2026-07-26T00:29:28+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 |
| CVE-2017-17502 | suse_vex | SUSE CVE CVE-2017-17502 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:29:23+00:00 | Vulnerability · Source |
| CVE-2017-17503 | suse_vex | SUSE CVE CVE-2017-17503 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T00:29:21+00:00 | Vulnerability · Source |
| CVE-2017-17504 | suse_vex | SUSE CVE CVE-2017-17504 | known affected: 94 known not affected: 20 recommended: 186 | 2026-07-26T00:29:19+00:00 | Vulnerability · Source |
| CVE-2017-17564 | suse_vex | SUSE CVE CVE-2017-17564 | known affected: 32 known not affected: 42 recommended: 166 | 2026-07-26T00:29:17+00:00 | Vulnerability · Source |
| CVE-2017-17566 | suse_vex | SUSE CVE CVE-2017-17566 | known affected: 32 known not affected: 42 recommended: 166 | 2026-07-26T00:29:16+00:00 | Vulnerability · Source |
| CVE-2017-17689 | suse_vex | SUSE CVE CVE-2017-17689 | known not affected: 247 recommended: 23 | 2026-07-26T00:29:14+00:00 | Vulnerability · Source |
| CVE-2017-17712 | suse_vex | SUSE CVE CVE-2017-17712 | known not affected: 174 recommended: 438 | 2026-07-26T00:29:11+00:00 | Vulnerability · Source |
| CVE-2017-17723 | suse_vex | SUSE CVE CVE-2017-17723 | known affected: 4 | 2026-07-26T00:29:10+00:00 | Vulnerability · Source |
| CVE-2017-17725 | suse_vex | SUSE CVE CVE-2017-17725 | known affected: 1 known not affected: 85 recommended: 10 | 2026-07-26T00:29:08+00:00 | Vulnerability · Source |
| CVE-2017-17740 | suse_vex | SUSE CVE CVE-2017-17740 | known affected: 373 known not affected: 23 recommended: 756 | 2026-07-26T00:29:06+00:00 | Vulnerability · Source |
| CVE-2017-17790 | suse_vex | SUSE CVE CVE-2017-17790 | known affected: 1 known not affected: 107 recommended: 98 | 2026-07-26T00:29:01+00:00 | Vulnerability · Source |
| CVE-2017-17852 | suse_vex | SUSE CVE CVE-2017-17852 | known not affected: 182 recommended: 299 | 2026-07-26T00:28:59+00:00 | Vulnerability · Source |
| CVE-2017-17856 | suse_vex | SUSE CVE CVE-2017-17856 | known not affected: 182 recommended: 299 | 2026-07-26T00:28:57+00:00 | Vulnerability · Source |
| CVE-2017-17863 | suse_vex | SUSE CVE CVE-2017-17863 | known not affected: 182 | 2026-07-26T00:28:54+00:00 | Vulnerability · Source |