VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
288036 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-63987 | suse_vex | SUSE CVE CVE-2026-63987 | known affected: 129 known not affected: 167 | 2026-07-30T16:34:08+00:00 | Vulnerability · Source |
| CVE-2026-63988 | suse_vex | SUSE CVE CVE-2026-63988 | known not affected: 296 | 2026-07-30T16:34:05+00:00 | Vulnerability · Source |
| CVE-2026-63989 | suse_vex | SUSE CVE CVE-2026-63989 | known not affected: 296 | 2026-07-30T16:34:04+00:00 | Vulnerability · Source |
| CVE-2026-63990 | suse_vex | SUSE CVE CVE-2026-63990 | known affected: 296 | 2026-07-30T16:34:02+00:00 | Vulnerability · Source |
| CVE-2026-63992 | suse_vex | SUSE CVE CVE-2026-63992 | known affected: 233 known not affected: 65 | 2026-07-30T16:33:57+00:00 | Vulnerability · Source |
| CVE-2026-63993 | suse_vex | SUSE CVE CVE-2026-63993 | No product status | 2026-07-30T16:33:55+00:00 | Vulnerability · Source |
| CVE-2026-63997 | suse_vex | SUSE CVE CVE-2026-63997 | known affected: 84 known not affected: 212 | 2026-07-30T16:33:46+00:00 | Vulnerability · Source |
| CVE-2026-63998 | suse_vex | SUSE CVE CVE-2026-63998 | known affected: 84 known not affected: 212 | 2026-07-30T16:33:44+00:00 | Vulnerability · Source |
| CVE-2026-63999 | suse_vex | SUSE CVE CVE-2026-63999 | known affected: 129 known not affected: 167 | 2026-07-30T16:33:41+00:00 | Vulnerability · Source |
| CVE-2026-64022 | suse_vex | SUSE CVE CVE-2026-64022 | known not affected: 296 | 2026-07-30T16:33:32+00:00 | Vulnerability · Source |
| CVE-2026-64023 | suse_vex | SUSE CVE CVE-2026-64023 | known not affected: 296 | 2026-07-30T16:33:30+00:00 | Vulnerability · Source |
| CVE-2026-64028 | suse_vex | SUSE CVE CVE-2026-64028 | known not affected: 296 | 2026-07-30T16:33:28+00:00 | Vulnerability · Source |
| CVE-2026-64031 | suse_vex | SUSE CVE CVE-2026-64031 | known not affected: 296 | 2026-07-30T16:33:26+00:00 | Vulnerability · Source |
| CVE-2026-64036 | suse_vex | SUSE CVE CVE-2026-64036 | known affected: 129 known not affected: 167 | 2026-07-30T16:33:23+00:00 | Vulnerability · Source |
| CVE-2026-64049 | suse_vex | SUSE CVE CVE-2026-64049 | known not affected: 296 | 2026-07-30T16:33:20+00:00 | Vulnerability · Source |
| CVE-2026-64052 | suse_vex | SUSE CVE CVE-2026-64052 | known affected: 129 known not affected: 167 | 2026-07-30T16:33:18+00:00 | Vulnerability · Source |
| CVE-2026-64053 | suse_vex | SUSE CVE CVE-2026-64053 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:16+00:00 | Vulnerability · Source |
| CVE-2026-64054 | suse_vex | SUSE CVE CVE-2026-64054 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:14+00:00 | Vulnerability · Source |
| CVE-2026-64055 | suse_vex | SUSE CVE CVE-2026-64055 | known affected: 243 known not affected: 53 | 2026-07-30T16:33:12+00:00 | Vulnerability · Source |
| CVE-2026-64058 | suse_vex | SUSE CVE CVE-2026-64058 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:10+00:00 | Vulnerability · Source |
| CVE-2026-64059 | suse_vex | SUSE CVE CVE-2026-64059 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:08+00:00 | Vulnerability · Source |
| CVE-2026-64060 | suse_vex | SUSE CVE CVE-2026-64060 | known affected: 177 known not affected: 119 | 2026-07-30T16:33:07+00:00 | Vulnerability · Source |
| CVE-2026-64062 | suse_vex | SUSE CVE CVE-2026-64062 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:05+00:00 | Vulnerability · Source |
| CVE-2026-64063 | suse_vex | SUSE CVE CVE-2026-64063 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:03+00:00 | Vulnerability · Source |
| CVE-2026-64064 | suse_vex | SUSE CVE CVE-2026-64064 | known affected: 29 known not affected: 267 | 2026-07-30T16:33:00+00:00 | Vulnerability · Source |
| CVE-2026-64065 | suse_vex | SUSE CVE CVE-2026-64065 | known affected: 29 known not affected: 267 | 2026-07-30T16:32:58+00:00 | Vulnerability · Source |
| CVE-2026-64212 | suse_vex | SUSE CVE CVE-2026-64212 | known affected: 12 known not affected: 286 | 2026-07-30T16:32:55+00:00 | Vulnerability · Source |
| CVE-2026-64216 | suse_vex | SUSE CVE CVE-2026-64216 | known affected: 29 known not affected: 269 | 2026-07-30T16:32:50+00:00 | Vulnerability · Source |
| CVE-2026-64217 | suse_vex | SUSE CVE CVE-2026-64217 | known affected: 131 known not affected: 167 | 2026-07-30T16:32:48+00:00 | Vulnerability · Source |
| CVE-2026-64222 | suse_vex | SUSE CVE CVE-2026-64222 | known affected: 219 known not affected: 79 | 2026-07-30T16:32:43+00:00 | Vulnerability · Source |
| CVE-2026-64232 | suse_vex | SUSE CVE CVE-2026-64232 | known affected: 29 known not affected: 269 | 2026-07-30T16:32:33+00:00 | Vulnerability · Source |
| CVE-2026-64235 | suse_vex | SUSE CVE CVE-2026-64235 | known affected: 29 known not affected: 269 | 2026-07-30T16:32:31+00:00 | Vulnerability · Source |
| CVE-2026-64258 | suse_vex | SUSE CVE CVE-2026-64258 | known not affected: 298 | 2026-07-30T16:32:20+00:00 | Vulnerability · Source |
| CVE-2026-64260 | suse_vex | SUSE CVE CVE-2026-64260 | known not affected: 298 | 2026-07-30T16:32:18+00:00 | Vulnerability · Source |
| CVE-2026-64831 | suse_vex | SUSE CVE CVE-2026-64831 | known not affected: 417 | 2026-07-30T16:30:13+00:00 | Vulnerability · Source |
| CVE-2026-64833 | suse_vex | SUSE CVE CVE-2026-64833 | known affected: 417 | 2026-07-30T16:30:11+00:00 | Vulnerability · Source |
| CVE-2026-64834 | suse_vex | SUSE CVE CVE-2026-64834 | known affected: 417 | 2026-07-30T16:30:09+00:00 | Vulnerability · Source |
| CVE-2026-64863 | suse_vex | SUSE CVE CVE-2026-64863 | No product status | 2026-07-30T16:30:07+00:00 | Vulnerability · Source |
| CVE-2026-65703 | suse_vex | SUSE CVE CVE-2026-65703 | known affected: 417 | 2026-07-30T16:30:06+00:00 | Vulnerability · Source |
| CVE-2026-65704 | suse_vex | SUSE CVE CVE-2026-65704 | known affected: 110 known not affected: 307 | 2026-07-30T16:30:04+00:00 | Vulnerability · Source |
| CVE-2026-65705 | suse_vex | SUSE CVE CVE-2026-65705 | known affected: 417 | 2026-07-30T16:30:03+00:00 | Vulnerability · Source |
| CVE-2026-65706 | suse_vex | SUSE CVE CVE-2026-65706 | known affected: 417 | 2026-07-30T16:30:02+00:00 | Vulnerability · Source |
| CVE-2026-66036 | suse_vex | SUSE CVE CVE-2026-66036 | known affected: 110 known not affected: 307 | 2026-07-30T16:29:56+00:00 | Vulnerability · Source |
| CVE-2026-66037 | suse_vex | SUSE CVE CVE-2026-66037 | known affected: 37 known not affected: 380 | 2026-07-30T16:29:54+00:00 | Vulnerability · Source |
| CVE-2026-50219 | redhat_vex | expat: libexpat: Use-after-free vulnerability due to improper handler call depth tracking | fixed: 3 known affected: 22 | 2026-07-30T15:26:16+00:00 | Vulnerability · Source |
| CVE-2026-56132 | redhat_vex | expat: libexpat: Arbitrary Code Execution via Heap-based Buffer Overflow | fixed: 3 known affected: 22 under investigation: 21 | 2026-07-30T15:25:37+00:00 | Vulnerability · Source |
| CVE-2026-47143 | redhat_vex | capstone: Capstone: Denial of Service vulnerability via crafted input | fixed: 4 known not affected: 15 | 2026-07-30T15:25:35+00:00 | Vulnerability · Source |
| CVE-2026-55851 | redhat_vex | io.netty/netty-codec-haproxy: Netty codec-haproxy: Denial of Service via crafted PROXY protocol v2 message | fixed: 3 known affected: 37 known not affected: 1 | 2026-07-30T14:55:15+00:00 | Vulnerability · Source |
| CVE-2026-56820 | redhat_vex | io.netty/netty-handler-ssl-ocsp: Netty: Certificate revocation bypass via OCSP response replay attack | known affected: 2 known not affected: 1 | 2026-07-30T14:55:11+00:00 | Vulnerability · Source |
| CVE-2026-56817 | redhat_vex | io.netty/netty-codec-xml: Netty: Information disclosure via XML External Entity (XXE) vulnerability | known affected: 9 known not affected: 1 | 2026-07-30T14:55:07+00:00 | Vulnerability · Source |