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-5526 | suse_vex | SUSE CVE CVE-2017-5526 | known affected: 420 known not affected: 231 recommended: 1971 | 2026-07-26T00:45:30+00:00 | Vulnerability · Source |
| CVE-2017-5548 | suse_vex | SUSE CVE CVE-2017-5548 | known not affected: 34 | 2026-07-26T00:45:29+00:00 | Vulnerability · Source |
| CVE-2017-5551 | suse_vex | SUSE CVE CVE-2017-5551 | known not affected: 407 recommended: 404 | 2026-07-26T00:45:27+00:00 | Vulnerability · Source |
| CVE-2017-5576 | suse_vex | SUSE CVE CVE-2017-5576 | known affected: 12 known not affected: 258 recommended: 101 | 2026-07-26T00:45:26+00:00 | Vulnerability · Source |
| CVE-2017-5577 | suse_vex | SUSE CVE CVE-2017-5577 | known affected: 12 known not affected: 258 recommended: 101 | 2026-07-26T00:45:24+00:00 | Vulnerability · Source |
| CVE-2017-5579 | suse_vex | SUSE CVE CVE-2017-5579 | known affected: 420 known not affected: 804 recommended: 1875 | 2026-07-26T00:45:21+00:00 | Vulnerability · Source |
| CVE-2017-5596 | suse_vex | SUSE CVE CVE-2017-5596 | known affected: 1 recommended: 588 | 2026-07-26T00:45:19+00:00 | Vulnerability · Source |
| CVE-2017-5601 | suse_vex | SUSE CVE CVE-2017-5601 | known affected: 402 known not affected: 123 recommended: 137 | 2026-07-26T00:45:18+00:00 | Vulnerability · Source |
| CVE-2017-5648 | suse_vex | SUSE CVE CVE-2017-5648 | known affected: 440 known not affected: 141 recommended: 220 | 2026-07-26T00:45:17+00:00 | Vulnerability · Source |
| CVE-2017-5667 | suse_vex | SUSE CVE CVE-2017-5667 | known affected: 420 known not affected: 190 recommended: 1831 | 2026-07-26T00:45:14+00:00 | Vulnerability · Source |
| CVE-2017-5734 | suse_vex | SUSE CVE CVE-2017-5734 | known affected: 29 recommended: 234 | 2026-07-26T00:45:10+00:00 | Vulnerability · Source |
| CVE-2017-5735 | suse_vex | SUSE CVE CVE-2017-5735 | known affected: 29 recommended: 234 | 2026-07-26T00:45:08+00:00 | Vulnerability · Source |
| CVE-2017-5754 | suse_vex | SUSE CVE CVE-2017-5754 | known affected: 358 known not affected: 198 recommended: 2030 | 2026-07-26T00:45:06+00:00 | Vulnerability · Source |
| CVE-2017-5885 | suse_vex | SUSE CVE CVE-2017-5885 | known not affected: 408 recommended: 530 | 2026-07-26T00:44:56+00:00 | Vulnerability · Source |
| CVE-2017-5897 | suse_vex | SUSE CVE CVE-2017-5897 | known affected: 12 known not affected: 481 recommended: 300 | 2026-07-26T00:44:55+00:00 | Vulnerability · Source |
| CVE-2017-5931 | suse_vex | SUSE CVE CVE-2017-5931 | known not affected: 283 recommended: 1641 | 2026-07-26T00:44:53+00:00 | Vulnerability · Source |
| CVE-2017-5951 | suse_vex | SUSE CVE CVE-2017-5951 | known affected: 36 known not affected: 164 recommended: 240 | 2026-07-26T00:44:51+00:00 | Vulnerability · Source |
| CVE-2017-5957 | suse_vex | SUSE CVE CVE-2017-5957 | recommended: 134 | 2026-07-26T00:44:49+00:00 | Vulnerability · Source |
| CVE-2017-5969 | suse_vex | SUSE CVE CVE-2017-5969 | known affected: 393 known not affected: 96 recommended: 521 | 2026-07-26T00:44:48+00:00 | Vulnerability · Source |
| CVE-2017-5986 | suse_vex | SUSE CVE CVE-2017-5986 | known not affected: 381 recommended: 435 | 2026-07-26T00:44:45+00:00 | Vulnerability · Source |
| CVE-2017-5993 | suse_vex | SUSE CVE CVE-2017-5993 | recommended: 134 | 2026-07-26T00:44:43+00:00 | Vulnerability · Source |
| CVE-2017-6001 | suse_vex | SUSE CVE CVE-2017-6001 | known not affected: 529 recommended: 12 | 2026-07-26T00:44:41+00:00 | Vulnerability · Source |
| CVE-2017-6056 | suse_vex | SUSE CVE CVE-2017-6056 | known not affected: 54 | 2026-07-26T00:44:39+00:00 | Vulnerability · Source |
| CVE-2017-6181 | suse_vex | SUSE CVE CVE-2017-6181 | known not affected: 58 | 2026-07-26T00:44:38+00:00 | Vulnerability · Source |
| CVE-2017-6311 | suse_vex | SUSE CVE CVE-2017-6311 | known affected: 14 known not affected: 60 | 2026-07-26T00:44:35+00:00 | Vulnerability · Source |
| CVE-2017-6312 | suse_vex | SUSE CVE CVE-2017-6312 | known affected: 397 known not affected: 828 recommended: 672 | 2026-07-26T00:44:33+00:00 | Vulnerability · Source |
| CVE-2017-6317 | suse_vex | SUSE CVE CVE-2017-6317 | recommended: 29 | 2026-07-26T00:44:32+00:00 | Vulnerability · Source |
| CVE-2017-6348 | suse_vex | SUSE CVE CVE-2017-6348 | known affected: 2 known not affected: 319 recommended: 233 | 2026-07-26T00:44:31+00:00 | Vulnerability · Source |
| CVE-2017-6353 | suse_vex | SUSE CVE CVE-2017-6353 | known affected: 14 known not affected: 345 recommended: 423 | 2026-07-26T00:44:29+00:00 | Vulnerability · Source |
| CVE-2017-6439 | suse_vex | SUSE CVE CVE-2017-6439 | recommended: 338 | 2026-07-26T00:44:18+00:00 | Vulnerability · Source |
| CVE-2017-6462 | suse_vex | SUSE CVE CVE-2017-6462 | known affected: 31 recommended: 103 | 2026-07-26T00:44:16+00:00 | Vulnerability · Source |
| CVE-2017-6508 | suse_vex | SUSE CVE CVE-2017-6508 | known affected: 337 known not affected: 24 recommended: 169 | 2026-07-26T00:44:11+00:00 | Vulnerability · Source |
| CVE-2017-6590 | suse_vex | SUSE CVE CVE-2017-6590 | known not affected: 172 recommended: 253 | 2026-07-26T00:44:09+00:00 | Vulnerability · Source |
| CVE-2017-6828 | suse_vex | SUSE CVE CVE-2017-6828 | known affected: 45 recommended: 202 | 2026-07-26T00:44:07+00:00 | Vulnerability · Source |
| CVE-2017-6830 | suse_vex | SUSE CVE CVE-2017-6830 | known affected: 45 recommended: 202 | 2026-07-26T00:44:05+00:00 | Vulnerability · Source |
| CVE-2017-6833 | suse_vex | SUSE CVE CVE-2017-6833 | known affected: 45 recommended: 196 | 2026-07-26T00:44:04+00:00 | Vulnerability · Source |
| CVE-2017-6834 | suse_vex | SUSE CVE CVE-2017-6834 | known affected: 45 recommended: 202 | 2026-07-26T00:44:02+00:00 | Vulnerability · Source |
| CVE-2017-6835 | suse_vex | SUSE CVE CVE-2017-6835 | known affected: 45 recommended: 202 | 2026-07-26T00:44:00+00:00 | Vulnerability · Source |
| CVE-2017-6852 | suse_vex | SUSE CVE CVE-2017-6852 | known not affected: 100 | 2026-07-26T00:43:58+00:00 | Vulnerability · Source |
| CVE-2017-6874 | suse_vex | SUSE CVE CVE-2017-6874 | known not affected: 343 | 2026-07-26T00:43:56+00:00 | Vulnerability · Source |
| CVE-2017-6892 | suse_vex | SUSE CVE CVE-2017-6892 | known affected: 394 known not affected: 14 recommended: 165 | 2026-07-26T00:43:53+00:00 | Vulnerability · Source |
| CVE-2017-6965 | suse_vex | SUSE CVE CVE-2017-6965 | known affected: 394 known not affected: 158 recommended: 340 | 2026-07-26T00:43:51+00:00 | Vulnerability · Source |
| CVE-2017-7006 | suse_vex | SUSE CVE CVE-2017-7006 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:49+00:00 | Vulnerability · Source |
| CVE-2017-7018 | suse_vex | SUSE CVE CVE-2017-7018 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:46+00:00 | Vulnerability · Source |
| CVE-2017-7019 | suse_vex | SUSE CVE CVE-2017-7019 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:44+00:00 | Vulnerability · Source |
| CVE-2017-7043 | suse_vex | SUSE CVE CVE-2017-7043 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T00:43:33+00:00 | Vulnerability · Source |
| CVE-2017-7059 | suse_vex | SUSE CVE CVE-2017-7059 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:26+00:00 | Vulnerability · Source |
| CVE-2017-7061 | suse_vex | SUSE CVE CVE-2017-7061 | known affected: 12 known not affected: 329 recommended: 927 | 2026-07-26T00:43:24+00:00 | Vulnerability · Source |
| CVE-2017-7087 | suse_vex | SUSE CVE CVE-2017-7087 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:21+00:00 | Vulnerability · Source |
| CVE-2017-7090 | suse_vex | SUSE CVE CVE-2017-7090 | known not affected: 87 recommended: 927 | 2026-07-26T00:43:19+00:00 | Vulnerability · Source |