VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
286614 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-6435 | suse_vex | SUSE CVE CVE-2017-6435 | recommended: 335 | 2026-07-28T00:08:41+00:00 | Vulnerability · Source |
| CVE-2017-6458 | suse_vex | SUSE CVE CVE-2017-6458 | known affected: 24 recommended: 90 | 2026-07-28T00:08:40+00:00 | Vulnerability · Source |
| CVE-2017-6473 | suse_vex | SUSE CVE CVE-2017-6473 | known affected: 61 recommended: 444 | 2026-07-28T00:08:39+00:00 | Vulnerability · Source |
| CVE-2017-6502 | suse_vex | SUSE CVE CVE-2017-6502 | known not affected: 47 recommended: 128 | 2026-07-28T00:08:37+00:00 | Vulnerability · Source |
| CVE-2017-6512 | suse_vex | SUSE CVE CVE-2017-6512 | known affected: 237 recommended: 503 | 2026-07-28T00:08:36+00:00 | Vulnerability · Source |
| CVE-2017-6837 | suse_vex | SUSE CVE CVE-2017-6837 | known affected: 34 recommended: 190 | 2026-07-28T00:08:35+00:00 | Vulnerability · Source |
| CVE-2017-6850 | suse_vex | SUSE CVE CVE-2017-6850 | known affected: 31 known not affected: 111 recommended: 192 | 2026-07-28T00:08:33+00:00 | Vulnerability · Source |
| CVE-2017-7041 | suse_vex | SUSE CVE CVE-2017-7041 | known affected: 6 known not affected: 321 recommended: 912 | 2026-07-28T00:08:32+00:00 | Vulnerability · Source |
| CVE-2017-7056 | suse_vex | SUSE CVE CVE-2017-7056 | known affected: 6 known not affected: 321 recommended: 924 | 2026-07-28T00:08:30+00:00 | Vulnerability · Source |
| CVE-2017-7089 | suse_vex | SUSE CVE CVE-2017-7089 | known not affected: 69 recommended: 906 | 2026-07-28T00:08:29+00:00 | Vulnerability · Source |
| CVE-2017-7104 | suse_vex | SUSE CVE CVE-2017-7104 | known not affected: 69 recommended: 906 | 2026-07-28T00:08:28+00:00 | Vulnerability · Source |
| CVE-2017-7117 | suse_vex | SUSE CVE CVE-2017-7117 | known not affected: 87 recommended: 924 | 2026-07-28T00:08:26+00:00 | Vulnerability · Source |
| CVE-2017-7475 | suse_vex | SUSE CVE CVE-2017-7475 | known affected: 465 recommended: 408 | 2026-07-28T00:08:24+00:00 | Vulnerability · Source |
| CVE-2017-7507 | suse_vex | SUSE CVE CVE-2017-7507 | known affected: 4 known not affected: 25 recommended: 35 | 2026-07-28T00:08:22+00:00 | Vulnerability · Source |
| CVE-2017-7515 | suse_vex | SUSE CVE CVE-2017-7515 | recommended: 572 | 2026-07-28T00:08:21+00:00 | Vulnerability · Source |
| CVE-2017-7526 | suse_vex | SUSE CVE CVE-2017-7526 | known affected: 379 recommended: 464 | 2026-07-28T00:08:19+00:00 | Vulnerability · Source |
| CVE-2017-7541 | suse_vex | SUSE CVE CVE-2017-7541 | known not affected: 313 recommended: 480 | 2026-07-28T00:08:18+00:00 | Vulnerability · Source |
| CVE-2017-7555 | suse_vex | SUSE CVE CVE-2017-7555 | known affected: 311 known not affected: 75 recommended: 421 | 2026-07-28T00:08:16+00:00 | Vulnerability · Source |
| CVE-2017-7558 | suse_vex | SUSE CVE CVE-2017-7558 | known not affected: 14 recommended: 12 | 2026-07-28T00:08:15+00:00 | Vulnerability · Source |
| CVE-2017-7585 | suse_vex | SUSE CVE CVE-2017-7585 | known affected: 402 known not affected: 4 recommended: 180 | 2026-07-28T00:08:13+00:00 | Vulnerability · Source |
| CVE-2017-7608 | suse_vex | SUSE CVE CVE-2017-7608 | known affected: 494 known not affected: 1 recommended: 806 | 2026-07-28T00:08:12+00:00 | Vulnerability · Source |
| CVE-2017-7763 | suse_vex | SUSE CVE CVE-2017-7763 | known affected: 2 known not affected: 42 recommended: 216 | 2026-07-28T00:08:10+00:00 | Vulnerability · Source |
| CVE-2017-7785 | suse_vex | SUSE CVE CVE-2017-7785 | known affected: 1 known not affected: 42 recommended: 411 | 2026-07-28T00:08:07+00:00 | Vulnerability · Source |
| CVE-2017-7789 | suse_vex | SUSE CVE CVE-2017-7789 | known not affected: 60 recommended: 74 | 2026-07-28T00:08:06+00:00 | Vulnerability · Source |
| CVE-2017-7798 | suse_vex | SUSE CVE CVE-2017-7798 | known affected: 1 known not affected: 34 recommended: 406 | 2026-07-28T00:08:04+00:00 | Vulnerability · Source |
| CVE-2017-7812 | suse_vex | SUSE CVE CVE-2017-7812 | known not affected: 34 recommended: 12 | 2026-07-28T00:08:03+00:00 | Vulnerability · Source |
| CVE-2017-7824 | suse_vex | SUSE CVE CVE-2017-7824 | known not affected: 34 recommended: 610 | 2026-07-28T00:08:01+00:00 | Vulnerability · Source |
| CVE-2017-7868 | suse_vex | SUSE CVE CVE-2017-7868 | recommended: 124 | 2026-07-28T00:07:59+00:00 | Vulnerability · Source |
| CVE-2017-8347 | suse_vex | SUSE CVE CVE-2017-8347 | known not affected: 48 recommended: 128 | 2026-07-28T00:07:58+00:00 | Vulnerability · Source |
| CVE-2017-8355 | suse_vex | SUSE CVE CVE-2017-8355 | recommended: 178 | 2026-07-28T00:07:57+00:00 | Vulnerability · Source |
| CVE-2017-8356 | suse_vex | SUSE CVE CVE-2017-8356 | known not affected: 48 recommended: 128 | 2026-07-28T00:07:55+00:00 | Vulnerability · Source |
| CVE-2017-8872 | suse_vex | SUSE CVE CVE-2017-8872 | known affected: 53 known not affected: 131 recommended: 102 | 2026-07-28T00:07:53+00:00 | Vulnerability · Source |
| CVE-2017-8905 | suse_vex | SUSE CVE CVE-2017-8905 | known not affected: 13 recommended: 83 | 2026-07-28T00:07:52+00:00 | Vulnerability · Source |
| CVE-2017-9047 | suse_vex | SUSE CVE CVE-2017-9047 | known affected: 309 known not affected: 86 recommended: 550 | 2026-07-28T00:07:50+00:00 | Vulnerability · Source |
| CVE-2017-9060 | suse_vex | SUSE CVE CVE-2017-9060 | known not affected: 57 | 2026-07-28T00:07:49+00:00 | Vulnerability · Source |
| CVE-2017-9144 | suse_vex | SUSE CVE CVE-2017-9144 | recommended: 178 | 2026-07-28T00:07:47+00:00 | Vulnerability · Source |
| CVE-2017-9148 | suse_vex | SUSE CVE CVE-2017-9148 | known not affected: 155 recommended: 607 | 2026-07-28T00:07:46+00:00 | Vulnerability · Source |
| CVE-2017-9262 | suse_vex | SUSE CVE CVE-2017-9262 | known affected: 75 recommended: 180 | 2026-07-28T00:07:44+00:00 | Vulnerability · Source |
| CVE-2017-9348 | suse_vex | SUSE CVE CVE-2017-9348 | known affected: 3 known not affected: 181 recommended: 535 | 2026-07-28T00:07:42+00:00 | Vulnerability · Source |
| CVE-2017-9354 | suse_vex | SUSE CVE CVE-2017-9354 | known affected: 3 known not affected: 181 recommended: 535 | 2026-07-28T00:07:41+00:00 | Vulnerability · Source |
| CVE-2017-9375 | suse_vex | SUSE CVE CVE-2017-9375 | known affected: 13 recommended: 108 | 2026-07-28T00:07:40+00:00 | Vulnerability · Source |
| CVE-2017-9748 | suse_vex | SUSE CVE CVE-2017-9748 | known affected: 394 known not affected: 352 recommended: 336 | 2026-07-28T00:07:38+00:00 | Vulnerability · Source |
| CVE-2017-9749 | suse_vex | SUSE CVE CVE-2017-9749 | known affected: 8 known not affected: 41 | 2026-07-28T00:07:36+00:00 | Vulnerability · Source |
| CVE-2017-10078 | suse_vex | SUSE CVE CVE-2017-10078 | known not affected: 57 recommended: 488 | 2026-07-28T00:07:35+00:00 | Vulnerability · Source |
| CVE-2017-10176 | suse_vex | SUSE CVE CVE-2017-10176 | recommended: 311 | 2026-07-28T00:07:33+00:00 | Vulnerability · Source |
| CVE-2017-10295 | suse_vex | SUSE CVE CVE-2017-10295 | known affected: 80 known not affected: 209 recommended: 713 | 2026-07-28T00:07:31+00:00 | Vulnerability · Source |
| CVE-2017-10348 | suse_vex | SUSE CVE CVE-2017-10348 | known affected: 64 known not affected: 245 recommended: 713 | 2026-07-28T00:07:30+00:00 | Vulnerability · Source |
| CVE-2017-10800 | suse_vex | SUSE CVE CVE-2017-10800 | recommended: 188 | 2026-07-28T00:07:28+00:00 | Vulnerability · Source |
| CVE-2017-10810 | suse_vex | SUSE CVE CVE-2017-10810 | known not affected: 277 recommended: 102 | 2026-07-28T00:07:26+00:00 | Vulnerability · Source |
| CVE-2017-10918 | suse_vex | SUSE CVE CVE-2017-10918 | known affected: 7 known not affected: 6 recommended: 43 | 2026-07-28T00:07:25+00:00 | Vulnerability · Source |