VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
293841 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-58038 | redhat_vex | timeline: EasyTimeline: Wikimedia Foundation Timeline: Cross-site Scripting vulnerability | known not affected: 1 | 2026-07-03T07:07:00+00:00 | Vulnerability · Source |
| 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-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-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-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-17094 | suse_vex | SUSE CVE CVE-2018-17094 | recommended: 6 | 2026-07-03T04:58:14+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-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-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-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-12391 | suse_vex | SUSE CVE CVE-2020-12391 | known affected: 21 recommended: 9 | 2026-07-03T04:54:15+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-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-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-29974 | suse_vex | SUSE CVE CVE-2021-29974 | known affected: 1 recommended: 9 | 2026-07-03T04:51:21+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 |
| CVE-2022-3560 | suse_vex | SUSE CVE CVE-2022-3560 | known not affected: 13 recommended: 58 | 2026-07-03T04:49:20+00:00 | Vulnerability · Source |
| CVE-2022-22749 | suse_vex | SUSE CVE CVE-2022-22749 | recommended: 9 | 2026-07-03T04:48:43+00:00 | Vulnerability · Source |
| CVE-2022-24790 | suse_vex | SUSE CVE CVE-2022-24790 | known affected: 394 known not affected: 4 recommended: 106 | 2026-07-03T04:48:15+00:00 | Vulnerability · Source |
| CVE-2022-29915 | suse_vex | SUSE CVE CVE-2022-29915 | known not affected: 2 recommended: 9 | 2026-07-03T04:47:34+00:00 | Vulnerability · Source |
| CVE-2022-38475 | suse_vex | SUSE CVE CVE-2022-38475 | known affected: 2 recommended: 9 | 2026-07-03T04:46:56+00:00 | Vulnerability · Source |
| CVE-2022-41793 | suse_vex | SUSE CVE CVE-2022-41793 | recommended: 5 | 2026-07-03T04:46:40+00:00 | Vulnerability · Source |
| CVE-2022-42885 | suse_vex | SUSE CVE CVE-2022-42885 | recommended: 5 | 2026-07-03T04:46:30+00:00 | Vulnerability · Source |
| CVE-2022-43467 | suse_vex | SUSE CVE CVE-2022-43467 | recommended: 10 | 2026-07-03T04:46:20+00:00 | Vulnerability · Source |
| CVE-2022-43607 | suse_vex | SUSE CVE CVE-2022-43607 | recommended: 5 | 2026-07-03T04:46:19+00:00 | Vulnerability · Source |
| CVE-2022-44451 | suse_vex | SUSE CVE CVE-2022-44451 | recommended: 5 | 2026-07-03T04:46:17+00:00 | Vulnerability · Source |
| CVE-2022-44566 | suse_vex | SUSE CVE CVE-2022-44566 | known affected: 394 recommended: 14 | 2026-07-03T04:46:16+00:00 | Vulnerability · Source |
| CVE-2022-46280 | suse_vex | SUSE CVE CVE-2022-46280 | recommended: 10 | 2026-07-03T04:46:02+00:00 | Vulnerability · Source |
| CVE-2022-46289 | suse_vex | SUSE CVE CVE-2022-46289 | recommended: 5 | 2026-07-03T04:45:59+00:00 | Vulnerability · Source |
| CVE-2022-46290 | suse_vex | SUSE CVE CVE-2022-46290 | recommended: 5 | 2026-07-03T04:45:58+00:00 | Vulnerability · Source |
| CVE-2022-46292 | suse_vex | SUSE CVE CVE-2022-46292 | recommended: 5 | 2026-07-03T04:45:57+00:00 | Vulnerability · Source |
| CVE-2022-46294 | suse_vex | SUSE CVE CVE-2022-46294 | recommended: 5 | 2026-07-03T04:45:55+00:00 | Vulnerability · Source |
| CVE-2023-2794 | suse_vex | SUSE CVE CVE-2023-2794 | recommended: 6 | 2026-07-03T04:43:42+00:00 | Vulnerability · Source |
| CVE-2023-4232 | suse_vex | SUSE CVE CVE-2023-4232 | recommended: 6 | 2026-07-03T04:43:14+00:00 | Vulnerability · Source |