Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
CriticalPublic exploit

Unauthenticated Deserialization RCE in SolarWinds Web Help Desk

IdentifiersCVE-2025-40553CWE-502· Deserialization of Untrusted Data

CVE-2025-40553 is a critical deserialization of untrusted data vulnerability in SolarWinds Web Help Desk (WHD). Public reporting and vendor-linked summaries indicate the issue is reachable through WHD’s AjaxProxy/JSON-RPC handling in the legacy WebObjects-based application, where attacker-controlled JSON parameters can be materialized into Java objects. Research cited in the provided content describes this flaw as a patch bypass for earlier WHD deserialization fixes, allowing crafted requests to reach a deserialization sink and ultimately achieve remote code execution. The vulnerability is exploitable remotely and does not require authentication. Affected versions are reported as WHD 12.8.8 Hotfix 1 and below, with fixes released in WHD version 2026.1.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated remote code execution on the underlying WHD host. The attacker can run arbitrary commands on the server and, according to the provided reporting, compromise the system up to the host context used by the vulnerable service; some reporting notes SYSTEM-level impact in practical exploit chains. This can result in full application and server compromise, installation of malware or persistence mechanisms, data theft or tampering, creation of privileged accounts, and use of the WHD server as a foothold for lateral movement.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by restricting or removing internet access to Web Help Desk, especially to WHD /wo/ and related application endpoints implicated in the exploit path. Place the service behind VPN or trusted administrative access controls, segment the host from sensitive internal systems, and monitor logs for suspicious access to Helpdesk.woa/wo/*, unusual JSON-RPC/AjaxProxy activity, org.jabsorb-related errors, and unexpected command execution artifacts. These are temporary risk-reduction measures only and are not substitutes for upgrading to 2026.1.

Remediation

Patch, then assume compromise.

Upgrade SolarWinds Web Help Desk to version 2026.1, which is the vendor-reported fixed release for CVE-2025-40553. Apply the full vendor update rather than relying on partial hotfixes or blacklist-based mitigations from prior deserialization issues. Follow SolarWinds release notes and security advisory guidance for the upgrade. If prior hotfix guidance included manual classpath/library changes, ensure the system is brought fully to the supported fixed version rather than left in an intermediate state.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 2 candidates as fakes, detection scripts, or README-only repos.

VALID 0 / 2 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
SolarWindsWeb Help Deskapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

35 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures1

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity18

Community discussion across Reddit, Mastodon, and other social sources.