VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2013-4314 | suse_vex | SUSE CVE CVE-2013-4314 | recommended: 152 | 2026-08-10T16:48:15+00:00 | Vulnerability · Source |
| CVE-2013-4342 | suse_vex | SUSE CVE CVE-2013-4342 | known not affected: 22 recommended: 32 | 2026-08-10T16:48:14+00:00 | Vulnerability · Source |
| CVE-2013-4473 | suse_vex | SUSE CVE CVE-2013-4473 | recommended: 334 | 2026-08-10T16:48:12+00:00 | Vulnerability · Source |
| CVE-2013-5823 | suse_vex | SUSE CVE CVE-2013-5823 | known affected: 2 recommended: 208 | 2026-08-10T16:48:07+00:00 | Vulnerability · Source |
| CVE-2014-2423 | suse_vex | SUSE CVE CVE-2014-2423 | known affected: 2 known not affected: 94 recommended: 199 | 2026-08-10T16:48:00+00:00 | Vulnerability · Source |
| CVE-2015-1119 | suse_vex | SUSE CVE CVE-2015-1119 | known not affected: 18 | 2026-08-10T16:47:48+00:00 | Vulnerability · Source |
| CVE-2015-1126 | suse_vex | SUSE CVE CVE-2015-1126 | known not affected: 18 | 2026-08-10T16:47:46+00:00 | Vulnerability · Source |
| CVE-2015-1858 | suse_vex | SUSE CVE CVE-2015-1858 | known not affected: 1161 recommended: 1676 | 2026-08-10T16:47:44+00:00 | Vulnerability · Source |
| CVE-2015-4680 | suse_vex | SUSE CVE CVE-2015-4680 | known affected: 24 known not affected: 333 recommended: 665 | 2026-08-10T16:47:39+00:00 | Vulnerability · Source |
| CVE-2015-7194 | suse_vex | SUSE CVE CVE-2015-7194 | known affected: 5 known not affected: 183 recommended: 620 | 2026-08-10T16:47:35+00:00 | Vulnerability · Source |
| CVE-2015-7566 | suse_vex | SUSE CVE CVE-2015-7566 | known not affected: 44 recommended: 181 | 2026-08-10T16:47:32+00:00 | Vulnerability · Source |
| CVE-2015-8767 | suse_vex | SUSE CVE CVE-2015-8767 | known not affected: 119 recommended: 343 | 2026-08-10T16:47:28+00:00 | Vulnerability · Source |
| CVE-2016-2782 | suse_vex | SUSE CVE CVE-2016-2782 | known affected: 2 known not affected: 359 recommended: 321 | 2026-08-10T16:47:23+00:00 | Vulnerability · Source |
| CVE-2016-2848 | suse_vex | SUSE CVE CVE-2016-2848 | known not affected: 47 | 2026-08-10T16:47:21+00:00 | Vulnerability · Source |
| CVE-2016-4606 | suse_vex | SUSE CVE CVE-2016-4606 | known not affected: 89 | 2026-08-10T16:47:14+00:00 | Vulnerability · Source |
| CVE-2016-4998 | suse_vex | SUSE CVE CVE-2016-4998 | known not affected: 271 recommended: 189 | 2026-08-10T16:47:13+00:00 | Vulnerability · Source |
| CVE-2016-6516 | suse_vex | SUSE CVE CVE-2016-6516 | known not affected: 102 recommended: 114 | 2026-08-10T16:47:08+00:00 | Vulnerability · Source |
| CVE-2016-7641 | suse_vex | SUSE CVE CVE-2016-7641 | known not affected: 87 recommended: 939 | 2026-08-10T16:47:05+00:00 | Vulnerability · Source |
| CVE-2017-5409 | suse_vex | SUSE CVE CVE-2017-5409 | known affected: 1 recommended: 81 | 2026-08-10T16:46:56+00:00 | Vulnerability · Source |
| CVE-2017-7675 | suse_vex | SUSE CVE CVE-2017-7675 | known not affected: 91 | 2026-08-10T16:46:51+00:00 | Vulnerability · Source |
| CVE-2017-7890 | suse_vex | SUSE CVE CVE-2017-7890 | known affected: 944 known not affected: 533 recommended: 1525 | 2026-08-10T16:46:48+00:00 | Vulnerability · Source |
| CVE-2017-8351 | suse_vex | SUSE CVE CVE-2017-8351 | recommended: 184 | 2026-08-10T16:46:47+00:00 | Vulnerability · Source |
| CVE-2017-13078 | suse_vex | SUSE CVE CVE-2017-13078 | known affected: 6 known not affected: 354 recommended: 123 | 2026-08-10T16:46:41+00:00 | Vulnerability · Source |
| CVE-2017-13734 | suse_vex | SUSE CVE CVE-2017-13734 | known affected: 156 known not affected: 79 recommended: 171 | 2026-08-10T16:46:39+00:00 | Vulnerability · Source |
| CVE-2017-15593 | suse_vex | SUSE CVE CVE-2017-15593 | known affected: 32 known not affected: 85 recommended: 141 | 2026-08-10T16:46:36+00:00 | Vulnerability · Source |
| CVE-2017-16669 | suse_vex | SUSE CVE CVE-2017-16669 | known affected: 97 recommended: 150 | 2026-08-10T16:46:34+00:00 | Vulnerability · Source |
| CVE-2017-17805 | suse_vex | SUSE CVE CVE-2017-17805 | known affected: 38 known not affected: 196 recommended: 631 | 2026-08-10T16:46:30+00:00 | Vulnerability · Source |
| CVE-2017-1000112 | suse_vex | SUSE CVE CVE-2017-1000112 | known affected: 146 known not affected: 8 recommended: 417 | 2026-08-10T16:46:28+00:00 | Vulnerability · Source |
| CVE-2018-7566 | suse_vex | SUSE CVE CVE-2018-7566 | known affected: 128 known not affected: 227 recommended: 611 | 2026-08-10T16:46:19+00:00 | Vulnerability · Source |
| CVE-2018-9303 | suse_vex | SUSE CVE CVE-2018-9303 | recommended: 8 | 2026-08-10T16:46:16+00:00 | Vulnerability · Source |
| CVE-2020-9484 | suse_vex | SUSE CVE CVE-2020-9484 | known affected: 511 known not affected: 145 recommended: 428 | 2026-08-10T16:45:44+00:00 | Vulnerability · Source |
| CVE-2020-12411 | suse_vex | SUSE CVE CVE-2020-12411 | known affected: 48 recommended: 9 | 2026-08-10T16:45:41+00:00 | Vulnerability · Source |
| CVE-2020-13631 | suse_vex | SUSE CVE CVE-2020-13631 | known affected: 364 known not affected: 279 recommended: 473 | 2026-08-10T16:45:38+00:00 | Vulnerability · Source |
| CVE-2020-29660 | suse_vex | SUSE CVE CVE-2020-29660 | known affected: 464 known not affected: 10 recommended: 1896 | 2026-08-10T16:45:28+00:00 | Vulnerability · Source |
| CVE-2021-4202 | suse_vex | SUSE CVE CVE-2021-4202 | known affected: 390 known not affected: 117 recommended: 1621 | 2026-08-10T16:45:22+00:00 | Vulnerability · Source |
| CVE-2021-23984 | suse_vex | SUSE CVE CVE-2021-23984 | recommended: 639 | 2026-08-10T16:45:17+00:00 | Vulnerability · Source |
| CVE-2021-28147 | suse_vex | SUSE CVE CVE-2021-28147 | known not affected: 12 recommended: 241 | 2026-08-10T16:45:15+00:00 | Vulnerability · Source |
| CVE-2021-47151 | suse_vex | SUSE CVE CVE-2021-47151 | known not affected: 292 | 2026-08-10T16:45:04+00:00 | Vulnerability · Source |
| CVE-2021-47160 | suse_vex | SUSE CVE CVE-2021-47160 | known affected: 411 known not affected: 306 recommended: 91 | 2026-08-10T16:45:03+00:00 | Vulnerability · Source |
| CVE-2021-47571 | suse_vex | SUSE CVE CVE-2021-47571 | known affected: 363 known not affected: 76 recommended: 664 | 2026-08-10T16:44:53+00:00 | Vulnerability · Source |
| CVE-2022-48940 | suse_vex | SUSE CVE CVE-2022-48940 | known affected: 340 known not affected: 248 recommended: 288 | 2026-08-10T16:44:20+00:00 | Vulnerability · Source |
| CVE-2023-53717 | suse_vex | SUSE CVE CVE-2023-53717 | known affected: 415 known not affected: 170 recommended: 354 | 2026-08-10T16:43:22+00:00 | Vulnerability · Source |
| CVE-2025-27423 | suse_vex | SUSE CVE CVE-2025-27423 | known affected: 15 known not affected: 231 | 2026-08-10T16:41:56+00:00 | Vulnerability · Source |
| CVE-2025-68119 | suse_vex | SUSE CVE CVE-2025-68119 | known affected: 24 known not affected: 108 recommended: 274 | 2026-08-10T16:40:13+00:00 | Vulnerability · Source |
| CVE-2025-68973 | suse_vex | SUSE CVE CVE-2025-68973 | known affected: 403 recommended: 144 | 2026-08-10T16:40:04+00:00 | Vulnerability · Source |
| CVE-2026-3945 | suse_vex | SUSE CVE CVE-2026-3945 | recommended: 3 | 2026-08-10T16:39:49+00:00 | Vulnerability · Source |
| CVE-2026-12372 | suse_vex | SUSE CVE CVE-2026-12372 | No product status | 2026-08-10T16:39:00+00:00 | Vulnerability · Source |
| CVE-2026-12706 | suse_vex | SUSE CVE CVE-2026-12706 | known affected: 19 known not affected: 307 recommended: 129 | 2026-08-10T16:38:56+00:00 | Vulnerability · Source |
| CVE-2026-14899 | suse_vex | SUSE CVE CVE-2026-14899 | first fixed: 15 known affected: 24 recommended: 22 | 2026-08-10T16:38:43+00:00 | Vulnerability · Source |
| CVE-2026-15718 | suse_vex | SUSE CVE CVE-2026-15718 | first fixed: 23 known not affected: 106 recommended: 116 | 2026-08-10T16:38:37+00:00 | Vulnerability · Source |