Skip to main content
VulnerabilityPublished Updated

CVE-2025-40540: SolarWinds Serv-U · Incorrect Type Conversion or Cast

Affects SolarWinds Serv-USource CVE Database V5

0
Compare

Not known to be exploited · CVSS 9.1 Critical.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.

Contested

Critical score, yet low EPSS after six months
EPSS
0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Feb 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
SolarWindsServ-UAffected
  • =SolarWinds Serv-U 15.5.3 and prior versions
Fixed in–

AI-suggested

  1. Immediate upgrade to the latest patched version of SolarWinds Serv-U once available; monitor vendor advisories for patch releases.
  2. Restrict administrative access to Serv-U servers to trusted personnel only and enforce strong authentication mechanisms such as multi-factor authentication (MFA).
  3. Run Serv-U services with the least privileges necessary, avoiding running under full administrative accounts, especially on Windows systems.
  4. Implement strict network segmentation and firewall rules to limit access to Serv-U management interfaces and services.
  5. Monitor logs and system behavior for unusual activity indicative of privilege escalation or code execution attempts.
  6. Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block unauthorized code execution.
  7. Conduct regular audits of administrative accounts and permissions on systems running Serv-U.
  8. Prepare incident response plans specifically addressing potential exploitation scenarios involving Serv-U.
  9. If patching is delayed, consider temporary mitigations such as disabling unnecessary Serv-U features or services that could be exploited.
  10. Stay informed through trusted cybersecurity information sharing platforms for any emerging exploit reports or mitigation techniques.

Description

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 medium because services frequently run under less-privileged service accounts by default.

References

Community reviews

Loading reviews…