VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291746 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-9379 | suse_vex | SUSE CVE CVE-2016-9379 | known affected: 334 known not affected: 6 recommended: 556 | 2026-08-05T01:29:49+00:00 | Vulnerability · Source |
| CVE-2016-9756 | suse_vex | SUSE CVE CVE-2016-9756 | known affected: 14 known not affected: 259 recommended: 314 | 2026-08-05T01:29:44+00:00 | Vulnerability · Source |
| CVE-2016-9801 | suse_vex | SUSE CVE CVE-2016-9801 | known affected: 20 known not affected: 13 recommended: 312 | 2026-08-05T01:29:43+00:00 | Vulnerability · Source |
| CVE-2016-10200 | suse_vex | SUSE CVE CVE-2016-10200 | known not affected: 364 recommended: 335 | 2026-08-05T01:29:40+00:00 | Vulnerability · Source |
| CVE-2016-10349 | suse_vex | SUSE CVE CVE-2016-10349 | known affected: 24 known not affected: 16 recommended: 25 | 2026-08-05T01:29:37+00:00 | Vulnerability · Source |
| CVE-2016-10507 | suse_vex | SUSE CVE CVE-2016-10507 | recommended: 21 | 2026-08-05T01:29:34+00:00 | Vulnerability · Source |
| CVE-2016-1000345 | suse_vex | SUSE CVE CVE-2016-1000345 | known not affected: 18 recommended: 134 | 2026-08-05T01:29:31+00:00 | Vulnerability · Source |
| CVE-2017-3533 | suse_vex | SUSE CVE CVE-2017-3533 | known affected: 1 known not affected: 109 recommended: 732 | 2026-08-05T01:29:28+00:00 | Vulnerability · Source |
| CVE-2017-3645 | suse_vex | SUSE CVE CVE-2017-3645 | known affected: 1 known not affected: 64 | 2026-08-05T01:29:25+00:00 | Vulnerability · Source |
| CVE-2017-5123 | suse_vex | SUSE CVE CVE-2017-5123 | known affected: 35 known not affected: 430 recommended: 6 | 2026-08-05T01:29:23+00:00 | Vulnerability · Source |
| CVE-2017-7099 | suse_vex | SUSE CVE CVE-2017-7099 | known not affected: 87 recommended: 927 | 2026-08-05T01:29:17+00:00 | Vulnerability · Source |
| CVE-2017-7102 | suse_vex | SUSE CVE CVE-2017-7102 | known not affected: 87 recommended: 927 | 2026-08-05T01:29:16+00:00 | Vulnerability · Source |
| CVE-2017-7645 | suse_vex | SUSE CVE CVE-2017-7645 | known affected: 12 known not affected: 274 recommended: 179 | 2026-08-05T01:29:12+00:00 | Vulnerability · Source |
| CVE-2017-8779 | suse_vex | SUSE CVE CVE-2017-8779 | known affected: 320 known not affected: 24 recommended: 249 | 2026-08-05T01:29:04+00:00 | Vulnerability · Source |
| CVE-2017-8797 | suse_vex | SUSE CVE CVE-2017-8797 | known not affected: 537 recommended: 22 | 2026-08-05T01:29:03+00:00 | Vulnerability · Source |
| CVE-2017-9108 | suse_vex | SUSE CVE CVE-2017-9108 | known affected: 18 recommended: 49 | 2026-08-05T01:29:01+00:00 | Vulnerability · Source |
| CVE-2017-9835 | suse_vex | SUSE CVE CVE-2017-9835 | known affected: 1 recommended: 85 | 2026-08-05T01:28:59+00:00 | Vulnerability · Source |
| CVE-2017-11140 | suse_vex | SUSE CVE CVE-2017-11140 | known affected: 3 known not affected: 85 recommended: 14 | 2026-08-05T01:28:57+00:00 | Vulnerability · Source |
| CVE-2017-11522 | suse_vex | SUSE CVE CVE-2017-11522 | known affected: 10 known not affected: 144 | 2026-08-05T01:28:55+00:00 | Vulnerability · Source |
| CVE-2017-12192 | suse_vex | SUSE CVE CVE-2017-12192 | known affected: 33 known not affected: 310 recommended: 23 | 2026-08-05T01:28:52+00:00 | Vulnerability · Source |
| CVE-2017-12377 | suse_vex | SUSE CVE CVE-2017-12377 | known affected: 1 known not affected: 78 recommended: 280 | 2026-08-05T01:28:51+00:00 | Vulnerability · Source |
| CVE-2017-12563 | suse_vex | SUSE CVE CVE-2017-12563 | known affected: 95 recommended: 186 | 2026-08-05T01:28:48+00:00 | Vulnerability · Source |
| CVE-2017-12989 | suse_vex | SUSE CVE CVE-2017-12989 | known affected: 336 known not affected: 24 recommended: 147 | 2026-08-05T01:28:46+00:00 | Vulnerability · Source |
| CVE-2017-13003 | suse_vex | SUSE CVE CVE-2017-13003 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-05T01:28:44+00:00 | Vulnerability · Source |
| CVE-2017-13051 | suse_vex | SUSE CVE CVE-2017-13051 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-05T01:28:42+00:00 | Vulnerability · Source |
| CVE-2017-13084 | suse_vex | SUSE CVE CVE-2017-13084 | known affected: 6 known not affected: 354 | 2026-08-05T01:28:40+00:00 | Vulnerability · Source |
| CVE-2017-13147 | suse_vex | SUSE CVE CVE-2017-13147 | known affected: 94 recommended: 186 | 2026-08-05T01:28:38+00:00 | Vulnerability · Source |
| CVE-2017-13673 | suse_vex | SUSE CVE CVE-2017-13673 | known affected: 394 known not affected: 163 recommended: 1738 | 2026-08-05T01:28:34+00:00 | Vulnerability · Source |
| CVE-2017-13721 | suse_vex | SUSE CVE CVE-2017-13721 | known affected: 394 known not affected: 29 recommended: 262 | 2026-08-05T01:28:32+00:00 | Vulnerability · Source |
| CVE-2017-14245 | suse_vex | SUSE CVE CVE-2017-14245 | known affected: 394 known not affected: 68 recommended: 179 | 2026-08-05T01:28:29+00:00 | Vulnerability · Source |
| CVE-2017-14248 | suse_vex | SUSE CVE CVE-2017-14248 | known not affected: 301 | 2026-08-05T01:28:27+00:00 | Vulnerability · Source |
| CVE-2017-14952 | suse_vex | SUSE CVE CVE-2017-14952 | recommended: 136 | 2026-08-05T01:28:25+00:00 | Vulnerability · Source |
| CVE-2017-14994 | suse_vex | SUSE CVE CVE-2017-14994 | known affected: 3 known not affected: 128 recommended: 14 | 2026-08-05T01:28:24+00:00 | Vulnerability · Source |
| CVE-2017-15275 | suse_vex | SUSE CVE CVE-2017-15275 | known affected: 854 known not affected: 475 recommended: 3972 | 2026-08-05T01:28:21+00:00 | Vulnerability · Source |
| CVE-2017-15281 | suse_vex | SUSE CVE CVE-2017-15281 | known affected: 95 known not affected: 14 recommended: 172 | 2026-08-05T01:28:20+00:00 | Vulnerability · Source |
| CVE-2017-15400 | suse_vex | SUSE CVE CVE-2017-15400 | known not affected: 123 | 2026-08-05T01:28:18+00:00 | Vulnerability · Source |
| CVE-2017-15412 | suse_vex | SUSE CVE CVE-2017-15412 | known affected: 394 known not affected: 6 recommended: 161 | 2026-08-05T01:28:17+00:00 | Vulnerability · Source |
| CVE-2017-16526 | suse_vex | SUSE CVE CVE-2017-16526 | known not affected: 570 | 2026-08-05T01:28:15+00:00 | Vulnerability · Source |
| CVE-2017-18237 | suse_vex | SUSE CVE CVE-2017-18237 | known not affected: 178 | 2026-08-05T01:28:10+00:00 | Vulnerability · Source |
| CVE-2017-1000158 | suse_vex | SUSE CVE CVE-2017-1000158 | known affected: 480 known not affected: 16 recommended: 777 | 2026-08-05T01:28:08+00:00 | Vulnerability · Source |
| CVE-2017-1000409 | suse_vex | SUSE CVE CVE-2017-1000409 | known affected: 61 known not affected: 266 recommended: 1108 | 2026-08-05T01:28:06+00:00 | Vulnerability · Source |
| CVE-2018-1053 | suse_vex | SUSE CVE CVE-2018-1053 | known not affected: 46 recommended: 433 | 2026-08-05T01:28:04+00:00 | Vulnerability · Source |
| CVE-2018-1066 | suse_vex | SUSE CVE CVE-2018-1066 | known not affected: 77 recommended: 80 | 2026-08-05T01:28:02+00:00 | Vulnerability · Source |
| CVE-2018-5147 | suse_vex | SUSE CVE CVE-2018-5147 | known affected: 27 known not affected: 229 recommended: 310 | 2026-08-05T01:27:52+00:00 | Vulnerability · Source |
| CVE-2018-5745 | suse_vex | SUSE CVE CVE-2018-5745 | known affected: 428 known not affected: 1 recommended: 1076 | 2026-08-05T01:27:48+00:00 | Vulnerability · Source |
| CVE-2018-6081 | suse_vex | SUSE CVE CVE-2018-6081 | recommended: 10 | 2026-08-05T01:27:47+00:00 | Vulnerability · Source |
| CVE-2018-7419 | suse_vex | SUSE CVE CVE-2018-7419 | known affected: 1 known not affected: 115 recommended: 589 | 2026-08-05T01:27:44+00:00 | Vulnerability · Source |
| CVE-2018-10675 | suse_vex | SUSE CVE CVE-2018-10675 | known affected: 2 known not affected: 158 recommended: 203 | 2026-08-05T01:27:39+00:00 | Vulnerability · Source |
| CVE-2018-12120 | suse_vex | SUSE CVE CVE-2018-12120 | known affected: 40 known not affected: 76 recommended: 84 | 2026-08-05T01:27:36+00:00 | Vulnerability · Source |
| CVE-2018-13153 | suse_vex | SUSE CVE CVE-2018-13153 | recommended: 34 | 2026-08-05T01:27:32+00:00 | Vulnerability · Source |