VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
292285 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2025-71385 | redhat_vex | netdata: Netdata: Arbitrary code execution via reflected Cross-Site Scripting | known not affected: 1 | 2026-07-03T06:40:23+00:00 | Vulnerability · Source |
| CVE-2026-59102 | redhat_vex | Forgejo: Forgejo: Arbitrary JavaScript execution via stored cross-site scripting in Actions run | known not affected: 1 | 2026-07-03T06:40:23+00:00 | Vulnerability · Source |
| CVE-2026-20216 | redhat_vex | ClamAV: ClamAV: Denial of Service via crafted InstallShield file | known not affected: 1 | 2026-07-03T06:17:08+00:00 | Vulnerability · Source |
| CVE-2012-3977 | suse_vex | SUSE CVE CVE-2012-3977 | known not affected: 39 recommended: 11 | 2026-07-03T05:05:23+00:00 | Vulnerability · Source |
| CVE-2013-0748 | suse_vex | SUSE CVE CVE-2013-0748 | known not affected: 39 recommended: 197 | 2026-07-03T05:05:05+00:00 | Vulnerability · Source |
| CVE-2013-0759 | suse_vex | SUSE CVE CVE-2013-0759 | known not affected: 39 recommended: 60 | 2026-07-03T05:05:02+00:00 | Vulnerability · Source |
| CVE-2013-6674 | suse_vex | SUSE CVE CVE-2013-6674 | known affected: 23 known not affected: 144 | 2026-07-03T05:04:18+00:00 | Vulnerability · Source |
| CVE-2014-8627 | suse_vex | SUSE CVE CVE-2014-8627 | recommended: 25 | 2026-07-03T05:03:35+00:00 | Vulnerability · Source |
| CVE-2017-9039 | suse_vex | SUSE CVE CVE-2017-9039 | known affected: 1 known not affected: 134 recommended: 52 | 2026-07-03T05:00:30+00:00 | Vulnerability · Source |
| CVE-2017-12966 | suse_vex | SUSE CVE CVE-2017-12966 | recommended: 1 | 2026-07-03T05:00:03+00:00 | Vulnerability · Source |
| CVE-2018-0487 | suse_vex | SUSE CVE CVE-2018-0487 | recommended: 20 | 2026-07-03T04:59:32+00:00 | Vulnerability · Source |
| CVE-2018-12116 | suse_vex | SUSE CVE CVE-2018-12116 | known affected: 21 known not affected: 175 recommended: 279 | 2026-07-03T04:58:50+00:00 | Vulnerability · Source |
| CVE-2018-12382 | suse_vex | SUSE CVE CVE-2018-12382 | known not affected: 200 recommended: 9 | 2026-07-03T04:58:47+00:00 | Vulnerability · Source |
| CVE-2018-12391 | suse_vex | SUSE CVE CVE-2018-12391 | known affected: 1 recommended: 99 | 2026-07-03T04:58:43+00:00 | Vulnerability · Source |
| CVE-2018-12401 | suse_vex | SUSE CVE CVE-2018-12401 | known affected: 1 recommended: 9 | 2026-07-03T04:58:39+00:00 | Vulnerability · Source |
| CVE-2018-12406 | suse_vex | SUSE CVE CVE-2018-12406 | known affected: 20 known not affected: 168 recommended: 9 | 2026-07-03T04:58:38+00:00 | Vulnerability · Source |
| CVE-2018-15751 | suse_vex | SUSE CVE CVE-2018-15751 | known affected: 394 known not affected: 535 recommended: 1095 | 2026-07-03T04:58:28+00:00 | Vulnerability · Source |
| CVE-2018-17094 | suse_vex | SUSE CVE CVE-2018-17094 | recommended: 6 | 2026-07-03T04:58:14+00:00 | Vulnerability · Source |
| CVE-2018-18499 | suse_vex | SUSE CVE CVE-2018-18499 | known not affected: 200 | 2026-07-03T04:57:49+00:00 | Vulnerability · Source |
| CVE-2018-20587 | suse_vex | SUSE CVE CVE-2018-20587 | recommended: 10 | 2026-07-03T04:57:35+00:00 | Vulnerability · Source |
| CVE-2019-9798 | suse_vex | SUSE CVE CVE-2019-9798 | known affected: 20 known not affected: 76 recommended: 9 | 2026-07-03T04:56:43+00:00 | Vulnerability · Source |
| CVE-2019-9808 | suse_vex | SUSE CVE CVE-2019-9808 | known affected: 20 known not affected: 76 recommended: 9 | 2026-07-03T04:56:41+00:00 | Vulnerability · Source |
| CVE-2019-9809 | suse_vex | SUSE CVE CVE-2019-9809 | known affected: 20 known not affected: 76 recommended: 9 | 2026-07-03T04:56:40+00:00 | Vulnerability · Source |
| CVE-2019-11328 | suse_vex | SUSE CVE CVE-2019-11328 | known affected: 11 known not affected: 18 recommended: 4 | 2026-07-03T04:56:28+00:00 | Vulnerability · Source |
| CVE-2019-13638 | suse_vex | SUSE CVE CVE-2019-13638 | known not affected: 34 recommended: 3 | 2026-07-03T04:55:50+00:00 | Vulnerability · Source |
| CVE-2019-15947 | suse_vex | SUSE CVE CVE-2019-15947 | recommended: 10 | 2026-07-03T04:55:34+00:00 | Vulnerability · Source |
| CVE-2019-17020 | suse_vex | SUSE CVE CVE-2019-17020 | known affected: 21 recommended: 9 | 2026-07-03T04:55:24+00:00 | Vulnerability · Source |
| CVE-2019-17025 | suse_vex | SUSE CVE CVE-2019-17025 | known affected: 21 recommended: 9 | 2026-07-03T04:55:23+00:00 | Vulnerability · Source |
| CVE-2019-19882 | suse_vex | SUSE CVE CVE-2019-19882 | known affected: 2 known not affected: 32 | 2026-07-03T04:55:09+00:00 | Vulnerability · Source |
| CVE-2020-6794 | suse_vex | SUSE CVE CVE-2020-6794 | known affected: 20 recommended: 68 | 2026-07-03T04:54:52+00:00 | Vulnerability · Source |
| CVE-2020-6795 | suse_vex | SUSE CVE CVE-2020-6795 | known affected: 20 recommended: 68 | 2026-07-03T04:54:50+00:00 | Vulnerability · Source |
| CVE-2020-6815 | suse_vex | SUSE CVE CVE-2020-6815 | recommended: 9 | 2026-07-03T04:54:45+00:00 | Vulnerability · Source |
| CVE-2020-6823 | suse_vex | SUSE CVE CVE-2020-6823 | recommended: 9 | 2026-07-03T04:54:42+00:00 | Vulnerability · Source |
| CVE-2020-8565 | suse_vex | SUSE CVE CVE-2020-8565 | recommended: 41 | 2026-07-03T04:54:33+00:00 | Vulnerability · Source |
| CVE-2020-11651 | suse_vex | SUSE CVE CVE-2020-11651 | known affected: 394 known not affected: 13 recommended: 1058 | 2026-07-03T04:54:17+00:00 | Vulnerability · Source |
| CVE-2020-12391 | suse_vex | SUSE CVE CVE-2020-12391 | known affected: 21 recommended: 9 | 2026-07-03T04:54:15+00:00 | Vulnerability · Source |
| CVE-2020-12394 | suse_vex | SUSE CVE CVE-2020-12394 | known affected: 21 recommended: 9 | 2026-07-03T04:54:11+00:00 | Vulnerability · Source |
| CVE-2020-14198 | suse_vex | SUSE CVE CVE-2020-14198 | recommended: 10 | 2026-07-03T04:53:53+00:00 | Vulnerability · Source |
| CVE-2020-14577 | suse_vex | SUSE CVE CVE-2020-14577 | known affected: 536 recommended: 1174 | 2026-07-03T04:53:49+00:00 | Vulnerability · Source |
| CVE-2020-26975 | suse_vex | SUSE CVE CVE-2020-26975 | recommended: 9 | 2026-07-03T04:53:04+00:00 | Vulnerability · Source |
| CVE-2020-26979 | suse_vex | SUSE CVE CVE-2020-26979 | recommended: 9 | 2026-07-03T04:53:01+00:00 | Vulnerability · Source |
| CVE-2020-36327 | suse_vex | SUSE CVE CVE-2020-36327 | known affected: 492 known not affected: 17 recommended: 63 | 2026-07-03T04:52:36+00:00 | Vulnerability · Source |
| CVE-2021-3450 | suse_vex | SUSE CVE CVE-2021-3450 | known affected: 1 known not affected: 675 recommended: 422 | 2026-07-03T04:52:27+00:00 | Vulnerability · Source |
| CVE-2021-23986 | suse_vex | SUSE CVE CVE-2021-23986 | recommended: 9 | 2026-07-03T04:51:43+00:00 | Vulnerability · Source |
| CVE-2021-23988 | suse_vex | SUSE CVE CVE-2021-23988 | recommended: 9 | 2026-07-03T04:51:42+00:00 | Vulnerability · Source |
| CVE-2021-24000 | suse_vex | SUSE CVE CVE-2021-24000 | known affected: 1 recommended: 9 | 2026-07-03T04:51:39+00:00 | Vulnerability · Source |
| CVE-2021-25315 | suse_vex | SUSE CVE CVE-2021-25315 | known affected: 394 known not affected: 142 recommended: 742 | 2026-07-03T04:51:37+00:00 | Vulnerability · Source |
| CVE-2021-29974 | suse_vex | SUSE CVE CVE-2021-29974 | known affected: 1 recommended: 9 | 2026-07-03T04:51:21+00:00 | Vulnerability · Source |
| CVE-2021-31607 | suse_vex | SUSE CVE CVE-2021-31607 | known affected: 394 known not affected: 2 recommended: 1065 | 2026-07-03T04:51:05+00:00 | Vulnerability · Source |
| CVE-2021-34432 | suse_vex | SUSE CVE CVE-2021-34432 | No product status | 2026-07-03T04:50:54+00:00 | Vulnerability · Source |