A heap out-of-bounds read vulnerability in the Linux kernel's Network Controller Sideband Interface (NCSI) driver was fixed. The flaw occurs when the payload length field in an NCSI command is larger than the actual netlink attribute data, leading to reading beyond the buffer and leaking kernel heap memory. This vulnerability requires CAP_NET_ADMIN privileges and affects systems with registered NCSI devices, such as OpenBMC on Aspeed BMC SoCs. The issue was discovered by Tencent Yunding Lab's dynamic kernel fuzzer and has been patched in affected Linux kernel versions.
A time-of-check to time-of-use (TOCTOU) race condition was fixed in the Linux kernel's SMC socket implementation. The vulnerability involves a race between smc_listen_out() and listener close operations, which can cause a memory leak by enqueuing child sockets on a closed listener. This can lead to kernel memory exhaustion when a remote peer repeatedly opens TCP connections while the server closes sockets. The issue has been addressed by moving the lock acquisition to cover the state check and enqueue operation atomically.
A vulnerability in the Linux kernel's SMC (Shared Memory Communications) subsystem was fixed. The flaw involved improper handling of incoming qentry pointers in the smc_llc_event_handler() function, where duplicate CONFIRM_LINK or ADD_LINK_CONT requests could overwrite an existing qentry pointer without freeing the previous allocation, causing a memory leak. This issue was addressed by adding a guard to prevent overwriting when a qentry is already set. The vulnerability affects specific Linux kernel versions and has been patched.
A vulnerability in the Linux kernel's mlx5 network driver was resolved where the fw_tracer creation function could return either NULL or ERR_PTR on failure. The code incorrectly treated these return values the same, leading to a NULL pointer dereference and a kernel crash during core dump logic. This flaw could cause a denial of service via system crash. The issue affects specific Linux kernel versions and has been patched.
CVE-2026-56860 is a vulnerability related to quadratic complexity in the resolvePath function within the net/url package of Microsoft software versions 3.0 and 4.0. The issue could potentially lead to performance degradation due to inefficient path resolution.
SilkParasite is a cyberespionage operation assessed with medium confidence as China-nexus that targeted government bodies across Central Asia. Seven remote access tool families were deployed, five of which were previously undocumented: DriveSilkRAT, CookiETagRAT, NomadRAT, GoginRAT, and NodeEdgeRAT. The toolset is small, modular, and professionally engineered with traces of AI-assisted development. Initial access occurred through malicious Microsoft Office documents delivered via spear-phishing, using regionally tailored lures impersonating government ministries. The operation leveraged DLL sideloading as the primary delivery mechanism and used Google Drive for command-and-control communications to hide within trusted services. Infrastructure analysis identified connections to China Unicom's backbone network, and operational patterns suggest a functioning software organization with maintained build pipelines and careful operational security.
This content is a security industry report highlighting Microsoft's recognition as a leader in the Frost Radar™: Cloud Workload Protection Platforms (CWPP) for 2026. It discusses the evolving challenges of protecting cloud workloads, especially in complex environments using containers and Kubernetes, and emphasizes the need for integrated runtime security solutions. Microsoft Defender for Cloud is noted for its comprehensive coverage and integration across infrastructure, workloads, identities, and applications. The report does not describe a specific vulnerability or exploit but rather industry trends and product capabilities.
A high severity vulnerability identified as CVE-2026-46655 affects the virtio-win package used in Red Hat Enterprise Linux 9. This package provides paravirtualized network drivers for Microsoft Windows guests running fully virtualized on Red Hat Enterprise Linux, improving I/O performance. An update to virtio-win is available addressing this issue.
MacSync Stealer is a macOS-targeted information stealer that uses rapidly rotating infrastructure to deliver payloads, communicate with compromised devices, and exfiltrate stolen data. It employs social engineering to trick users into executing commands that retrieve and run malicious payloads. The malware collects sensitive information including macOS Keychain data, browser credentials, SSH keys, and files from user directories. Data is staged, compressed, split into chunks, and exfiltrated via HTTP PUT requests to attacker-controlled domains that frequently change. Despite domain rotation, consistent behavioral patterns in network requests, command-line usage, and process execution provide reliable detection and hunting opportunities. Microsoft Defender Experts identified over 30 related domains by correlating these recurring traits across the attack chain. The attack chain includes payload retrieval, command-and-control communication, data collection, staging, exfiltration, and cleanup.
In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_conntrack_sip: widen NAT rewrite delta to s32 in sip_help_tcp() sip_help_tcp() stores the size change of each NAT-rewritten SIP message in s16 diff and accumulates it in s16 tdiff, but a single message can grow by more than S16_MAX while the packet stays under the 65535 enlarge_skb() limit: nf_nat_sip() rewrites every matching URI, and a long Contact list expands the message by tens of kilobytes. diff then wraps, and "datalen = datalen + diff - msglen" yields a huge unsigned datalen, so the next iteration's ct_sip_get_header() reads past the linearized skb tail. Widen diff, tdiff and the seq_adjust hook to s32. Both are bounded by the 65535 byte packet limit, and the seqadj core is already s32 (nf_ct_seqadj_set() takes s32), so no previously accepted input is rejected. BUG: KASAN: use-after-free in ct_sip_get_header (net/netfilter/nf_conntrack_sip.c:464) Read of size 1 at addr ffff888010800000 by task ksoftirqd/1/25 ct_sip_get_header (net/netfilter/nf_conntrack_sip.c:464) sip_help_tcp (net/netfilter/nf_conntrack_sip.c:1694) nf_confirm (net/netfilter/nf_conntrack_proto.c:183) nf_hook_slow (net/netfilter/core.c:619) ip6_output (net/ipv6/ip6_output.c:246) ip6_forward (net/ipv6/ip6_output.c:690) ipv6_rcv (net/ipv6/ip6_input.c:351) __netif_receive_skb_one_core (net/core/dev.c:6212) process_backlog (net/core/dev.c:6676) __napi_poll (net/core/dev.c:7735) net_rx_action (net/core/dev.c:7955) handle_softirqs (kernel/softirq.c:622) run_ksoftirqd (kernel/softirq.c:1076) ...
In the Linux kernel, the following vulnerability has been resolved: can: peak_usb: peak_usb_start(): fix double free of transfer buffer on URB submit error In peak_usb_start(), each RX URB transfer buffer is allocated with kmalloc() and the URB is flagged URB_FREE_BUFFER so that the final usb_free_urb() also frees the transfer buffer. If usb_submit_urb() fails, the error path frees the buffer explicitly with kfree(buf) and then calls usb_free_urb(urb). Because URB_FREE_BUFFER is set, usb_free_urb() -> urb_destroy() frees the same buffer a second time, a double free of the transfer buffer. BUG: KASAN: double-free in usb_free_urb.part.0+0x91/0xb0 Free of addr ffff8881069ccb80 by task trigger.sh/285 Call Trace: kfree+0x113/0x3c0 usb_free_urb.part.0+0x91/0xb0 Drop the redundant kfree(buf); usb_free_urb() already releases the transfer buffer. This mirrors commit 03819abbeb11 ("net: usb: lan78xx: Fix double free issue with interrupt buffer allocation").
In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix skb leak on flow key update failure during ct ovs_ct_execute() always steals or frees the skb on failure while ovs_flow_key_update() does not. So, if it fails and we return right away, the skb ends up leaked. Fix that by breaking instead and letting the common error handling code at the bottom of the loop to free the skb properly. This is a very unlikely scenario as it requires the packet to become unparseable by applying a set of actions on a previously parseable skb, but should be fixed nevertheless. Reported by Sashiko.
In the Linux kernel, the following vulnerability has been resolved: qede: sync udp_tunnel ports outside qede_lock in the recovery path A TX timeout on a qede NIC that has VXLAN/GENEVE tunnel ports configured wedges the rtnetlink control plane of the whole machine: NETDEV WATCHDOG: ens6f1 (qede): transmit queue 2 timed out 10226 ms [qede_tx_timeout:586(ens6f1)]TX timeout on queue 2! [qede_recovery_handler:2665(ens6f0)]Starting a recovery process The recovery path deadlocks on the driver's own mutex: qede_sp_task rtnl_lock() mutex_lock(&edev->qede_lock) <- taken qede_recovery_handler qede_load udp_tunnel_nic_reset_ntf __udp_tunnel_nic_device_sync info->sync_table == qede_udp_tunnel_sync mutex_lock(&edev->qede_lock) <- same task: deadlock The mutex is not recursive, so the kworker blocks on itself with rtnl_lock held, and neither lock is ever released. Every task that calls rtnl_lock() afterwards (ip, ovs-vswitchd, lldpad, IPv6 addrconf, sshd) blocks forever while the node still answers ping. In a vmcore from an affected production node rtnl_mutex.owner decodes to the very kworker blocked at the innermost mutex_lock() above. Re-sync the tunnel ports from qede_sp_task() after the internal lock is dropped, still under rtnl_lock as the udp_tunnel API requires. This mirrors qede_open(), which calls udp_tunnel_nic_reset_ntf() under rtnl without the internal lock. qede_recovery_handler() now returns whether it has successfully reloaded an open device, and the caller re-syncs the ports only in that case. This keeps the old gating exactly: a device that was down or a failed recovery returns false, as those paths never reached the udp_tunnel_nic_reset_ntf() call before either. This was the only user of the qede_lock()/qede_unlock() helpers, so remove them.
In the Linux kernel, the following vulnerability has been resolved: net: sxgbe: free TX rings on RX allocation failure When RX descriptor ring allocation fails, init_dma_desc_rings() only frees the partially allocated RX rings and returns. The TX rings that were allocated earlier in the same function are leaked. Rearrange error labels to clean up TX rings upon RX failures.
CVE-2026-68441 is a published vulnerability related to the handling of TC_ACT_REDIRECT from qdisc filter chains in Microsoft software version 3.0. No detailed technical or impact information is provided in the available data.
The Microsoft Container Migration Solution Accelerator is a multi-service application that provides a multi-agent, AI-driven migration solution for moving container service configurations to Azure Kubernetes Service. In version 2.1.2 and earlier, a security vulnerability was identified in the Container Migration Solution Accelerator, specifically an authenticated IDOR (Insecure Direct Object Reference) that allows users to read, write, and delete processes belonging to other authenticated users. The issue affects multiple API endpoints, where ownership checks are missing, enabling unauthorized access and modification of migration data across users within the same organization. The vulnerability is present in both process and file management APIs, and the application relies on Entra ID authentication but lacks proper authorization controls between users. Authenticated users are able to access, modify, and delete processes and files belonging to other users without proper authorization checks.
A critical authentication bypass vulnerability (CVE-2026-55040) in Microsoft SharePoint has been exploited using a proof-of-concept exploit published by Rapid7. The flaw allows attackers without privileges to impersonate SharePoint users or administrators, potentially disclosing files and modifying data. Microsoft patched this vulnerability in the July 2026 Patch Tuesday updates for SharePoint Enterprise Server 2016 and SharePoint Server 2019. Although exploit code is being used in attacks, there is no confirmed widespread exploitation in the wild. CISA has issued guidance to secure SharePoint servers, including limiting Internet exposure and applying Microsoft's security hardening recommendations.
A new zero-day exploit named 'ShieldBreak' targets Microsoft Defender, enabling privilege escalation to SYSTEM level on fully patched Windows 10, Windows 11, and Windows Server systems. The exploit bypasses the patch for a previous vulnerability called RoguePlanet (CVE-2026-50656). It requires Microsoft Defender to be enabled to succeed. The exploit was released by a security researcher known as Nightmare Eclipse, who has disclosed multiple zero-days affecting Microsoft products in 2026. Microsoft has patched RoguePlanet but has not yet addressed ShieldBreak. The exploit has been confirmed to work by an independent vulnerability analyst. There is no indication of active exploitation in the wild or an official patch for ShieldBreak at this time.
Microsoft has released its monthly security update for August 2026, which includes 421 vulnerabilities affecting a range of products, including 62 that Microsoft marked as "critical." Microsoft notes that 1 of the vulnerabilities disclosed this month have been exploited in the wild CVE-2026-68820 is an elevation of privilege vulnerability affecting Windows Ancillary Function Driver for WinSock. A Use After Free vulnerability could allow an authorized attacker to elevate privileges locally. This vulnerability has a CVSS base score of 7.0. Out of 62 "critical" vulnerabilities, 40 are remote code execution (RCE) vulnerabilities. Microsoft considers exploitation of the following vulnerabilities more likely. CVE-2026-62893 is a remote code execution vulnerability affecting Windows Deployment Services TFTP Server. A Use After Free could allow an unauthorized attacker to execute code over a network. This vulnerability has a CVSS base score of 9.8. CVE-2026-65665 is a remote code execution vulnerability affecting Microsoft SharePoint Server. Deserialization of Untrusted Data could allow an authorized attacker to execute code over a network. This vulnerability has a CVSS base score of 8.8. CVE-2026-62823 is a remote code execution vulnerability affecting Windows DHCP Server. A Heap-based Buffer Overflow could allow an unauthorized attacker to execute code over an adjacent network. This vulnerability has a CVSS base score of 8.8. Microsoft considers exploitation of the following vulnerabilities less likely. CVE-2026-62830 is an elevation of privilege vulnerability affecting Azure SRE Agent. Missing Authorization could allow an authorized attacker to elevate privileges over a network. This vulnerability has a CVSS base score of 9.9. CVE-2026-50516 is an elevation of privilege vulnerability affecting Microsoft Azure Kubernetes Service. Missing Authentication for Critical Function could allow an unauthorized attacker to elevate privileges over a network. This vulnerability has a CVSS base score of 9.4. Three remote code execution vulnerabilities, CVE-2026-68794 , CVE-2026-68816 and CVE-2026-68804 , affect Microsoft Excel and have a CVSS base score of 7.8. An unauthorized attacker could execute code locally. CVE-2026-68794 is a Heap-based Buffer Overflow. CVE-2026-68816 is a Stack-based Buffer Overflow. CVE-2026-68804 involves a Numeric Truncation Error and a Heap-based Buffer Overflow. CVE-2026-62911 is an elevation of privilege vulnerability affecting Microsoft Exchange Server. Authentication Bypass by Capture-replay could allow an authorized attacker to elevate privileges over a network. This vulnerability has a CVSS base score of 8.0. Nine remote code execution vulnerabilities, CVE-2026-63515 , CVE-2026-65657 , CVE-2026-63532 , CVE-2026-64898 , CVE-2026-64903 , CVE-2026-64909 , CVE-2026-64910 , CVE-2026-64911 and CVE-2026-70130 , affect Microsoft Office and could allow an unauthorized attacker to execute code locally. CVE-2026-63515 involves an Out-of-bounds Read and an Integer Underflow (Wrap or Wraparound) and has a CVSS base score of 7.8. CVE-2026-65657 is a Use After Free and has a CVSS base score of 7.8. CVE-2026-63532 involves an Integer Overflow or Wraparound and a Heap-based Buffer Overflow and has a CVSS base score of 7.8. CVE-2026-64898 involves a Heap-based Buffer Overflow and an Integer Overflow or Wraparound and has a CVSS base score of 7.8. CVE-2026-64903 involves an Integer Overflow or Wraparound and a Heap-based Buffer Overflow and has a CVSS base score of 7.8. CVE-2026-64909 involves an Integer Underflow (Wrap or Wraparound), an Out-of-bounds Read and a Heap-based Buffer Overflow and has a CVSS base score of 7.8. CVE-2026-64910 is an Untrusted Pointer Dereference and has a CVSS base score of 7.8. CVE-2026-64911 involves an Integer Overflow or Wraparound and a Heap-based Buffer Overflow and has a CVSS base score of 7.8. CVE-2026-70130 is a Heap-based Buffer Overflow and has a CVSS base score of 8.4. Five remote code exec…
Microsoft released the Windows 10 KB5120249 cumulative update for versions 22H2 and 21H2 as part of the August 2026 Patch Tuesday. The update addresses security vulnerabilities and bugs, including a fix for File History backup failures to network shares due to invalid credentials and expands the rollout of new Secure Boot certificates. This update is mandatory and improves device security by increasing coverage for Secure Boot certificate deployment. No new issues have been reported with this update so far.