VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
294458 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-12726 | redhat_vex | awx: automation-controller: awx: GitHub webhook second-order SSRF via unvalidated statuses_url exfiltrates PAT credential | known affected: 3 | 2026-07-17T16:43:44+00:00 | Vulnerability · Source |
| CVE-2026-46090 | redhat_vex | kernel: ALSA: aloop: Fix peer runtime UAF during format-change stop | fixed: 2085 known affected: 22 under investigation: 14 | 2026-07-17T16:42:12+00:00 | Vulnerability · Source |
| CVE-2026-31685 | redhat_vex | kernel: netfilter: ip6t_eui64: reject invalid MAC header for all packets | fixed: 2085 known affected: 36 | 2026-07-17T16:42:07+00:00 | Vulnerability · Source |
| CVE-2026-23243 | redhat_vex | kernel: Linux kernel: Denial of service and memory corruption in RDMA umad | fixed: 2295 known affected: 36 | 2026-07-17T16:42:04+00:00 | Vulnerability · Source |
| CVE-2026-43158 | redhat_vex | kernel: xfs: fix freemap adjustments when adding xattrs to leaf blocks | fixed: 2085 known affected: 22 known not affected: 14 | 2026-07-17T16:41:53+00:00 | Vulnerability · Source |
| CVE-2026-43110 | redhat_vex | kernel: wifi: brcmfmac: validate bsscfg indices in IF events | fixed: 1918 known affected: 22 known not affected: 14 | 2026-07-17T16:41:52+00:00 | Vulnerability · Source |
| CVE-2026-44930 | redhat_vex | apache-cxf: org.apache.cxf.services.xkms/cxf-services-xkms-x509-repo-ldap: Apache CXF: Information Disclosure via LDAP Injection | fixed: 1 known affected: 1 known not affected: 1 | 2026-07-17T16:18:32+00:00 | Vulnerability · Source |
| CVE-2026-53166 | redhat_vex | kernel: futex/requeue: Prevent NULL pointer dereference in remove_waiter() on self-deadlock | fixed: 2132 known affected: 22 known not affected: 14 | 2026-07-17T16:13:21+00:00 | Vulnerability · Source |
| CVE-2026-46181 | redhat_vex | kernel: RDMA/mlx4: Fix mis-use of RCU in mlx4_srq_event() | fixed: 1469 known affected: 22 known not affected: 76 under investigation: 14 | 2026-07-17T16:11:29+00:00 | Vulnerability · Source |
| CVE-2026-43198 | redhat_vex | kernel: tcp: fix potential race in tcp_v6_syn_recv_sock() | fixed: 2085 known affected: 22 under investigation: 14 | 2026-07-17T16:11:14+00:00 | Vulnerability · Source |
| CVE-2005-3409 | suse_vex | SUSE CVE CVE-2005-3409 | known not affected: 60 recommended: 12 | 2026-07-17T14:34:03+00:00 | Vulnerability · Source |
| CVE-2006-1494 | suse_vex | SUSE CVE CVE-2006-1494 | known affected: 2110 recommended: 201 | 2026-07-17T14:33:55+00:00 | Vulnerability · Source |
| CVE-2006-1615 | suse_vex | SUSE CVE CVE-2006-1615 | recommended: 14 | 2026-07-17T14:33:54+00:00 | Vulnerability · Source |
| CVE-2006-4250 | suse_vex | SUSE CVE CVE-2006-4250 | recommended: 9 | 2026-07-17T14:33:52+00:00 | Vulnerability · Source |
| CVE-2006-5740 | suse_vex | SUSE CVE CVE-2006-5740 | recommended: 29 | 2026-07-17T14:33:50+00:00 | Vulnerability · Source |
| CVE-2006-5752 | suse_vex | SUSE CVE CVE-2006-5752 | recommended: 61 | 2026-07-17T14:33:49+00:00 | Vulnerability · Source |
| CVE-2007-6596 | suse_vex | SUSE CVE CVE-2007-6596 | recommended: 23 | 2026-07-17T14:33:35+00:00 | Vulnerability · Source |
| CVE-2008-0005 | suse_vex | SUSE CVE CVE-2008-0005 | recommended: 61 | 2026-07-17T14:33:34+00:00 | Vulnerability · Source |
| CVE-2008-2079 | suse_vex | SUSE CVE CVE-2008-2079 | known affected: 1 known not affected: 37 recommended: 173 | 2026-07-17T14:33:28+00:00 | Vulnerability · Source |
| CVE-2008-4865 | suse_vex | SUSE CVE CVE-2008-4865 | recommended: 17 | 2026-07-17T14:33:23+00:00 | Vulnerability · Source |
| CVE-2009-5031 | suse_vex | SUSE CVE CVE-2009-5031 | recommended: 25 | 2026-07-17T14:32:49+00:00 | Vulnerability · Source |
| CVE-2010-2766 | suse_vex | SUSE CVE CVE-2010-2766 | known not affected: 39 recommended: 254 | 2026-07-17T14:32:31+00:00 | Vulnerability · Source |
| CVE-2011-0420 | suse_vex | SUSE CVE CVE-2011-0420 | known affected: 2110 recommended: 482 | 2026-07-17T14:32:10+00:00 | Vulnerability · Source |
| CVE-2011-3005 | suse_vex | SUSE CVE CVE-2011-3005 | known affected: 2 recommended: 143 | 2026-07-17T14:31:41+00:00 | Vulnerability · Source |
| CVE-2012-2391 | suse_vex | SUSE CVE CVE-2012-2391 | recommended: 7 | 2026-07-17T14:30:55+00:00 | Vulnerability · Source |
| CVE-2013-6401 | suse_vex | SUSE CVE CVE-2013-6401 | known affected: 320 known not affected: 35 recommended: 262 | 2026-07-17T14:29:05+00:00 | Vulnerability · Source |
| CVE-2014-2905 | suse_vex | SUSE CVE CVE-2014-2905 | recommended: 10 | 2026-07-17T14:28:01+00:00 | Vulnerability · Source |
| CVE-2014-6431 | suse_vex | SUSE CVE CVE-2014-6431 | recommended: 75 | 2026-07-17T14:27:34+00:00 | Vulnerability · Source |
| CVE-2015-5963 | suse_vex | SUSE CVE CVE-2015-5963 | recommended: 23 | 2026-07-17T14:25:36+00:00 | Vulnerability · Source |
| CVE-2016-0701 | suse_vex | SUSE CVE CVE-2016-0701 | known affected: 320 known not affected: 293 recommended: 791 | 2026-07-17T14:24:32+00:00 | Vulnerability · Source |
| CVE-2016-3096 | suse_vex | SUSE CVE CVE-2016-3096 | known affected: 2 recommended: 8 | 2026-07-17T14:23:43+00:00 | Vulnerability · Source |
| CVE-2016-4493 | suse_vex | SUSE CVE CVE-2016-4493 | known affected: 2 known not affected: 416 | 2026-07-17T14:23:30+00:00 | Vulnerability · Source |
| CVE-2016-7466 | suse_vex | SUSE CVE CVE-2016-7466 | known affected: 407 known not affected: 125 recommended: 1740 | 2026-07-17T14:22:37+00:00 | Vulnerability · Source |
| CVE-2017-5468 | suse_vex | SUSE CVE CVE-2017-5468 | known not affected: 42 recommended: 12 | 2026-07-17T14:20:39+00:00 | Vulnerability · Source |
| CVE-2017-5471 | suse_vex | SUSE CVE CVE-2017-5471 | known affected: 2 known not affected: 42 | 2026-07-17T14:20:37+00:00 | Vulnerability · Source |
| CVE-2017-10197 | suse_vex | SUSE CVE CVE-2017-10197 | known not affected: 42 | 2026-07-17T14:18:40+00:00 | Vulnerability · Source |
| CVE-2017-12620 | suse_vex | SUSE CVE CVE-2017-12620 | recommended: 4 | 2026-07-17T14:18:20+00:00 | Vulnerability · Source |
| CVE-2017-15134 | suse_vex | SUSE CVE CVE-2017-15134 | recommended: 154 | 2026-07-17T14:17:28+00:00 | Vulnerability · Source |
| CVE-2018-5187 | suse_vex | SUSE CVE CVE-2018-5187 | known affected: 21 recommended: 105 | 2026-07-17T14:15:47+00:00 | Vulnerability · Source |
| CVE-2018-15687 | suse_vex | SUSE CVE CVE-2018-15687 | known affected: 320 known not affected: 315 recommended: 643 | 2026-07-17T14:14:03+00:00 | Vulnerability · Source |
| CVE-2019-3902 | suse_vex | SUSE CVE CVE-2019-3902 | known affected: 9 recommended: 65 | 2026-07-17T14:11:47+00:00 | Vulnerability · Source |
| CVE-2019-7548 | suse_vex | SUSE CVE CVE-2019-7548 | known affected: 11 recommended: 421 | 2026-07-17T14:11:24+00:00 | Vulnerability · Source |
| CVE-2019-16094 | suse_vex | SUSE CVE CVE-2019-16094 | recommended: 20 | 2026-07-17T14:08:15+00:00 | Vulnerability · Source |
| CVE-2020-1735 | suse_vex | SUSE CVE CVE-2020-1735 | recommended: 248 | 2026-07-17T14:06:58+00:00 | Vulnerability · Source |
| CVE-2026-57075 | redhat_vex | YAML::Syck: YAML::Syck: Information disclosure via out-of-bounds read in base64 decoder | known affected: 5 | 2026-07-17T14:05:57+00:00 | Vulnerability · Source |
| CVE-2026-57077 | redhat_vex | YAML::Syck: YAML::Syck: Information disclosure via out-of-bounds read | known affected: 5 | 2026-07-17T14:05:54+00:00 | Vulnerability · Source |
| CVE-2026-57076 | redhat_vex | YAML-Syck: YAML::Syck: Heap use-after-free via anchor name reuse | known affected: 5 | 2026-07-17T14:05:50+00:00 | Vulnerability · Source |
| CVE-2026-13713 | redhat_vex | YAML-Syck: YAML::Syck: Denial of Service via crafted YAML document | known affected: 5 | 2026-07-17T14:05:02+00:00 | Vulnerability · Source |
| CVE-2021-31542 | suse_vex | SUSE CVE CVE-2021-31542 | recommended: 274 | 2026-07-17T14:00:07+00:00 | Vulnerability · Source |
| CVE-2021-38509 | suse_vex | SUSE CVE CVE-2021-38509 | known affected: 1 recommended: 404 | 2026-07-17T13:59:19+00:00 | Vulnerability · Source |