Microsoft is working to fix a known issue affecting Windows Server Update Services (WSUS) servers, which has caused synchronization problems for more than a week. [...]

Microsoft has confirmed an ongoing issue affecting Windows Server Update Services (WSUS) servers, leading to extended synchronization times and operational timeouts. This problem, which began in recent days with a noticeable increase in impact starting July 13, 2026, prevents IT administrators from deploying the latest Windows updates via WSUS or Configuration Manager.
WSUS, a service designed to help organizations manage and distribute Microsoft product updates from a local server, typically synchronizes with Microsoft Update servers daily to retrieve update metadata. However, affected servers are unable to complete this synchronization, impacting both client platforms (Windows 10, version 1607 and later) and server platforms (Windows Server 2012 and later).
Microsoft has implemented initial mitigation measures on Saturday, July 18, 2026, which have reportedly restored normal synchronization times and operations for newly installed or rebuilt WSUS servers. However, the company is still developing additional mitigations for existing WSUS servers that were previously affected and continue to experience synchronization difficulties.
The company stated that it is working on steps to help customers safely remove affected metadata from their environments on these previously impacted servers.
This is not the first time WSUS has encountered issues. In May of the previous year, Microsoft addressed a similar problem that caused errors for enterprise customers attempting to update Windows 11 versions 22H2 and 23H2. Additionally, in July 2025, an issue preventing WSUS from syncing with Microsoft Update for the deployment of the latest updates was resolved. A month later, in August 2025, another problem that blocked the delivery of the August 2025 security update via WSUS was also fixed.

Attackers are exploiting a new unpatched vulnerability in Magento Open Source and Adobe Commerce that lets them run malicious code on an online store's server without logging in, Dutch e-commerce security company Sansec said in an advisory published on September 5. Sansec, which discovered the flaw and named it StyleSmuggler, said attacks started on September 4. "Sansec is publishing early

JetBrains is urging Cadence users to revoke and rotate all credentials following a security incident last month in which unidentified threat actors exploited a recently disclosed critical vulnerability in TeamCity to breach its own environment. "Cadence users should immediately revoke or rotate all credentials and secrets that may have been used to run their Cadence executions," JetBrains said.
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
A security flaw has been discovered in Tenda CP3 27.5.57.101. This vulnerability affects the function SystemAsh of the file Apis/system.c of the component Kylin. The manipulation of the argument AlarmVoiceURL results in os command injection. It is possible to launch the attack remotely.

OpenAI has announced a $1 billion commitment to provide subsidized access to its Daybreak AI cybersecurity tools for under-resourced critical infrastructure defenders. The initiative, named Daybreak for Frontline Defenders, will offer AI models, training, and technical support over the next six months, prioritizing water and wastewater utilities, electric grid operators, and local government entities. This move aims to equip organizations with limited budgets and staff against increasingly sophisticated cyber threats.
In BPF instructions that load/store a value from/to a scratch memory register the register index is an unsigned 32-bit integer and must not exceed 15, but libpcap BPF interpreter does not validate the value. In particular uncommon use cases a crafted filter program can cause the interpreter to try reading and writing the OS process memory in the 16GiB starting at the current stack frame on 64-bit architectures and in the entire address space on 32-bit architectures.