<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Wsus — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/wsus/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 04 May 2026 14:17:05 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/wsus/feed.xml" rel="self" type="application/rss+xml"/><item><title>Potential WSUS Abuse for Lateral Movement via PsExec</title><link>https://feed.craftedsignal.io/briefs/2024-07-wsus-psexec/</link><pubDate>Mon, 04 May 2026 14:17:05 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2024-07-wsus-psexec/</guid><description>Adversaries may exploit Windows Server Update Services (WSUS) to execute PsExec for lateral movement within a network by abusing the trusted update mechanism to run signed binaries.</description><content:encoded><![CDATA[<p>This detection identifies potential abuse of Windows Server Update Services (WSUS) for lateral movement by executing PsExec. WSUS is designed to manage updates for Microsoft products, ensuring only signed binaries are executed. Attackers can exploit this by using WSUS to distribute and execute Microsoft-signed tools like PsExec, which can then be used to move laterally within the network. This technique leverages the trust relationship inherent in WSUS to bypass security controls. The rule focuses on detecting suspicious processes initiated by <code>wuauclt.exe</code> (the Windows Update client) executing PsExec from the SoftwareDistribution Download Install directories. Defenders should monitor WSUS activity and PsExec executions to detect and respond to this potential threat.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>The attacker compromises a system within the target network.</li>
<li>The attacker gains control over the WSUS server or performs a man-in-the-middle attack to spoof WSUS.</li>
<li>The attacker uses the compromised WSUS server to approve a malicious update containing PsExec.</li>
<li>The WSUS client (<code>wuauclt.exe</code>) on targeted machines downloads the &ldquo;approved&rdquo; update from the WSUS server, placing PsExec in the <code>C:\Windows\SoftwareDistribution\Download\Install\</code> directory.</li>
<li>The WSUS client executes PsExec.</li>
<li>PsExec is used to execute commands or transfer files to other systems on the network.</li>
<li>The attacker uses the compromised systems to gather credentials or move laterally to other high-value targets.</li>
<li>The attacker achieves their objective, such as data exfiltration or ransomware deployment.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows attackers to achieve lateral movement within the network, leading to the compromise of additional systems and sensitive data. This can result in data breaches, financial loss, and reputational damage. The scope of impact depends on the level of access achieved by the attacker and the value of the compromised systems.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Deploy the Sigma rule <code>WSUS PsExec Execution</code> to detect potential WSUS abuse involving PsExec execution.</li>
<li>Enable Sysmon process creation logging (Event ID 1) to gain visibility into process executions, as referenced in the <a href="https://ela.st/sysmon-event-1-setup">setup instructions</a>.</li>
<li>Implement enhanced monitoring and logging for WSUS activities to detect unauthorized changes or updates.</li>
<li>Investigate and remove any unauthorized binaries found in the <code>C:\Windows\SoftwareDistribution\Download\Install\</code> directory.</li>
<li>Review and restrict the accounts authorized to manage WSUS to prevent unauthorized modifications.</li>
</ul>
]]></content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>lateral-movement</category><category>wsus</category><category>psexec</category><category>windows</category></item><item><title>Windows Server Update Service (WSUS) Privilege Escalation via CVE-2026-26174</title><link>https://feed.craftedsignal.io/briefs/2026-04-wsus-privesc/</link><pubDate>Tue, 14 Apr 2026 18:23:14 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-wsus-privesc/</guid><description>CVE-2026-26174 is a race condition vulnerability in Windows Server Update Service that allows an authorized attacker to elevate privileges locally.</description><content:encoded><![CDATA[<p>CVE-2026-26174 describes a race condition vulnerability within the Windows Server Update Service (WSUS). Disclosed on April 14, 2026, this flaw allows a locally authenticated attacker with limited privileges to elevate their privileges to SYSTEM. The vulnerability stems from improper synchronization when WSUS handles concurrent requests, leading to a race condition that can be exploited to overwrite critical system files or manipulate system processes. Successful exploitation could grant an attacker full control over the affected system, potentially enabling lateral movement within the network, data exfiltration, or deployment of malware. Due to the critical role of WSUS in managing updates across an enterprise, this vulnerability poses a significant risk to organizations relying on WSUS for patch management.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker authenticates to the target Windows system with a low-privileged account.</li>
<li>The attacker crafts a malicious request designed to trigger the race condition in WSUS. This might involve sending multiple, simultaneous update requests.</li>
<li>WSUS processes the crafted requests concurrently, leading to unsynchronized access to shared resources.</li>
<li>Due to the race condition, the attacker gains the ability to manipulate a shared resource, such as a temporary file or a registry key, used by WSUS.</li>
<li>The attacker exploits the manipulated shared resource to overwrite a critical system file within the WSUS directory (e.g., a DLL loaded by the WSUS service) or modify a registry setting used by WSUS for configuration.</li>
<li>WSUS service restarts or reloads the modified component, executing the attacker&rsquo;s injected code with elevated privileges.</li>
<li>The attacker&rsquo;s code executes with SYSTEM privileges, granting them full control over the system.</li>
<li>The attacker leverages the elevated privileges to install malicious software, create new accounts, or perform other unauthorized actions.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of CVE-2026-26174 allows a local attacker to elevate privileges to SYSTEM. This level of access grants complete control over the compromised machine. In a networked environment, this could lead to lateral movement to other systems, exfiltration of sensitive data, or the deployment of ransomware. Given that WSUS is often deployed across numerous systems, a single successful exploit could compromise a large number of machines. The vulnerability has a CVSS v3.1 score of 7.0, indicating a high severity.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Apply the patch released by Microsoft to address CVE-2026-26174 on all WSUS servers immediately.</li>
<li>Monitor process creation events for unusual processes spawned by the WSUS service (w3wp.exe) using the &ldquo;Detect Suspicious WSUS Child Processes&rdquo; Sigma rule to detect potential exploitation attempts.</li>
<li>Monitor file modifications within the WSUS installation directory (typically <code>C:\Program Files\Update Services\</code>) using the &ldquo;Detect WSUS File Modifications&rdquo; Sigma rule.</li>
<li>Review WSUS logs for any unusual activity or errors that might indicate an attempted exploitation of CVE-2026-26174.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>cve-2026-26174</category><category>privilege-escalation</category><category>windows</category><category>wsus</category></item></channel></rss>