Total
893 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2026-87642 | 1 Google | 1 Chrome | 2026-09-09 | N/A | 4.3 MEDIUM |
| Uninitialized resource in WebGL in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | |||||
| CVE-2026-78519 | 1 Microsoft | 5 365 Apps, Office 2019, Office 2021 and 2 more | 2026-09-09 | N/A | 8.8 HIGH |
| Use of uninitialized resource in Microsoft Office Outlook allows an unauthorized attacker to execute code over a network. | |||||
| CVE-2026-81958 | 1 Microsoft | 7 365 Apps, Excel, Microsoft 365 and 4 more | 2026-09-09 | N/A | 5.5 MEDIUM |
| Use of uninitialized resource in Microsoft Office Excel allows an unauthorized attacker to disclose information locally. | |||||
| CVE-2026-81391 | 1 Microsoft | 7 365 Apps, Excel, Microsoft 365 and 4 more | 2026-09-09 | N/A | 5.5 MEDIUM |
| Use of uninitialized resource in Microsoft Office Excel allows an unauthorized attacker to disclose information locally. | |||||
| CVE-2026-69485 | 2026-09-09 | N/A | 8.8 HIGH | ||
| Use of uninitialized resource in Remote Desktop Client allows an authorized attacker to execute code over a network. | |||||
| CVE-2026-69358 | 2026-09-09 | N/A | 7.1 HIGH | ||
| Use of uninitialized resource in Remote Desktop Client allows an authorized attacker to execute code over a network. | |||||
| CVE-2026-85880 | 1 Microsoft | 8 Windows 10 1607, Windows 10 1809, Windows 10 21h2 and 5 more | 2026-09-09 | N/A | 7.8 HIGH |
| Heap-based buffer overflow in Windows ALPC allows an authorized attacker to elevate privileges locally. | |||||
| CVE-2026-72945 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Use of uninitialized resource in Windows Task Scheduler allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-69770 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Use of uninitialized resource in Windows Spaceport.sys allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-69349 | 2026-09-08 | N/A | 5.7 MEDIUM | ||
| Use of uninitialized resource in Windows Management Instrumentation allows an authorized attacker to disclose information over a network. | |||||
| CVE-2026-69288 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Use of uninitialized resource in Windows GDI+ allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-68873 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Insertion of sensitive information into log file in Windows Program Compatibility Assistant Service allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-72989 | 2026-09-08 | N/A | 7.5 HIGH | ||
| Use of uninitialized resource in Windows Failover Cluster allows an unauthorized attacker to disclose information over a network. | |||||
| CVE-2026-69853 | 2026-09-08 | N/A | 4.7 MEDIUM | ||
| Use of uninitialized resource in Windows Win32K allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-69672 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Use of uninitialized resource in Windows DNS allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-68852 | 2026-09-08 | N/A | 5.5 MEDIUM | ||
| Use of uninitialized resource in Microsoft Account allows an authorized attacker to disclose information locally. | |||||
| CVE-2026-64413 | 1 Linux | 1 Linux Kernel | 2026-09-08 | N/A | 7.0 HIGH |
| In the Linux kernel, the following vulnerability has been resolved: netfilter: ebtables: zero chainstack array sashiko reports: looking at ebtables table translation, could a sparse cpu_possible_mask lead to an uninitialized pointer free? If cpu_possible_mask is sparse (for example, CPU 0 and CPU 2 are possible, but CPU 1 is not), the allocation loop skips CPU 1. If vmalloc_node() fails at CPU 2, the cleanup loop will blindly decrement and call vfree() on newinfo->chainstack[1]. Not a real-world bug, such allocation isn't expected to fail in the first place. | |||||
| CVE-2026-53218 | 1 Linux | 1 Linux Kernel | 2026-09-08 | N/A | 5.5 MEDIUM |
| In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_exthdr: fix register tracking for F_PRESENT flag nft_exthdr_init() passes user-controlled priv->len to nft_parse_register_store(), which marks that many bytes in the register bitmap as initialized. However, when NFT_EXTHDR_F_PRESENT is set, the eval paths write only 1 byte (nft_reg_store8) or 4 bytes (*dest = 0 on TCP/DCCP error path). When len > 4, registers beyond the first are never written, retaining uninitialized stack data from nft_regs. Bail out if userspace requests too much data when F_PRESENT is set. | |||||
| CVE-2026-46132 | 1 Linux | 1 Linux Kernel | 2026-09-08 | N/A | 5.5 MEDIUM |
| In the Linux kernel, the following vulnerability has been resolved: net: rtnetlink: zero ifla_vf_broadcast to avoid stack infoleak in rtnl_fill_vfinfo rtnl_fill_vfinfo() declares struct ifla_vf_broadcast on the stack without initialisation: struct ifla_vf_broadcast vf_broadcast; The struct contains a single fixed 32-byte field: /* include/uapi/linux/if_link.h */ struct ifla_vf_broadcast { __u8 broadcast[32]; }; The function then copies dev->broadcast into it using dev->addr_len as the length: memcpy(vf_broadcast.broadcast, dev->broadcast, dev->addr_len); On Ethernet devices (the overwhelming majority of SR-IOV NICs) dev->addr_len is 6, so only the first 6 bytes of broadcast[] are written. The remaining 26 bytes retain whatever was previously on the kernel stack. The full struct is then handed to userspace via: nla_put(skb, IFLA_VF_BROADCAST, sizeof(vf_broadcast), &vf_broadcast) leaking up to 26 bytes of uninitialised kernel stack per VF per RTM_GETLINK request, repeatable. The other vf_* structs in the same function are explicitly zeroed for exactly this reason - see the memset() calls for ivi, vf_vlan_info, node_guid and port_guid a few lines above. vf_broadcast was simply missed when it was added. Reachability: any unprivileged local process can open AF_NETLINK / NETLINK_ROUTE without capabilities and send RTM_GETLINK with an IFLA_EXT_MASK attribute carrying RTEXT_FILTER_VF. The kernel walks each VF and emits IFLA_VF_BROADCAST, leaking 26 bytes of stack per VF per request. Stack residue at this call site can include return addresses and transient sensitive data; KASAN with stack instrumentation, or KMSAN, will flag the nla_put() when reproduced. Zero the on-stack struct before the partial memcpy, matching the existing pattern used for the other vf_* structs in the same function. | |||||
| CVE-2026-64360 | 1 Linux | 1 Linux Kernel | 2026-09-04 | N/A | 5.5 MEDIUM |
| In the Linux kernel, the following vulnerability has been resolved: hfs/hfsplus: zero-initialize buffer in hfs_bnode_read hfs_bnode_read() can return early without writing to the output buffer when is_bnode_offset_valid() fails or when check_and_correct_requested_ length() corrects the length to zero. Callers such as hfs_bnode_read_ u16() and hfs_bnode_read_u8() pass stack-allocated buffers and use the result unconditionally, leading to KMSAN uninit-value reports. Rather than initializing at each individual call site, zero the buffer at the start of hfs_bnode_read() before any validation checks. This ensures all callers in both hfs and hfsplus get a deterministic zero value regardless of which early-return path is taken. | |||||