VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291935 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-5240 | suse_vex | SUSE CVE CVE-2016-5240 | known not affected: 109 recommended: 20 | 2026-08-02T16:55:45+00:00 | Vulnerability · Source |
| CVE-2016-5265 | suse_vex | SUSE CVE CVE-2016-5265 | known affected: 5 recommended: 438 | 2026-08-02T16:55:43+00:00 | Vulnerability · Source |
| CVE-2016-5292 | suse_vex | SUSE CVE CVE-2016-5292 | known affected: 1 known not affected: 24 recommended: 321 | 2026-08-02T16:55:40+00:00 | Vulnerability · Source |
| CVE-2016-5549 | suse_vex | SUSE CVE CVE-2016-5549 | known affected: 124 known not affected: 166 recommended: 561 | 2026-08-02T16:55:35+00:00 | Vulnerability · Source |
| CVE-2016-6307 | suse_vex | SUSE CVE CVE-2016-6307 | known not affected: 102 | 2026-08-02T16:55:29+00:00 | Vulnerability · Source |
| CVE-2016-6786 | suse_vex | SUSE CVE CVE-2016-6786 | known not affected: 529 | 2026-08-02T16:55:27+00:00 | Vulnerability · Source |
| CVE-2016-6888 | suse_vex | SUSE CVE CVE-2016-6888 | known affected: 1 known not affected: 178 recommended: 1831 | 2026-08-02T16:55:25+00:00 | Vulnerability · Source |
| CVE-2016-7908 | suse_vex | SUSE CVE CVE-2016-7908 | known affected: 349 known not affected: 169 recommended: 2390 | 2026-08-02T16:55:21+00:00 | Vulnerability · Source |
| CVE-2016-7909 | suse_vex | SUSE CVE CVE-2016-7909 | known affected: 347 known not affected: 157 recommended: 2390 | 2026-08-02T16:55:18+00:00 | Vulnerability · Source |
| CVE-2016-8668 | suse_vex | SUSE CVE CVE-2016-8668 | known affected: 420 known not affected: 136 recommended: 1754 | 2026-08-02T16:55:15+00:00 | Vulnerability · Source |
| CVE-2016-8735 | suse_vex | SUSE CVE CVE-2016-8735 | known affected: 46 recommended: 192 | 2026-08-02T16:55:12+00:00 | Vulnerability · Source |
| CVE-2016-9103 | suse_vex | SUSE CVE CVE-2016-9103 | known affected: 395 known not affected: 192 recommended: 1834 | 2026-08-02T16:55:10+00:00 | Vulnerability · Source |
| CVE-2016-9312 | suse_vex | SUSE CVE CVE-2016-9312 | known affected: 4 known not affected: 16 | 2026-08-02T16:55:07+00:00 | Vulnerability · Source |
| CVE-2016-9423 | suse_vex | SUSE CVE CVE-2016-9423 | known not affected: 35 recommended: 4 | 2026-08-02T16:55:04+00:00 | Vulnerability · Source |
| CVE-2016-9574 | suse_vex | SUSE CVE CVE-2016-9574 | known affected: 1 recommended: 512 | 2026-08-02T16:55:01+00:00 | Vulnerability · Source |
| CVE-2016-9793 | suse_vex | SUSE CVE CVE-2016-9793 | known affected: 12 known not affected: 73 recommended: 404 | 2026-08-02T16:54:59+00:00 | Vulnerability · Source |
| CVE-2016-10025 | suse_vex | SUSE CVE CVE-2016-10025 | known affected: 332 known not affected: 104 recommended: 430 | 2026-08-02T16:54:56+00:00 | Vulnerability · Source |
| CVE-2016-10088 | suse_vex | SUSE CVE CVE-2016-10088 | known not affected: 379 recommended: 331 | 2026-08-02T16:54:53+00:00 | Vulnerability · Source |
| CVE-2016-10154 | suse_vex | SUSE CVE CVE-2016-10154 | known not affected: 34 | 2026-08-02T16:54:50+00:00 | Vulnerability · Source |
| CVE-2016-10195 | suse_vex | SUSE CVE CVE-2016-10195 | known affected: 30 recommended: 39 | 2026-08-02T16:54:48+00:00 | Vulnerability · Source |
| CVE-2016-10708 | suse_vex | SUSE CVE CVE-2016-10708 | known affected: 19 recommended: 107 | 2026-08-02T16:54:44+00:00 | Vulnerability · Source |
| CVE-2016-10764 | suse_vex | SUSE CVE CVE-2016-10764 | known not affected: 229 | 2026-08-02T16:54:42+00:00 | Vulnerability · Source |
| CVE-2017-5391 | suse_vex | SUSE CVE CVE-2017-5391 | known affected: 1 known not affected: 38 recommended: 249 | 2026-08-02T16:54:33+00:00 | Vulnerability · Source |
| CVE-2017-5402 | suse_vex | SUSE CVE CVE-2017-5402 | known affected: 1 recommended: 416 | 2026-08-02T16:54:31+00:00 | Vulnerability · Source |
| CVE-2017-6214 | suse_vex | SUSE CVE CVE-2017-6214 | known not affected: 364 recommended: 346 | 2026-08-02T16:54:21+00:00 | Vulnerability · Source |
| CVE-2017-6313 | suse_vex | SUSE CVE CVE-2017-6313 | known affected: 394 known not affected: 136 recommended: 672 | 2026-08-02T16:54:19+00:00 | Vulnerability · Source |
| CVE-2017-7542 | suse_vex | SUSE CVE CVE-2017-7542 | known affected: 26 known not affected: 406 recommended: 667 | 2026-08-02T16:54:10+00:00 | Vulnerability · Source |
| CVE-2017-7834 | suse_vex | SUSE CVE CVE-2017-7834 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-02T16:54:05+00:00 | Vulnerability · Source |
| CVE-2017-9043 | suse_vex | SUSE CVE CVE-2017-9043 | known not affected: 33 recommended: 54 | 2026-08-02T16:54:02+00:00 | Vulnerability · Source |
| CVE-2017-9106 | suse_vex | SUSE CVE CVE-2017-9106 | known affected: 18 recommended: 49 | 2026-08-02T16:54:00+00:00 | Vulnerability · Source |
| CVE-2017-9125 | suse_vex | SUSE CVE CVE-2017-9125 | known affected: 30 recommended: 208 | 2026-08-02T16:53:57+00:00 | Vulnerability · Source |
| CVE-2017-11499 | suse_vex | SUSE CVE CVE-2017-11499 | known not affected: 310 recommended: 495 | 2026-08-02T16:53:51+00:00 | Vulnerability · Source |
| CVE-2017-11523 | suse_vex | SUSE CVE CVE-2017-11523 | known affected: 94 known not affected: 50 recommended: 136 | 2026-08-02T16:53:50+00:00 | Vulnerability · Source |
| CVE-2017-11530 | suse_vex | SUSE CVE CVE-2017-11530 | known affected: 94 known not affected: 14 recommended: 172 | 2026-08-02T16:53:49+00:00 | Vulnerability · Source |
| CVE-2017-12185 | suse_vex | SUSE CVE CVE-2017-12185 | known affected: 2 known not affected: 51 recommended: 42 | 2026-08-02T16:53:46+00:00 | Vulnerability · Source |
| CVE-2017-13006 | suse_vex | SUSE CVE CVE-2017-13006 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-02T16:53:43+00:00 | Vulnerability · Source |
| CVE-2017-13747 | suse_vex | SUSE CVE CVE-2017-13747 | known affected: 6 known not affected: 56 | 2026-08-02T16:53:39+00:00 | Vulnerability · Source |
| CVE-2017-13758 | suse_vex | SUSE CVE CVE-2017-13758 | known not affected: 52 recommended: 150 | 2026-08-02T16:53:37+00:00 | Vulnerability · Source |
| CVE-2017-14061 | suse_vex | SUSE CVE CVE-2017-14061 | known affected: 8 known not affected: 272 | 2026-08-02T16:53:36+00:00 | Vulnerability · Source |
| CVE-2017-14989 | suse_vex | SUSE CVE CVE-2017-14989 | known affected: 94 known not affected: 50 recommended: 136 | 2026-08-02T16:53:33+00:00 | Vulnerability · Source |
| CVE-2017-15710 | suse_vex | SUSE CVE CVE-2017-15710 | known affected: 92 recommended: 168 | 2026-08-02T16:53:31+00:00 | Vulnerability · Source |
| CVE-2017-16527 | suse_vex | SUSE CVE CVE-2017-16527 | known not affected: 346 recommended: 496 | 2026-08-02T16:53:29+00:00 | Vulnerability · Source |
| CVE-2017-17052 | suse_vex | SUSE CVE CVE-2017-17052 | known not affected: 116 recommended: 293 | 2026-08-02T16:53:28+00:00 | Vulnerability · Source |
| CVE-2017-17500 | suse_vex | SUSE CVE CVE-2017-17500 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-02T16:53:25+00:00 | Vulnerability · Source |
| CVE-2017-1000377 | suse_vex | SUSE CVE CVE-2017-1000377 | known not affected: 298 | 2026-08-02T16:53:20+00:00 | Vulnerability · Source |
| CVE-2018-1111 | suse_vex | SUSE CVE CVE-2018-1111 | known not affected: 61 recommended: 5 | 2026-08-02T16:53:18+00:00 | Vulnerability · Source |
| CVE-2018-3630 | suse_vex | SUSE CVE CVE-2018-3630 | known affected: 50 recommended: 239 | 2026-08-02T16:53:15+00:00 | Vulnerability · Source |
| CVE-2018-10471 | suse_vex | SUSE CVE CVE-2018-10471 | known affected: 358 known not affected: 63 recommended: 535 | 2026-08-02T16:53:07+00:00 | Vulnerability · Source |
| CVE-2018-10938 | suse_vex | SUSE CVE CVE-2018-10938 | known affected: 140 known not affected: 273 recommended: 643 | 2026-08-02T16:53:05+00:00 | Vulnerability · Source |
| CVE-2018-12360 | suse_vex | SUSE CVE CVE-2018-12360 | known affected: 21 recommended: 451 | 2026-08-02T16:53:02+00:00 | Vulnerability · Source |