SolarWinds has issued a security advisory for five critical vulnerabilities in its Web Help Desk (WHD) platform, an IT service management tool used by over 300,000 organizations worldwide. The batch of flaws includes two unauthenticated remote code execution (RCE) vulnerabilities and two authentication bypasses, all rated with a critical CVSS score of 9.8. The disclosure is particularly concerning as it demonstrates a persistent failure to secure the platform; one of the new vulnerabilities is the second failed attempt to patch an insecure deserialization flaw first reported 17 months ago. These vulnerabilities could provide attackers with a direct gateway into an organization's internal IT infrastructure, making immediate remediation essential.
The disclosure covers five distinct but related vulnerabilities that expose SolarWinds WHD instances to severe risk:
A central issue is the recurring failure to fix an insecure deserialization vulnerability in the AjaxProxy component. The original flaw, CVE-2024-28986, was patched, but that patch was bypassed by CVE-2025-26399 in September 2025. Now, CVE-2025-40553 represents a third iteration of the same underlying weakness, demonstrating a systemic issue in the patching process.
The risk is highest for the thousands of organizations that expose their WHD instances directly to the internet.
As of this report, there is no public confirmation of active exploitation in the wild. However, given the critical 9.8 CVSS scores and the history of this vulnerability class, security researchers and threat actors will likely develop proof-of-concept exploits very quickly. The three-week remediation deadline for U.S. federal agencies indicates that intelligence services consider exploitation highly probable.
A successful exploit of the RCE or authentication bypass vulnerabilities would be catastrophic. Since WHD is an IT service management platform, it is often deeply integrated with other core IT systems and holds sensitive data and credentials.
An attacker could:
Security teams should proactively hunt for signs of exploitation attempts against their WHD instances:
/helpdesk/ra.poAjaxProxy endpoint, which has been the source of the deserialization flaws.w3wp.exe or java.execmd.exe, powershell.exe, or any unexpected network connections.Web Server Log Analysis: Scrutinize access logs for internet-facing WHD servers. Look for unusual or malformed requests to the /helpdesk/ra.po endpoint. Any requests containing serialized Java objects or unusual character strings should be investigated.
Endpoint Monitoring: Use an EDR solution to monitor the WHD server for anomalous process creation. The application's worker process should not be spawning command shells or making unexpected outbound connections.
Vulnerability Scanning: Run authenticated and unauthenticated vulnerability scans against WHD instances to confirm if they are vulnerable to the newly disclosed CVEs.
Patch Immediately: The top priority is to update all SolarWinds WHD instances to the latest patched version provided by SolarWinds. Due to the 9.8 CVSS scores, this should be treated as an emergency change.
Restrict Access: If patching cannot be done immediately, restrict network access to the WHD platform. It should not be exposed to the public internet. Access should be limited to internal users or through a secure VPN with multi-factor authentication.
Web Application Firewall (WAF): Deploy a WAF with rules designed to inspect and block malicious serialized objects in HTTP requests. This can provide a layer of virtual patching against deserialization attacks, but it should not be relied upon as a primary control.
CISA adds SolarWinds WHD RCE (CVE-2025-40551) to KEV catalog, confirming active exploitation. Federal agencies must patch by Feb 6; all organizations urged to update.
Immediately applying the patches provided by SolarWinds is the most critical step to protect against these vulnerabilities.
Mapped D3FEND Techniques:
Do not expose the Web Help Desk platform to the public internet. Restrict access to internal networks or via a secure VPN as a compensating control.
Mapped D3FEND Techniques:
Using a Web Application Firewall (WAF) to filter for malicious serialized objects can help block exploitation attempts, but should not replace patching.
Mapped D3FEND Techniques:
SolarWinds discloses five critical vulnerabilities in its Web Help Desk platform.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.