VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293999 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2015-4164 | suse_vex | SUSE CVE CVE-2015-4164 | known not affected: 32 recommended: 109 | 2026-08-01T00:24:03+00:00 | Vulnerability · Source |
| CVE-2015-6855 | suse_vex | SUSE CVE CVE-2015-6855 | known affected: 321 known not affected: 148 recommended: 2355 | 2026-08-01T00:23:49+00:00 | Vulnerability · Source |
| CVE-2015-8713 | suse_vex | SUSE CVE CVE-2015-8713 | known affected: 86 recommended: 107 | 2026-08-01T00:23:29+00:00 | Vulnerability · Source |
| CVE-2015-8901 | suse_vex | SUSE CVE CVE-2015-8901 | known affected: 97 recommended: 216 | 2026-08-01T00:23:25+00:00 | Vulnerability · Source |
| CVE-2015-8949 | suse_vex | SUSE CVE CVE-2015-8949 | known not affected: 4 | 2026-08-01T00:23:23+00:00 | Vulnerability · Source |
| CVE-2015-10082 | suse_vex | SUSE CVE CVE-2015-10082 | known affected: 21 known not affected: 137 recommended: 15 | 2026-08-01T00:23:19+00:00 | Vulnerability · Source |
| CVE-2015-20109 | suse_vex | SUSE CVE CVE-2015-20109 | known not affected: 608 | 2026-08-01T00:23:17+00:00 | Vulnerability · Source |
| CVE-2016-2074 | suse_vex | SUSE CVE CVE-2016-2074 | known not affected: 18 | 2026-08-01T00:23:09+00:00 | Vulnerability · Source |
| CVE-2016-3634 | suse_vex | SUSE CVE CVE-2016-3634 | known not affected: 53 | 2026-08-01T00:22:56+00:00 | Vulnerability · Source |
| CVE-2016-4802 | suse_vex | SUSE CVE CVE-2016-4802 | known not affected: 49 | 2026-08-01T00:22:50+00:00 | Vulnerability · Source |
| CVE-2016-4859 | suse_vex | SUSE CVE CVE-2016-4859 | known not affected: 443 | 2026-08-01T00:22:49+00:00 | Vulnerability · Source |
| CVE-2016-6153 | suse_vex | SUSE CVE CVE-2016-6153 | known affected: 394 known not affected: 139 recommended: 162 | 2026-08-01T00:22:43+00:00 | Vulnerability · Source |
| CVE-2016-7911 | suse_vex | SUSE CVE CVE-2016-7911 | known affected: 4 recommended: 314 | 2026-08-01T00:22:35+00:00 | Vulnerability · Source |
| CVE-2016-7958 | suse_vex | SUSE CVE CVE-2016-7958 | known not affected: 92 | 2026-08-01T00:22:33+00:00 | Vulnerability · Source |
| CVE-2016-9428 | suse_vex | SUSE CVE CVE-2016-9428 | known not affected: 15 | 2026-08-01T00:22:18+00:00 | Vulnerability · Source |
| CVE-2016-9437 | suse_vex | SUSE CVE CVE-2016-9437 | known affected: 1 recommended: 87 | 2026-08-01T00:22:17+00:00 | Vulnerability · Source |
| CVE-2016-9535 | suse_vex | SUSE CVE CVE-2016-9535 | known not affected: 28 recommended: 26 | 2026-08-01T00:22:14+00:00 | Vulnerability · Source |
| CVE-2016-10047 | suse_vex | SUSE CVE CVE-2016-10047 | known not affected: 99 | 2026-08-01T00:22:08+00:00 | Vulnerability · Source |
| CVE-2017-3650 | suse_vex | SUSE CVE CVE-2017-3650 | known affected: 1 known not affected: 64 | 2026-08-01T00:21:54+00:00 | Vulnerability · Source |
| CVE-2017-6000 | suse_vex | SUSE CVE CVE-2017-6000 | known not affected: 73 | 2026-08-01T00:21:36+00:00 | Vulnerability · Source |
| CVE-2017-7294 | suse_vex | SUSE CVE CVE-2017-7294 | known not affected: 339 recommended: 455 | 2026-08-01T00:21:31+00:00 | Vulnerability · Source |
| CVE-2017-7808 | suse_vex | SUSE CVE CVE-2017-7808 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T00:21:26+00:00 | Vulnerability · Source |
| CVE-2017-8061 | suse_vex | SUSE CVE CVE-2017-8061 | known not affected: 34 | 2026-08-01T00:21:24+00:00 | Vulnerability · Source |
| CVE-2017-8072 | suse_vex | SUSE CVE CVE-2017-8072 | known not affected: 34 | 2026-08-01T00:21:22+00:00 | Vulnerability · Source |
| CVE-2017-8904 | suse_vex | SUSE CVE CVE-2017-8904 | known affected: 13 | 2026-08-01T00:21:19+00:00 | Vulnerability · Source |
| CVE-2017-10081 | suse_vex | SUSE CVE CVE-2017-10081 | known affected: 409 known not affected: 109 recommended: 690 | 2026-08-01T00:21:08+00:00 | Vulnerability · Source |
| CVE-2017-10243 | suse_vex | SUSE CVE CVE-2017-10243 | known affected: 15 known not affected: 109 recommended: 674 | 2026-08-01T00:21:03+00:00 | Vulnerability · Source |
| CVE-2017-11434 | suse_vex | SUSE CVE CVE-2017-11434 | known affected: 471 known not affected: 65 recommended: 2001 | 2026-08-01T00:21:01+00:00 | Vulnerability · Source |
| CVE-2017-11526 | suse_vex | SUSE CVE CVE-2017-11526 | known affected: 94 known not affected: 21 recommended: 186 | 2026-08-01T00:20:59+00:00 | Vulnerability · Source |
| CVE-2017-11697 | suse_vex | SUSE CVE CVE-2017-11697 | known not affected: 355 | 2026-08-01T00:20:58+00:00 | Vulnerability · Source |
| CVE-2017-12184 | suse_vex | SUSE CVE CVE-2017-12184 | known affected: 2 known not affected: 51 recommended: 42 | 2026-08-01T00:20:55+00:00 | Vulnerability · Source |
| CVE-2017-13004 | suse_vex | SUSE CVE CVE-2017-13004 | known affected: 336 known not affected: 24 recommended: 151 | 2026-08-01T00:20:52+00:00 | Vulnerability · Source |
| CVE-2017-13132 | suse_vex | SUSE CVE CVE-2017-13132 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:51+00:00 | Vulnerability · Source |
| CVE-2017-13144 | suse_vex | SUSE CVE CVE-2017-13144 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:49+00:00 | Vulnerability · Source |
| CVE-2017-13648 | suse_vex | SUSE CVE CVE-2017-13648 | known not affected: 14 recommended: 172 | 2026-08-01T00:20:47+00:00 | Vulnerability · Source |
| CVE-2017-14400 | suse_vex | SUSE CVE CVE-2017-14400 | known affected: 10 known not affected: 144 | 2026-08-01T00:20:43+00:00 | Vulnerability · Source |
| CVE-2017-16352 | suse_vex | SUSE CVE CVE-2017-16352 | known affected: 94 recommended: 186 | 2026-08-01T00:20:37+00:00 | Vulnerability · Source |
| CVE-2017-16931 | suse_vex | SUSE CVE CVE-2017-16931 | known affected: 61 | 2026-08-01T00:20:34+00:00 | Vulnerability · Source |
| CVE-2017-17479 | suse_vex | SUSE CVE CVE-2017-17479 | recommended: 10 | 2026-08-01T00:20:32+00:00 | Vulnerability · Source |
| CVE-2017-17879 | suse_vex | SUSE CVE CVE-2017-17879 | known affected: 94 known not affected: 21 recommended: 186 | 2026-08-01T00:20:26+00:00 | Vulnerability · Source |
| CVE-2017-17887 | suse_vex | SUSE CVE CVE-2017-17887 | known affected: 97 known not affected: 36 recommended: 100 | 2026-08-01T00:20:25+00:00 | Vulnerability · Source |
| CVE-2017-18022 | suse_vex | SUSE CVE CVE-2017-18022 | recommended: 186 | 2026-08-01T00:20:23+00:00 | Vulnerability · Source |
| CVE-2017-18238 | suse_vex | SUSE CVE CVE-2017-18238 | known affected: 4 known not affected: 14 recommended: 26 | 2026-08-01T00:20:20+00:00 | Vulnerability · Source |
| CVE-2018-5114 | suse_vex | SUSE CVE CVE-2018-5114 | known affected: 1 known not affected: 42 recommended: 12 | 2026-08-01T00:20:07+00:00 | Vulnerability · Source |
| CVE-2018-5182 | suse_vex | SUSE CVE CVE-2018-5182 | known affected: 26 recommended: 83 | 2026-08-01T00:20:05+00:00 | Vulnerability · Source |
| CVE-2018-5407 | suse_vex | SUSE CVE CVE-2018-5407 | known affected: 430 known not affected: 304 recommended: 598 | 2026-08-01T00:20:04+00:00 | Vulnerability · Source |
| CVE-2018-8011 | suse_vex | SUSE CVE CVE-2018-8011 | known affected: 31 known not affected: 233 recommended: 82 | 2026-08-01T00:19:57+00:00 | Vulnerability · Source |
| CVE-2018-9252 | suse_vex | SUSE CVE CVE-2018-9252 | known affected: 46 recommended: 154 | 2026-08-01T00:19:53+00:00 | Vulnerability · Source |
| CVE-2018-10124 | suse_vex | SUSE CVE CVE-2018-10124 | known affected: 28 known not affected: 221 recommended: 662 | 2026-08-01T00:19:48+00:00 | Vulnerability · Source |
| CVE-2018-10932 | suse_vex | SUSE CVE CVE-2018-10932 | known not affected: 154 recommended: 15 | 2026-08-01T00:19:44+00:00 | Vulnerability · Source |