VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
285025 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-9923 | suse_vex | SUSE CVE CVE-2016-9923 | known not affected: 136 recommended: 1641 | 2026-07-26T17:00:15+00:00 | Vulnerability · Source |
| CVE-2016-10169 | suse_vex | SUSE CVE CVE-2016-10169 | known affected: 30 recommended: 57 | 2026-07-26T17:00:13+00:00 | Vulnerability · Source |
| CVE-2016-10251 | suse_vex | SUSE CVE CVE-2016-10251 | known affected: 37 known not affected: 113 recommended: 204 | 2026-07-26T17:00:11+00:00 | Vulnerability · Source |
| CVE-2016-10268 | suse_vex | SUSE CVE CVE-2016-10268 | known affected: 441 known not affected: 80 recommended: 298 | 2026-07-26T17:00:09+00:00 | Vulnerability · Source |
| CVE-2016-10371 | suse_vex | SUSE CVE CVE-2016-10371 | known affected: 438 known not affected: 99 recommended: 264 | 2026-07-26T17:00:07+00:00 | Vulnerability · Source |
| CVE-2017-2354 | suse_vex | SUSE CVE CVE-2017-2354 | known not affected: 248 recommended: 927 | 2026-07-26T17:00:05+00:00 | Vulnerability · Source |
| CVE-2017-2587 | suse_vex | SUSE CVE CVE-2017-2587 | known affected: 16 recommended: 56 | 2026-07-26T17:00:04+00:00 | Vulnerability · Source |
| CVE-2017-3231 | suse_vex | SUSE CVE CVE-2017-3231 | known affected: 124 known not affected: 166 recommended: 584 | 2026-07-26T17:00:02+00:00 | Vulnerability · Source |
| CVE-2017-3289 | suse_vex | SUSE CVE CVE-2017-3289 | known affected: 114 known not affected: 166 recommended: 584 | 2026-07-26T17:00:00+00:00 | Vulnerability · Source |
| CVE-2017-3639 | suse_vex | SUSE CVE CVE-2017-3639 | known affected: 1 known not affected: 64 | 2026-07-26T16:59:58+00:00 | Vulnerability · Source |
| CVE-2017-5465 | suse_vex | SUSE CVE CVE-2017-5465 | known not affected: 42 recommended: 770 | 2026-07-26T16:59:56+00:00 | Vulnerability · Source |
| CVE-2017-5563 | suse_vex | SUSE CVE CVE-2017-5563 | known not affected: 47 | 2026-07-26T16:59:54+00:00 | Vulnerability · Source |
| 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 |