CVE-2025-40539
Solarwinds Serv-U ≤ 15.5.4
Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2025-40539 is a critical-severity Incorrect Type Conversion or Cast (CWE-704) vulnerability in Solarwinds Serv-U. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 37th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-40539 is a type confusion vulnerability (CWE-704) in SolarWinds Serv-U, a file transfer server software. When exploited, it enables a malicious actor to execute arbitrary native code with the privileges of the affected account. The vulnerability carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H), reflecting its high impact despite requiring high privileges, due to the scope change from network-accessible exploitation.
Exploitation requires administrative privileges on the target system (PR:H), limiting it to attackers who have already gained such access, such as compromised insiders or those escalating from lower privileges. A successful attack can be performed remotely over the network with low complexity (AV:N/AC:L), achieving complete confidentiality, integrity, and availability impacts (C:H/I:H/A:H) in a changed scope (S:C), effectively allowing full system compromise under the service's privileged context.
SolarWinds has addressed the issue in Serv-U version 15.5.4, as detailed in the release notes at https://documentation.solarwinds.com/en/success_center/servu/content/release_notes/servu_15-5-4_release_notes.htm. Additional mitigation guidance and details are provided in the vendor's security advisory at https://www.solarwinds.com/trust-center/security-advisories/CVE-2025-40539. On Windows deployments, the risk is considered medium because Serv-U services often run under less-privileged accounts by default.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-207545
Vulnerability Data
A type confusion vulnerability exists in Serv-U which when exploited, gives a malicious actor the ability to execute arbitrary native code as privileged account. This issue requires administrative privileges to abuse. On Windows deployments, the risk is scored as a…
more
medium because services frequently run under less-privileged service accounts by default.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds incorrect type conversions or casts.
Requiring documented development standards and tools can mandate safe typing, casting rules, and compiler checks that stop the weakness from being introduced.
Security engineering principles can require type-safe design and casting practices that structurally avoid incorrect conversions.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent type-conversion flaws via coding standards, reviews, and testing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover type-conversion defects before release.
Secure development lifecycle includes type-safety reviews that reduce incorrect casts.
Application security requirements can mandate strong typing and safe casting rules.
Secure architecture principles discourage unsafe type conversions in design.
Secure coding standards directly forbid or detect incorrect type casts.