VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285057 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2017-5898 | suse_vex | SUSE CVE CVE-2017-5898 | known affected: 394 known not affected: 156 recommended: 1923 | 2026-07-26T16:59:52+00:00 | Vulnerability · Source |
| CVE-2017-6004 | suse_vex | SUSE CVE CVE-2017-6004 | known affected: 349 known not affected: 521 recommended: 731 | 2026-07-26T16:59:50+00:00 | Vulnerability · Source |
| CVE-2017-6210 | suse_vex | SUSE CVE CVE-2017-6210 | recommended: 29 | 2026-07-26T16:59:48+00:00 | Vulnerability · Source |
| CVE-2017-6505 | suse_vex | SUSE CVE CVE-2017-6505 | known affected: 320 known not affected: 212 recommended: 2310 | 2026-07-26T16:59:46+00:00 | Vulnerability · Source |
| CVE-2017-6507 | suse_vex | SUSE CVE CVE-2017-6507 | known affected: 342 known not affected: 320 recommended: 1074 | 2026-07-26T16:59:44+00:00 | Vulnerability · Source |
| CVE-2017-7052 | suse_vex | SUSE CVE CVE-2017-7052 | known affected: 12 known not affected: 329 recommended: 939 | 2026-07-26T16:59:42+00:00 | Vulnerability · Source |
| CVE-2017-7100 | suse_vex | SUSE CVE CVE-2017-7100 | known not affected: 87 recommended: 927 | 2026-07-26T16:59:40+00:00 | Vulnerability · Source |
| CVE-2017-7120 | suse_vex | SUSE CVE CVE-2017-7120 | known not affected: 87 recommended: 927 | 2026-07-26T16:59:39+00:00 | Vulnerability · Source |
| CVE-2017-7224 | suse_vex | SUSE CVE CVE-2017-7224 | known affected: 442 known not affected: 21 recommended: 340 | 2026-07-26T16:59:37+00:00 | Vulnerability · Source |
| CVE-2017-7511 | suse_vex | SUSE CVE CVE-2017-7511 | known affected: 60 known not affected: 39 recommended: 583 | 2026-07-26T16:59:35+00:00 | Vulnerability · Source |
| CVE-2017-7547 | suse_vex | SUSE CVE CVE-2017-7547 | known not affected: 45 recommended: 264 | 2026-07-26T16:59:33+00:00 | Vulnerability · Source |
| CVE-2017-7586 | suse_vex | SUSE CVE CVE-2017-7586 | known affected: 44 known not affected: 14 recommended: 172 | 2026-07-26T16:59:32+00:00 | Vulnerability · Source |
| CVE-2017-7718 | suse_vex | SUSE CVE CVE-2017-7718 | known affected: 26 known not affected: 280 recommended: 268 | 2026-07-26T16:59:30+00:00 | Vulnerability · Source |
| CVE-2017-7753 | suse_vex | SUSE CVE CVE-2017-7753 | known affected: 1 known not affected: 42 recommended: 417 | 2026-07-26T16:59:28+00:00 | Vulnerability · Source |
| CVE-2017-7819 | suse_vex | SUSE CVE CVE-2017-7819 | known not affected: 42 recommended: 650 | 2026-07-26T16:59:27+00:00 | Vulnerability · Source |
| CVE-2017-7843 | suse_vex | SUSE CVE CVE-2017-7843 | known not affected: 143 recommended: 250 | 2026-07-26T16:59:25+00:00 | Vulnerability · Source |
| CVE-2017-8069 | suse_vex | SUSE CVE CVE-2017-8069 | known not affected: 34 | 2026-07-26T16:59:23+00:00 | Vulnerability · Source |
| CVE-2017-8086 | suse_vex | SUSE CVE CVE-2017-8086 | known affected: 26 known not affected: 107 recommended: 124 | 2026-07-26T16:59:22+00:00 | Vulnerability · Source |
| CVE-2017-8380 | suse_vex | SUSE CVE CVE-2017-8380 | known affected: 420 known not affected: 141 recommended: 1793 | 2026-07-26T16:59:20+00:00 | Vulnerability · Source |
| CVE-2017-9076 | suse_vex | SUSE CVE CVE-2017-9076 | known affected: 14 known not affected: 345 recommended: 444 | 2026-07-26T16:59:18+00:00 | Vulnerability · Source |
| CVE-2017-9112 | suse_vex | SUSE CVE CVE-2017-9112 | known affected: 5 known not affected: 79 recommended: 229 | 2026-07-26T16:59:16+00:00 | Vulnerability · Source |
| CVE-2017-9242 | suse_vex | SUSE CVE CVE-2017-9242 | known affected: 14 known not affected: 420 recommended: 554 | 2026-07-26T16:59:14+00:00 | Vulnerability · Source |
| CVE-2017-9408 | suse_vex | SUSE CVE CVE-2017-9408 | known affected: 60 known not affected: 39 recommended: 151 | 2026-07-26T16:59:13+00:00 | Vulnerability · Source |
| CVE-2017-10911 | suse_vex | SUSE CVE CVE-2017-10911 | known affected: 28 known not affected: 1412 recommended: 292 | 2026-07-26T16:59:10+00:00 | Vulnerability · Source |
| CVE-2017-10928 | suse_vex | SUSE CVE CVE-2017-10928 | known affected: 7 known not affected: 14 recommended: 136 | 2026-07-26T16:59:09+00:00 | Vulnerability · Source |
| CVE-2017-10985 | suse_vex | SUSE CVE CVE-2017-10985 | known affected: 24 known not affected: 111 recommended: 625 | 2026-07-26T16:59:07+00:00 | Vulnerability · Source |
| CVE-2017-11531 | suse_vex | SUSE CVE CVE-2017-11531 | known affected: 94 known not affected: 70 recommended: 136 | 2026-07-26T16:59:05+00:00 | Vulnerability · Source |
| CVE-2017-11643 | suse_vex | SUSE CVE CVE-2017-11643 | known affected: 3 known not affected: 128 recommended: 14 | 2026-07-26T16:59:03+00:00 | Vulnerability · Source |
| CVE-2017-11752 | suse_vex | SUSE CVE CVE-2017-11752 | known affected: 94 known not affected: 14 recommended: 172 | 2026-07-26T16:59:02+00:00 | Vulnerability · Source |
| CVE-2017-12177 | suse_vex | SUSE CVE CVE-2017-12177 | known affected: 2 known not affected: 38 recommended: 42 | 2026-07-26T16:59:00+00:00 | Vulnerability · Source |
| CVE-2017-12374 | suse_vex | SUSE CVE CVE-2017-12374 | known affected: 1 known not affected: 78 recommended: 280 | 2026-07-26T16:58:59+00:00 | Vulnerability · Source |
| CVE-2017-12380 | suse_vex | SUSE CVE CVE-2017-12380 | known affected: 1 known not affected: 78 recommended: 280 | 2026-07-26T16:58:57+00:00 | Vulnerability · Source |
| CVE-2017-12427 | suse_vex | SUSE CVE CVE-2017-12427 | known affected: 95 recommended: 186 | 2026-07-26T16:58:56+00:00 | Vulnerability · Source |
| CVE-2017-12641 | suse_vex | SUSE CVE CVE-2017-12641 | known affected: 94 recommended: 186 | 2026-07-26T16:58:54+00:00 | Vulnerability · Source |
| CVE-2017-12935 | suse_vex | SUSE CVE CVE-2017-12935 | known affected: 94 known not affected: 91 recommended: 186 | 2026-07-26T16:58:52+00:00 | Vulnerability · Source |
| CVE-2017-13050 | suse_vex | SUSE CVE CVE-2017-13050 | known affected: 336 known not affected: 24 recommended: 147 | 2026-07-26T16:58:50+00:00 | Vulnerability · Source |
| CVE-2017-13061 | suse_vex | SUSE CVE CVE-2017-13061 | known affected: 95 recommended: 186 | 2026-07-26T16:58:48+00:00 | Vulnerability · Source |
| CVE-2017-14033 | suse_vex | SUSE CVE CVE-2017-14033 | known affected: 1 known not affected: 55 recommended: 98 | 2026-07-26T16:58:46+00:00 | Vulnerability · Source |
| CVE-2017-14129 | suse_vex | SUSE CVE CVE-2017-14129 | known affected: 394 known not affected: 21 recommended: 330 | 2026-07-26T16:58:45+00:00 | Vulnerability · Source |
| CVE-2017-14164 | suse_vex | SUSE CVE CVE-2017-14164 | known not affected: 65 recommended: 200 | 2026-07-26T16:58:43+00:00 | Vulnerability · Source |
| CVE-2017-14318 | suse_vex | SUSE CVE CVE-2017-14318 | known affected: 31 known not affected: 125 recommended: 111 | 2026-07-26T16:58:42+00:00 | Vulnerability · Source |
| CVE-2017-14520 | suse_vex | SUSE CVE CVE-2017-14520 | known affected: 60 known not affected: 39 recommended: 111 | 2026-07-26T16:58:40+00:00 | Vulnerability · Source |
| CVE-2017-14632 | suse_vex | SUSE CVE CVE-2017-14632 | known affected: 509 known not affected: 120 recommended: 402 | 2026-07-26T16:58:38+00:00 | Vulnerability · Source |
| CVE-2017-14684 | suse_vex | SUSE CVE CVE-2017-14684 | known affected: 10 known not affected: 144 | 2026-07-26T16:58:37+00:00 | Vulnerability · Source |
| CVE-2017-14864 | suse_vex | SUSE CVE CVE-2017-14864 | known affected: 81 known not affected: 60 recommended: 186 | 2026-07-26T16:58:35+00:00 | Vulnerability · Source |
| CVE-2017-15041 | suse_vex | SUSE CVE CVE-2017-15041 | known not affected: 160 recommended: 61 | 2026-07-26T16:58:34+00:00 | Vulnerability · Source |
| CVE-2017-16879 | suse_vex | SUSE CVE CVE-2017-16879 | known not affected: 667 recommended: 50 | 2026-07-26T16:58:31+00:00 | Vulnerability · Source |
| CVE-2017-17085 | suse_vex | SUSE CVE CVE-2017-17085 | known not affected: 115 recommended: 606 | 2026-07-26T16:58:30+00:00 | Vulnerability · Source |
| CVE-2017-17857 | suse_vex | SUSE CVE CVE-2017-17857 | known not affected: 182 recommended: 299 | 2026-07-26T16:58:27+00:00 | Vulnerability · Source |
| CVE-2017-18043 | suse_vex | SUSE CVE CVE-2017-18043 | known affected: 69 known not affected: 11 recommended: 218 | 2026-07-26T16:58:26+00:00 | Vulnerability · Source |