VEX records
Browse vendor VEX statements available in this Vulnerability-Lookup instance and pivot to the related vulnerability.
291904 VEX records
API response| Vulnerability | Source | Title | Product status | Imported | Links |
|---|---|---|---|---|---|
| CVE-2026-64129 | suse_vex | SUSE CVE CVE-2026-64129 | known not affected: 296 | 2026-08-05T00:33:24+00:00 | Vulnerability · Source |
| CVE-2026-64139 | suse_vex | SUSE CVE CVE-2026-64139 | known not affected: 296 | 2026-08-05T00:33:22+00:00 | Vulnerability · Source |
| CVE-2026-64144 | suse_vex | SUSE CVE CVE-2026-64144 | known affected: 159 known not affected: 137 | 2026-08-05T00:33:20+00:00 | Vulnerability · Source |
| CVE-2026-64168 | suse_vex | SUSE CVE CVE-2026-64168 | known affected: 144 known not affected: 152 | 2026-08-05T00:33:17+00:00 | Vulnerability · Source |
| CVE-2026-64169 | suse_vex | SUSE CVE CVE-2026-64169 | known not affected: 296 | 2026-08-05T00:33:16+00:00 | Vulnerability · Source |
| CVE-2026-64518 | suse_vex | SUSE CVE CVE-2026-64518 | known affected: 29 known not affected: 269 | 2026-08-05T00:31:00+00:00 | Vulnerability · Source |
| CVE-2026-64524 | suse_vex | SUSE CVE CVE-2026-64524 | known affected: 40 known not affected: 258 | 2026-08-05T00:30:56+00:00 | Vulnerability · Source |
| CVE-2026-65898 | suse_vex | SUSE CVE CVE-2026-65898 | known affected: 14 | 2026-08-05T00:30:49+00:00 | Vulnerability · Source |
| CVE-2026-65899 | suse_vex | SUSE CVE CVE-2026-65899 | known affected: 14 | 2026-08-05T00:30:48+00:00 | Vulnerability · Source |
| CVE-2026-65900 | suse_vex | SUSE CVE CVE-2026-65900 | known affected: 14 | 2026-08-05T00:30:47+00:00 | Vulnerability · Source |
| CVE-2026-65901 | suse_vex | SUSE CVE CVE-2026-65901 | known affected: 14 | 2026-08-05T00:30:45+00:00 | Vulnerability · Source |
| CVE-2026-65902 | suse_vex | SUSE CVE CVE-2026-65902 | known affected: 14 | 2026-08-05T00:30:44+00:00 | Vulnerability · Source |
| CVE-2026-65903 | suse_vex | SUSE CVE CVE-2026-65903 | known affected: 14 | 2026-08-05T00:30:43+00:00 | Vulnerability · Source |
| CVE-2026-65904 | suse_vex | SUSE CVE CVE-2026-65904 | known affected: 14 | 2026-08-05T00:30:41+00:00 | Vulnerability · Source |
| CVE-2026-65911 | suse_vex | SUSE CVE CVE-2026-65911 | known affected: 14 | 2026-08-05T00:30:40+00:00 | Vulnerability · Source |
| CVE-2026-65912 | suse_vex | SUSE CVE CVE-2026-65912 | known affected: 14 | 2026-08-05T00:30:38+00:00 | Vulnerability · Source |
| CVE-2026-65913 | suse_vex | SUSE CVE CVE-2026-65913 | known affected: 14 | 2026-08-05T00:30:36+00:00 | Vulnerability · Source |
| CVE-2026-65914 | suse_vex | SUSE CVE CVE-2026-65914 | known affected: 14 | 2026-08-05T00:30:34+00:00 | Vulnerability · Source |
| CVE-2026-65981 | suse_vex | SUSE CVE CVE-2026-65981 | No product status | 2026-08-05T00:30:32+00:00 | Vulnerability · Source |
| CVE-2026-66010 | suse_vex | SUSE CVE CVE-2026-66010 | known affected: 14 | 2026-08-05T00:30:30+00:00 | Vulnerability · Source |
| CVE-2026-66063 | suse_vex | SUSE CVE CVE-2026-66063 | No product status | 2026-08-05T00:30:20+00:00 | Vulnerability · Source |
| CVE-2026-66064 | suse_vex | SUSE CVE CVE-2026-66064 | No product status | 2026-08-05T00:30:19+00:00 | Vulnerability · Source |
| CVE-2026-66759 | suse_vex | SUSE CVE CVE-2026-66759 | known not affected: 26 recommended: 18 | 2026-08-05T00:30:17+00:00 | Vulnerability · Source |
| CVE-2026-67295 | suse_vex | SUSE CVE CVE-2026-67295 | known affected: 140 | 2026-08-05T00:30:14+00:00 | Vulnerability · Source |
| CVE-2026-67300 | suse_vex | SUSE CVE CVE-2026-67300 | known affected: 140 | 2026-08-05T00:30:10+00:00 | Vulnerability · Source |
| CVE-2026-67301 | suse_vex | SUSE CVE CVE-2026-67301 | known affected: 140 | 2026-08-05T00:30:09+00:00 | Vulnerability · Source |
| CVE-2026-67302 | suse_vex | SUSE CVE CVE-2026-67302 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:08+00:00 | Vulnerability · Source |
| CVE-2026-67303 | suse_vex | SUSE CVE CVE-2026-67303 | known affected: 93 known not affected: 47 | 2026-08-05T00:30:07+00:00 | Vulnerability · Source |
| CVE-2026-67304 | suse_vex | SUSE CVE CVE-2026-67304 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:05+00:00 | Vulnerability · Source |
| CVE-2026-67306 | suse_vex | SUSE CVE CVE-2026-67306 | known affected: 49 known not affected: 91 | 2026-08-05T00:30:04+00:00 | Vulnerability · Source |
| CVE-2026-67309 | suse_vex | SUSE CVE CVE-2026-67309 | No product status | 2026-08-05T00:30:03+00:00 | Vulnerability · Source |
| CVE-2026-67312 | suse_vex | SUSE CVE CVE-2026-67312 | known affected: 26 known not affected: 63 | 2026-08-05T00:30:02+00:00 | Vulnerability · Source |
| CVE-2026-67338 | suse_vex | SUSE CVE CVE-2026-67338 | No product status | 2026-08-05T00:30:00+00:00 | Vulnerability · Source |
| CVE-2026-69185 | suse_vex | SUSE CVE CVE-2026-69185 | known affected: 96 known not affected: 331 | 2026-08-05T00:29:56+00:00 | Vulnerability · Source |
| CVE-2026-69198 | suse_vex | SUSE CVE CVE-2026-69198 | known not affected: 236 | 2026-08-05T00:29:53+00:00 | Vulnerability · Source |
| CVE-2026-18103 | redhat_vex | dhcp-server: dhcp-server: Persistent denial of service due to buffer overflow via OMAPI | known affected: 22 | 2026-08-05T00:22:39+00:00 | Vulnerability · Source |
| CVE-2026-31460 | redhat_vex | kernel: drm/amd/display: check if ext_caps is valid in BL setup | known affected: 198 known not affected: 76 | 2026-08-04T23:40:36+00:00 | Vulnerability · Source |
| CVE-2026-43477 | redhat_vex | kernel: drm/i915/vrr: Configure VRR timings after enabling TRANS_DDI_FUNC_CTL | known affected: 198 known not affected: 76 | 2026-08-04T23:40:36+00:00 | Vulnerability · Source |
| CVE-2026-43191 | redhat_vex | kernel: drm/amd/display: Adjust PHY FSM transition to TX_EN-to-PLL_ON for TMDS on DCN35 | known affected: 274 | 2026-08-04T23:40:32+00:00 | Vulnerability · Source |
| CVE-2025-71294 | redhat_vex | kernel: drm/amdgpu: fix NULL pointer issue buffer funcs | known affected: 274 | 2026-08-04T23:40:31+00:00 | Vulnerability · Source |
| CVE-2026-43444 | redhat_vex | kernel: drm/amdkfd: Unreserve bo if queue update failed | known affected: 198 known not affected: 76 | 2026-08-04T23:40:27+00:00 | Vulnerability · Source |
| CVE-2026-43305 | redhat_vex | kernel: drm/amd/display: Fix mismatched unlock for DMUB HW lock in HWSS fast path | known affected: 274 | 2026-08-04T23:40:27+00:00 | Vulnerability · Source |
| CVE-2026-67294 | redhat_vex | FreeRDP: FreeRDP: Server certificate validation bypass via improper Extended Key Usage (EKU) validation | known affected: 31 | 2026-08-04T23:40:25+00:00 | Vulnerability · Source |
| CVE-2026-66401 | redhat_vex | FreeRDP: FreeRDP: Denial of Service via out-of-bounds read in UVC H.264 parser | known affected: 31 | 2026-08-04T23:40:19+00:00 | Vulnerability · Source |
| CVE-2026-68744 | redhat_vex | sssd: sssd: NSS responder uninitialized heap disclosure in initgroups reply | known affected: 134 known not affected: 31 | 2026-08-04T23:39:56+00:00 | Vulnerability · Source |
| CVE-2026-45976 | redhat_vex | kernel: drm/amdgpu: Fix memory leak in amdgpu_ras_init() | known affected: 198 known not affected: 76 | 2026-08-04T23:39:51+00:00 | Vulnerability · Source |
| CVE-2026-50263 | redhat_vex | xorg-x11-server: xorg-x11-server-Xwayland: xorg-x11-server: use-after-free information disclosure in CreateSaverWindow() | fixed: 1021 known affected: 9 | 2026-08-04T23:39:48+00:00 | Vulnerability · Source |
| CVE-2026-50260 | redhat_vex | xorg-x11-server: xorg-x11-server-Xwayland: xorg-x11-server: use-after-free in FreeCounter() | fixed: 1021 known affected: 9 | 2026-08-04T23:39:46+00:00 | Vulnerability · Source |
| CVE-2026-50261 | redhat_vex | xorg-x11-server: xorg-x11-server-Xwayland: xorg-x11-server: use-after-free in SyncChangeCounter() | fixed: 1021 known affected: 9 | 2026-08-04T23:38:46+00:00 | Vulnerability · Source |
| CVE-2026-50256 | redhat_vex | xorg-x11-server: xorg-x11-server-Xwayland: xorg-x11-server: stack buffer overflow in font alias resolution due to libXfont2 name length mismatch | fixed: 1021 known affected: 9 | 2026-08-04T23:38:36+00:00 | Vulnerability · Source |