VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
284903 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| 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-5462 | suse_vex | SUSE CVE CVE-2017-5462 | known not affected: 42 recommended: 768 | 2026-07-26T00:45:46+00:00 | Vulnerability · Source |
| CVE-2017-5467 | suse_vex | SUSE CVE CVE-2017-5467 | known affected: 2 known not affected: 42 recommended: 474 | 2026-07-26T00:45:45+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-5485 | suse_vex | SUSE CVE CVE-2017-5485 | known affected: 320 recommended: 186 | 2026-07-26T00:45:41+00:00 | Vulnerability · Source |
| CVE-2017-5486 | suse_vex | SUSE CVE CVE-2017-5486 | known affected: 320 recommended: 186 | 2026-07-26T00:45:40+00:00 | Vulnerability · Source |
| CVE-2017-5504 | suse_vex | SUSE CVE CVE-2017-5504 | known affected: 46 recommended: 150 | 2026-07-26T00:45:39+00:00 | Vulnerability · Source |
| CVE-2017-5505 | suse_vex | SUSE CVE CVE-2017-5505 | known affected: 46 known not affected: 16 recommended: 150 | 2026-07-26T00:45:38+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-5578 | suse_vex | SUSE CVE CVE-2017-5578 | known affected: 420 known not affected: 251 recommended: 1754 | 2026-07-26T00:45:23+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-5664 | suse_vex | SUSE CVE CVE-2017-5664 | known affected: 440 known not affected: 122 recommended: 252 | 2026-07-26T00:45:15+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-5731 | suse_vex | SUSE CVE CVE-2017-5731 | known affected: 29 recommended: 241 | 2026-07-26T00:45:12+00:00 | Vulnerability · Source |
| CVE-2017-5733 | suse_vex | SUSE CVE CVE-2017-5733 | known affected: 29 recommended: 234 | 2026-07-26T00:45:11+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-5834 | suse_vex | SUSE CVE CVE-2017-5834 | known affected: 34 recommended: 365 | 2026-07-26T00:45:05+00:00 | Vulnerability · Source |
| CVE-2017-5838 | suse_vex | SUSE CVE CVE-2017-5838 | known affected: 86 recommended: 2416 | 2026-07-26T00:45:03+00:00 | Vulnerability · Source |
| CVE-2017-5842 | suse_vex | SUSE CVE CVE-2017-5842 | known affected: 270 recommended: 1005 | 2026-07-26T00:45:02+00:00 | Vulnerability · Source |
| CVE-2017-5845 | suse_vex | SUSE CVE CVE-2017-5845 | known not affected: 6 recommended: 448 | 2026-07-26T00:45:01+00:00 | Vulnerability · Source |
| CVE-2017-5848 | suse_vex | SUSE CVE CVE-2017-5848 | known affected: 26 known not affected: 61 recommended: 2289 | 2026-07-26T00:44:59+00:00 | Vulnerability · Source |
| CVE-2017-5857 | suse_vex | SUSE CVE CVE-2017-5857 | known affected: 420 known not affected: 251 recommended: 1754 | 2026-07-26T00:44:57+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-5937 | suse_vex | SUSE CVE CVE-2017-5937 | recommended: 134 | 2026-07-26T00:44:52+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-5973 | suse_vex | SUSE CVE CVE-2017-5973 | known affected: 394 known not affected: 137 recommended: 1875 | 2026-07-26T00:44:46+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-5994 | suse_vex | SUSE CVE CVE-2017-5994 | recommended: 134 | 2026-07-26T00:44:42+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 |