CVE-2025-40553 in the critical feed json
SolarWinds Web Help Desk Deserialization of Untrusted Data Remote Code Execution Vulnerability
published 9mo ago modified 4mo ago also EUVD-2025-206482
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 68.0%
- EPSS 68.0% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 0
- none known
Summary
SolarWinds Web Help Desk was found to be susceptible to an untrusted data deserialization vulnerability that could lead to remote code execution, which would allow an attacker to run commands on the host machine. This could be exploited without authentication.
Patch / fix
- solarwinds web_help_desk 2026.1
Is CVE-2025-40553 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 9mo ago
Exploit prediction
67.98% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/watchtowrlabs/watchTowr-vs-SolarWinds-WebHelpDesk-CVE-2025-40552-CVE-2025-40553/blob/main/watchTowr-vs-SolarWinds-WebHelpDesk-CVE-2025-40552-CVE-2025-40553.py referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- SolarWinds Web Help Desk
Classification
- Weakness
-
- CWE-502 Deserialization of Untrusted Data
References
-
github.com
/watchtowrlabs/watchTowr-vs-SolarWinds-WebHelpDesk-CVE-2025-40552-CVE-2025-40553/blob/main/watchTowr-vs-SolarW
exploit
-
solarwinds.com
/trust-center/security-advisories/CVE-2025-40553
vendor-advisory
-
documentation.solarwinds.com
/en/success_center/whd/content/release_notes/whd_2026-1_release_notes.htm
release-notes
Sources
- CVE List CVE-2025-40553
- NVD CVE-2025-40553
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.