In a joint cybersecurity advisory, U.S. and international agencies have released critical guidance to help organizations fortify their on-premise Microsoft Exchange Server environments against persistent threats. The guidance emphasizes that unprotected and misconfigured instances remain prime targets for malicious actors and outlines a comprehensive strategy to secure these vital communication hubs.
A Unified Call to Secure Exchange Servers
The guidance was co-authored by the U.S. Cybersecurity and Infrastructure Security Agency (CISA), the National Security Agency (NSA), and their partners from Australia and Canada. It stresses that securing Exchange servers is fundamental to protecting the integrity and confidentiality of enterprise communications.
“By restricting administrative access, implementing multi-factor authentication, enforcing strict transport security configurations, and adopting zero trust (ZT) security model principles, organizations can significantly bolster their defenses against potential cyber attacks,” CISA stated.
A key recommendation is the decommissioning of end-of-life on-premises or hybrid Exchange servers once a transition to Microsoft 365 has been completed.
Essential Hardening Practices for Microsoft Exchange
The advisory provides a detailed list of actionable best practices to reduce the attack surface of Exchange Servers:
- Patching and Maintenance: Maintain a rigorous schedule for security updates and patching.
- Baseline Security: Apply and maintain the Exchange Server baseline, Windows security baselines, and relevant mail client security baselines.
- Enable Security Features: Ensure the Exchange Emergency Mitigation Service is active. Enable antivirus, Windows Antimalware Scan Interface (AMSI), Attack Surface Reduction (ASR) rules, and Endpoint Detection and Response (EDR) solutions.
- Access Control: Restrict administrative access to the Exchange Admin Center (EAC) and remote PowerShell. Enforce the principle of least privilege.
- Authentication Hardening: Configure strong protocolIOCss like Transport Layer Security (TLS), HTTP Strict Transport Security (HSTS), and Extended Protection (EP). Prefer Kerberos and SMB over the weaker NTLM protocol. Implement multi-factor authentication (MFA) universally.
- Remote PowerShell: Disable remote PowerShell access for standard users within the Exchange Management Shell (EMS).
Urgent Alert: Actively Exploited WSUS Vulnerability (CVE-2025-59287)
Concurrent with the Exchange guidance, CISA updated an alert concerning a critical, actively exploited vulnerability in Windows Server Update Services (WSUS)—CVE-2025-59287. This flaw could allow attackers to achieve remote code execution on affected servers.
Sophos reported that threat actors are already exploiting this vulnerability to harvest sensitive data from U.S. organizations across various sectors, including universities, technology, manufacturing, and healthcare. The exploitation activity began on October 24, 2025, just one day after Microsoft released an out-of-band patch.
Attack Chain and Detection Recommendations
In these attacks, adversaries leverage vulnerable WSUS servers to run Base64-encoded PowerShell commands, exfiltrating the stolen data to external endpoints like webhook[.]site.
CISA recommends organizations:
- Immediately apply the Microsoft security update for WSUS.
- Monitor for suspicious child processes spawned with SYSTEM-level permissions, especially from
wsusservice.exeorw3wp.exe. - Scrutinize nested PowerShell processes that use base64-encoded commands.
Sophos has identified at least six confirmed incidents among its customers, with further research pointing to over 50 victims. “This activity shows that threat actors moved quickly to exploit this critical vulnerability,” said Rafe Pilling, Director of Threat Intelligence at Sophos Counter Threat Unit. “We’re not seeing further mass exploitation at this time, but it’s still early, and defenders should treat this as an early warning.”
A Deeper Technical Insight
Adding a layer of complexity, researchers at Splunk discovered an alternate attack chain. Michael Haag, a Principal Threat Research Engineer, noted that the vulnerability “goes deeper than expected.” He found that the exploit can also be triggered via the Microsoft Management Console (mmc.exe) when an administrator opens the WSUS Admin Console or selects “Reset Server Node,” generating a specific Event Log crash.


