VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291877 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2014-3647 | suse_vex | SUSE CVE CVE-2014-3647 | known not affected: 136 recommended: 319 | 2026-08-12T00:29:07+00:00 | Vulnerability · Source |
| CVE-2014-4233 | suse_vex | SUSE CVE CVE-2014-4233 | known not affected: 44 recommended: 70 | 2026-08-12T00:29:05+00:00 | Vulnerability · Source |
| CVE-2014-4338 | suse_vex | SUSE CVE CVE-2014-4338 | known not affected: 8 recommended: 113 | 2026-08-12T00:29:04+00:00 | Vulnerability · Source |
| CVE-2014-5472 | suse_vex | SUSE CVE CVE-2014-5472 | known not affected: 500 recommended: 290 | 2026-08-12T00:29:01+00:00 | Vulnerability · Source |
| CVE-2014-6504 | suse_vex | SUSE CVE CVE-2014-6504 | known affected: 61 known not affected: 190 recommended: 95 | 2026-08-12T00:28:58+00:00 | Vulnerability · Source |
| CVE-2014-8101 | suse_vex | SUSE CVE CVE-2014-8101 | known affected: 1 recommended: 97 | 2026-08-12T00:28:56+00:00 | Vulnerability · Source |
| CVE-2014-9050 | suse_vex | SUSE CVE CVE-2014-9050 | known not affected: 1 recommended: 84 | 2026-08-12T00:28:54+00:00 | Vulnerability · Source |
| CVE-2014-9114 | suse_vex | SUSE CVE CVE-2014-9114 | known affected: 320 known not affected: 111 recommended: 1720 | 2026-08-12T00:28:52+00:00 | Vulnerability · Source |
| CVE-2014-9840 | suse_vex | SUSE CVE CVE-2014-9840 | known affected: 97 recommended: 216 | 2026-08-12T00:28:50+00:00 | Vulnerability · Source |
| CVE-2015-0811 | suse_vex | SUSE CVE CVE-2015-0811 | known affected: 1 known not affected: 28 recommended: 250 | 2026-08-12T00:28:47+00:00 | Vulnerability · Source |
| CVE-2015-0830 | suse_vex | SUSE CVE CVE-2015-0830 | known not affected: 39 recommended: 255 | 2026-08-12T00:28:46+00:00 | Vulnerability · Source |
| CVE-2015-5214 | suse_vex | SUSE CVE CVE-2015-5214 | recommended: 5001 | 2026-08-12T00:28:40+00:00 | Vulnerability · Source |
| CVE-2015-5312 | suse_vex | SUSE CVE CVE-2015-5312 | known affected: 400 known not affected: 102 recommended: 539 | 2026-08-12T00:28:38+00:00 | Vulnerability · Source |
| CVE-2015-7217 | suse_vex | SUSE CVE CVE-2015-7217 | known affected: 2 recommended: 251 | 2026-08-12T00:28:35+00:00 | Vulnerability · Source |
| CVE-2015-7513 | suse_vex | SUSE CVE CVE-2015-7513 | known not affected: 332 recommended: 193 | 2026-08-12T00:28:32+00:00 | Vulnerability · Source |
| CVE-2015-8553 | suse_vex | SUSE CVE CVE-2015-8553 | known not affected: 161 | 2026-08-12T00:28:29+00:00 | Vulnerability · Source |
| CVE-2016-0605 | suse_vex | SUSE CVE CVE-2016-0605 | known affected: 2 known not affected: 176 recommended: 10 | 2026-08-12T00:28:24+00:00 | Vulnerability · Source |
| CVE-2016-4354 | suse_vex | SUSE CVE CVE-2016-4354 | known not affected: 37 | 2026-08-12T00:28:15+00:00 | Vulnerability · Source |
| CVE-2016-9905 | suse_vex | SUSE CVE CVE-2016-9905 | known affected: 1 recommended: 169 | 2026-08-12T00:28:03+00:00 | Vulnerability · Source |
| CVE-2016-10144 | suse_vex | SUSE CVE CVE-2016-10144 | known affected: 1 known not affected: 14 recommended: 204 | 2026-08-12T00:28:01+00:00 | Vulnerability · Source |
| CVE-2017-3241 | suse_vex | SUSE CVE CVE-2017-3241 | known affected: 124 known not affected: 166 recommended: 584 | 2026-08-12T00:27:56+00:00 | Vulnerability · Source |
| CVE-2017-7869 | suse_vex | SUSE CVE CVE-2017-7869 | known affected: 328 known not affected: 4 recommended: 587 | 2026-08-12T00:27:45+00:00 | Vulnerability · Source |
| CVE-2017-10672 | suse_vex | SUSE CVE CVE-2017-10672 | known affected: 16 recommended: 21 | 2026-08-12T00:27:41+00:00 | Vulnerability · Source |
| CVE-2017-12957 | suse_vex | SUSE CVE CVE-2017-12957 | known affected: 29 known not affected: 73 recommended: 163 | 2026-08-12T00:27:35+00:00 | Vulnerability · Source |
| CVE-2017-13728 | suse_vex | SUSE CVE CVE-2017-13728 | known affected: 157 recommended: 201 | 2026-08-12T00:27:33+00:00 | Vulnerability · Source |
| CVE-2018-5748 | suse_vex | SUSE CVE CVE-2018-5748 | known affected: 436 known not affected: 1220 recommended: 2119 | 2026-08-12T00:27:22+00:00 | Vulnerability · Source |
| CVE-2018-14882 | suse_vex | SUSE CVE CVE-2018-14882 | known affected: 333 recommended: 145 | 2026-08-12T00:27:15+00:00 | Vulnerability · Source |
| CVE-2019-6201 | suse_vex | SUSE CVE CVE-2019-6201 | known affected: 154 known not affected: 82 recommended: 983 | 2026-08-12T00:27:01+00:00 | Vulnerability · Source |
| CVE-2019-9501 | suse_vex | SUSE CVE CVE-2019-9501 | known not affected: 75 | 2026-08-12T00:26:57+00:00 | Vulnerability · Source |
| CVE-2019-14294 | suse_vex | SUSE CVE CVE-2019-14294 | known not affected: 376 | 2026-08-12T00:26:47+00:00 | Vulnerability · Source |
| CVE-2020-1398 | suse_vex | SUSE CVE CVE-2020-1398 | known affected: 90 known not affected: 56 | 2026-08-12T00:26:37+00:00 | Vulnerability · Source |
| CVE-2020-8551 | suse_vex | SUSE CVE CVE-2020-8551 | known not affected: 49 recommended: 3 | 2026-08-12T00:26:30+00:00 | Vulnerability · Source |
| CVE-2020-24588 | suse_vex | SUSE CVE CVE-2020-24588 | known affected: 213 known not affected: 10 recommended: 1870 | 2026-08-12T00:26:16+00:00 | Vulnerability · Source |
| CVE-2020-26137 | suse_vex | SUSE CVE CVE-2020-26137 | known affected: 326 known not affected: 40 recommended: 1335 | 2026-08-12T00:26:12+00:00 | Vulnerability · Source |
| CVE-2021-4037 | suse_vex | SUSE CVE CVE-2021-4037 | known affected: 247 known not affected: 223 recommended: 1491 | 2026-08-12T00:26:01+00:00 | Vulnerability · Source |
| CVE-2021-4189 | suse_vex | SUSE CVE CVE-2021-4189 | known affected: 396 known not affected: 311 recommended: 619 | 2026-08-12T00:25:59+00:00 | Vulnerability · Source |
| CVE-2021-25749 | suse_vex | SUSE CVE CVE-2021-25749 | known not affected: 42 recommended: 43 | 2026-08-12T00:25:54+00:00 | Vulnerability · Source |
| CVE-2021-47210 | suse_vex | SUSE CVE CVE-2021-47210 | known affected: 336 known not affected: 177 recommended: 462 | 2026-08-12T00:25:38+00:00 | Vulnerability · Source |
| CVE-2021-47223 | suse_vex | SUSE CVE CVE-2021-47223 | known affected: 522 known not affected: 210 recommended: 26 | 2026-08-12T00:25:36+00:00 | Vulnerability · Source |
| CVE-2021-47335 | suse_vex | SUSE CVE CVE-2021-47335 | known not affected: 330 | 2026-08-12T00:25:33+00:00 | Vulnerability · Source |
| CVE-2021-47431 | suse_vex | SUSE CVE CVE-2021-47431 | known affected: 335 known not affected: 70 recommended: 657 | 2026-08-12T00:25:26+00:00 | Vulnerability · Source |
| CVE-2022-2078 | suse_vex | SUSE CVE CVE-2022-2078 | known not affected: 268 recommended: 42 | 2026-08-12T00:25:01+00:00 | Vulnerability · Source |
| CVE-2022-2959 | suse_vex | SUSE CVE CVE-2022-2959 | known affected: 265 known not affected: 276 recommended: 667 | 2026-08-12T00:24:46+00:00 | Vulnerability · Source |
| CVE-2022-23552 | suse_vex | SUSE CVE CVE-2022-23552 | known affected: 1 known not affected: 5 recommended: 136 | 2026-08-12T00:23:04+00:00 | Vulnerability · Source |
| CVE-2022-28748 | suse_vex | SUSE CVE CVE-2022-28748 | known affected: 149 known not affected: 21 recommended: 1736 | 2026-08-12T00:22:55+00:00 | Vulnerability · Source |
| CVE-2022-30594 | suse_vex | SUSE CVE CVE-2022-30594 | known affected: 216 known not affected: 102 recommended: 1869 | 2026-08-12T00:22:47+00:00 | Vulnerability · Source |
| CVE-2022-48628 | suse_vex | SUSE CVE CVE-2022-48628 | known affected: 305 known not affected: 251 recommended: 532 | 2026-08-12T00:21:37+00:00 | Vulnerability · Source |
| CVE-2022-49031 | suse_vex | SUSE CVE CVE-2022-49031 | known affected: 396 known not affected: 149 recommended: 478 | 2026-08-12T00:21:29+00:00 | Vulnerability · Source |
| CVE-2022-49492 | suse_vex | SUSE CVE CVE-2022-49492 | known affected: 413 known not affected: 194 recommended: 363 | 2026-08-12T00:21:20+00:00 | Vulnerability · Source |
| CVE-2022-50066 | suse_vex | SUSE CVE CVE-2022-50066 | known affected: 443 known not affected: 200 recommended: 291 | 2026-08-12T00:21:04+00:00 | Vulnerability · Source |