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-5335 | suse_vex | SUSE CVE CVE-2017-5335 | known affected: 8 known not affected: 4 recommended: 176 | 2026-07-26T00:46:41+00:00 | Vulnerability · Source |
| CVE-2017-5341 | suse_vex | SUSE CVE CVE-2017-5341 | known affected: 320 recommended: 182 | 2026-07-26T00:46:40+00:00 | Vulnerability · Source |
| CVE-2017-5378 | suse_vex | SUSE CVE CVE-2017-5378 | known affected: 1 recommended: 416 | 2026-07-26T00:46:38+00:00 | Vulnerability · Source |
| CVE-2017-5380 | suse_vex | SUSE CVE CVE-2017-5380 | known affected: 1 recommended: 416 | 2026-07-26T00:46:37+00:00 | Vulnerability · Source |
| CVE-2017-5383 | suse_vex | SUSE CVE CVE-2017-5383 | known affected: 1 recommended: 416 | 2026-07-26T00:46:33+00:00 | Vulnerability · Source |
| CVE-2017-5387 | suse_vex | SUSE CVE CVE-2017-5387 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:30+00:00 | Vulnerability · Source |
| CVE-2017-5390 | suse_vex | SUSE CVE CVE-2017-5390 | known affected: 1 recommended: 416 | 2026-07-26T00:46:27+00:00 | Vulnerability · Source |
| CVE-2017-5393 | suse_vex | SUSE CVE CVE-2017-5393 | known affected: 1 known not affected: 38 recommended: 249 | 2026-07-26T00:46:26+00:00 | Vulnerability · Source |
| CVE-2017-5396 | suse_vex | SUSE CVE CVE-2017-5396 | known affected: 1 recommended: 416 | 2026-07-26T00:46:24+00:00 | Vulnerability · Source |
| CVE-2017-5400 | suse_vex | SUSE CVE CVE-2017-5400 | known affected: 1 recommended: 416 | 2026-07-26T00:46:23+00:00 | Vulnerability · Source |
| CVE-2017-5403 | suse_vex | SUSE CVE CVE-2017-5403 | known affected: 1 recommended: 333 | 2026-07-26T00:46:21+00:00 | Vulnerability · Source |
| CVE-2017-5407 | suse_vex | SUSE CVE CVE-2017-5407 | known affected: 1 recommended: 416 | 2026-07-26T00:46:16+00:00 | Vulnerability · Source |
| CVE-2017-5408 | suse_vex | SUSE CVE CVE-2017-5408 | known affected: 1 recommended: 416 | 2026-07-26T00:46:14+00:00 | Vulnerability · Source |
| CVE-2017-5418 | suse_vex | SUSE CVE CVE-2017-5418 | known affected: 1 recommended: 333 | 2026-07-26T00:46:11+00:00 | Vulnerability · Source |
| CVE-2017-5425 | suse_vex | SUSE CVE CVE-2017-5425 | known affected: 1 | 2026-07-26T00:46:09+00:00 | Vulnerability · Source |
| CVE-2017-5426 | suse_vex | SUSE CVE CVE-2017-5426 | known affected: 1 recommended: 333 | 2026-07-26T00:46:08+00:00 | Vulnerability · Source |
| CVE-2017-5445 | suse_vex | SUSE CVE CVE-2017-5445 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:53+00:00 | Vulnerability · Source |
| CVE-2017-5449 | suse_vex | SUSE CVE CVE-2017-5449 | known affected: 2 known not affected: 42 recommended: 474 | 2026-07-26T00:45:50+00:00 | Vulnerability · Source |
| CVE-2017-5455 | suse_vex | SUSE CVE CVE-2017-5455 | known affected: 2 known not affected: 42 recommended: 389 | 2026-07-26T00:45:49+00:00 | Vulnerability · Source |
| CVE-2017-5459 | suse_vex | SUSE CVE CVE-2017-5459 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:47+00:00 | Vulnerability · Source |
| CVE-2017-5469 | suse_vex | SUSE CVE CVE-2017-5469 | known not affected: 42 recommended: 770 | 2026-07-26T00:45:43+00:00 | Vulnerability · Source |
| CVE-2017-5506 | suse_vex | SUSE CVE CVE-2017-5506 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:36+00:00 | Vulnerability · Source |
| CVE-2017-5508 | suse_vex | SUSE CVE CVE-2017-5508 | known affected: 1 known not affected: 14 recommended: 204 | 2026-07-26T00:45:35+00:00 | Vulnerability · Source |
| CVE-2017-5509 | suse_vex | SUSE CVE CVE-2017-5509 | known not affected: 113 | 2026-07-26T00:45:34+00:00 | Vulnerability · Source |
| CVE-2017-5510 | suse_vex | SUSE CVE CVE-2017-5510 | known not affected: 49 recommended: 168 | 2026-07-26T00:45:33+00:00 | Vulnerability · Source |
| CVE-2017-5511 | suse_vex | SUSE CVE CVE-2017-5511 | known affected: 1 recommended: 218 | 2026-07-26T00:45:31+00:00 | Vulnerability · Source |
| 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 |