VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
297729 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2016-10277 | suse_vex | SUSE CVE CVE-2016-10277 | recommended: 91 | 2026-06-07T06:17:19+00:00 | Vulnerability · Source |
| CVE-2017-7300 | suse_vex | SUSE CVE CVE-2017-7300 | known affected: 418 known not affected: 16 recommended: 330 | 2026-06-07T06:11:39+00:00 | Vulnerability · Source |
| CVE-2017-7790 | suse_vex | SUSE CVE CVE-2017-7790 | known not affected: 34 recommended: 12 | 2026-06-07T06:09:57+00:00 | Vulnerability · Source |
| CVE-2017-7811 | suse_vex | SUSE CVE CVE-2017-7811 | known not affected: 34 recommended: 12 | 2026-06-07T06:09:32+00:00 | Vulnerability · Source |
| CVE-2017-7813 | suse_vex | SUSE CVE CVE-2017-7813 | known not affected: 34 recommended: 12 | 2026-06-07T06:09:30+00:00 | Vulnerability · Source |
| CVE-2017-7838 | suse_vex | SUSE CVE CVE-2017-7838 | known affected: 1 known not affected: 34 recommended: 12 | 2026-06-07T06:09:01+00:00 | Vulnerability · Source |
| CVE-2017-11354 | suse_vex | SUSE CVE CVE-2017-11354 | No product status | 2026-06-07T06:06:08+00:00 | Vulnerability · Source |
| CVE-2017-12122 | suse_vex | SUSE CVE CVE-2017-12122 | recommended: 13 | 2026-06-07T06:05:43+00:00 | Vulnerability · Source |
| CVE-2017-14440 | suse_vex | SUSE CVE CVE-2017-14440 | recommended: 13 | 2026-06-07T06:02:15+00:00 | Vulnerability · Source |
| CVE-2017-14441 | suse_vex | SUSE CVE CVE-2017-14441 | known not affected: 8 recommended: 5 | 2026-06-07T06:02:14+00:00 | Vulnerability · Source |
| CVE-2017-14450 | suse_vex | SUSE CVE CVE-2017-14450 | recommended: 13 | 2026-06-07T06:02:12+00:00 | Vulnerability · Source |
| CVE-2017-1000246 | suse_vex | SUSE CVE CVE-2017-1000246 | recommended: 270 | 2026-06-07T05:56:17+00:00 | Vulnerability · Source |
| CVE-2018-5105 | suse_vex | SUSE CVE CVE-2018-5105 | known affected: 1 known not affected: 34 recommended: 12 | 2026-06-07T05:53:01+00:00 | Vulnerability · Source |
| CVE-2018-5122 | suse_vex | SUSE CVE CVE-2018-5122 | known affected: 1 known not affected: 34 recommended: 12 | 2026-06-07T05:52:48+00:00 | Vulnerability · Source |
| CVE-2018-5132 | suse_vex | SUSE CVE CVE-2018-5132 | known affected: 1 known not affected: 40 recommended: 12 | 2026-06-07T05:52:36+00:00 | Vulnerability · Source |
| CVE-2018-5133 | suse_vex | SUSE CVE CVE-2018-5133 | known affected: 1 known not affected: 40 recommended: 12 | 2026-06-07T05:52:35+00:00 | Vulnerability · Source |
| CVE-2018-5143 | suse_vex | SUSE CVE CVE-2018-5143 | known affected: 1 known not affected: 40 recommended: 12 | 2026-06-07T05:52:29+00:00 | Vulnerability · Source |
| CVE-2018-6033 | suse_vex | SUSE CVE CVE-2018-6033 | recommended: 34 | 2026-06-07T05:51:06+00:00 | Vulnerability · Source |
| CVE-2018-6156 | suse_vex | SUSE CVE CVE-2018-6156 | recommended: 20 | 2026-06-07T05:50:36+00:00 | Vulnerability · Source |
| CVE-2018-7492 | suse_vex | SUSE CVE CVE-2018-7492 | known not affected: 168 recommended: 625 | 2026-06-07T05:49:16+00:00 | Vulnerability · Source |
| CVE-2018-7714 | suse_vex | SUSE CVE CVE-2018-7714 | No product status | 2026-06-07T05:48:56+00:00 | Vulnerability · Source |
| CVE-2018-7738 | suse_vex | SUSE CVE CVE-2018-7738 | known affected: 422 known not affected: 201 recommended: 880 | 2026-06-07T05:48:50+00:00 | Vulnerability · Source |
| CVE-2018-12714 | suse_vex | SUSE CVE CVE-2018-12714 | recommended: 6 | 2026-06-07T05:44:46+00:00 | Vulnerability · Source |
| CVE-2018-14568 | suse_vex | SUSE CVE CVE-2018-14568 | recommended: 3 | 2026-06-07T05:43:38+00:00 | Vulnerability · Source |
| CVE-2018-16476 | suse_vex | SUSE CVE CVE-2018-16476 | known affected: 382 known not affected: 2 recommended: 25 | 2026-06-07T05:41:57+00:00 | Vulnerability · Source |
| CVE-2018-16871 | suse_vex | SUSE CVE CVE-2018-16871 | known affected: 86 known not affected: 223 recommended: 671 | 2026-06-07T05:41:27+00:00 | Vulnerability · Source |
| CVE-2018-18246 | suse_vex | SUSE CVE CVE-2018-18246 | recommended: 60 | 2026-06-07T05:40:29+00:00 | Vulnerability · Source |
| CVE-2018-20725 | suse_vex | SUSE CVE CVE-2018-20725 | recommended: 7 | 2026-06-07T05:38:05+00:00 | Vulnerability · Source |
| CVE-2018-20726 | suse_vex | SUSE CVE CVE-2018-20726 | recommended: 7 | 2026-06-07T05:38:04+00:00 | Vulnerability · Source |
| CVE-2019-3826 | suse_vex | SUSE CVE CVE-2019-3826 | known not affected: 6 | 2026-06-07T05:35:13+00:00 | Vulnerability · Source |
| CVE-2019-5051 | suse_vex | SUSE CVE CVE-2019-5051 | recommended: 21 | 2026-06-07T05:34:47+00:00 | Vulnerability · Source |
| CVE-2019-5058 | suse_vex | SUSE CVE CVE-2019-5058 | recommended: 41 | 2026-06-07T05:34:46+00:00 | Vulnerability · Source |
| CVE-2019-11699 | suse_vex | SUSE CVE CVE-2019-11699 | recommended: 9 | 2026-06-07T05:30:10+00:00 | Vulnerability · Source |
| CVE-2019-12218 | suse_vex | SUSE CVE CVE-2019-12218 | recommended: 21 | 2026-06-07T05:29:22+00:00 | Vulnerability · Source |
| CVE-2019-12221 | suse_vex | SUSE CVE CVE-2019-12221 | recommended: 21 | 2026-06-07T05:29:21+00:00 | Vulnerability · Source |
| CVE-2019-12222 | suse_vex | SUSE CVE CVE-2019-12222 | recommended: 21 | 2026-06-07T05:29:20+00:00 | Vulnerability · Source |
| CVE-2019-14868 | suse_vex | SUSE CVE CVE-2019-14868 | known affected: 382 known not affected: 11 recommended: 21 | 2026-06-07T05:27:11+00:00 | Vulnerability · Source |
| CVE-2019-15939 | suse_vex | SUSE CVE CVE-2019-15939 | recommended: 171 | 2026-06-07T05:25:59+00:00 | Vulnerability · Source |
| CVE-2019-16723 | suse_vex | SUSE CVE CVE-2019-16723 | recommended: 7 | 2026-06-07T05:25:40+00:00 | Vulnerability · Source |
| CVE-2019-16865 | suse_vex | SUSE CVE CVE-2019-16865 | known affected: 1 recommended: 516 | 2026-06-07T05:25:30+00:00 | Vulnerability · Source |
| CVE-2019-17358 | suse_vex | SUSE CVE CVE-2019-17358 | recommended: 7 | 2026-06-07T05:25:01+00:00 | Vulnerability · Source |
| CVE-2019-19338 | suse_vex | SUSE CVE CVE-2019-19338 | known affected: 416 known not affected: 73 recommended: 1390 | 2026-06-07T05:23:09+00:00 | Vulnerability · Source |
| CVE-2019-19911 | suse_vex | SUSE CVE CVE-2019-19911 | known affected: 1 recommended: 509 | 2026-06-07T05:22:37+00:00 | Vulnerability · Source |
| CVE-2019-20053 | suse_vex | SUSE CVE CVE-2019-20053 | recommended: 3 | 2026-06-07T05:22:18+00:00 | Vulnerability · Source |
| CVE-2020-5313 | suse_vex | SUSE CVE CVE-2020-5313 | known affected: 1 recommended: 516 | 2026-06-07T05:19:54+00:00 | Vulnerability · Source |
| CVE-2020-6808 | suse_vex | SUSE CVE CVE-2020-6808 | recommended: 9 | 2026-06-07T05:18:55+00:00 | Vulnerability · Source |
| CVE-2020-6813 | suse_vex | SUSE CVE CVE-2020-6813 | recommended: 9 | 2026-06-07T05:18:48+00:00 | Vulnerability · Source |
| CVE-2020-6824 | suse_vex | SUSE CVE CVE-2020-6824 | recommended: 9 | 2026-06-07T05:18:43+00:00 | Vulnerability · Source |
| CVE-2020-6826 | suse_vex | SUSE CVE CVE-2020-6826 | recommended: 9 | 2026-06-07T05:18:39+00:00 | Vulnerability · Source |
| CVE-2020-7217 | suse_vex | SUSE CVE CVE-2020-7217 | known affected: 331 known not affected: 18 recommended: 241 | 2026-06-07T05:18:21+00:00 | Vulnerability · Source |