CVE-2026-28318 — SERV-U
HIGHCVE-2026-28318 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in solarwinds serv-u. It is in CISA's Known Exploited Vulnerabilities catalog (added 2026-06-05) — treat it as actively exploited and patch now. A fix is available — see the affected versions and patch details below.
SolarWinds Serv-U is susceptible to specially crafted POST requests that crash the Serv-U service without authentication using Content-Encoding: deflate. Mitigation steps are provided…
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2026-06-05. Federal agencies were required to remediate by 2026-06-19.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2026-28318.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-28318 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 395,249 CVEs with a current EPSS score, this one falls in the 10–50% band (highlighted). Counts from FIRST.org, log-scaled.
Description
SolarWinds Serv-U is susceptible to specially crafted POST requests that crash the Serv-U service without authentication using Content-Encoding: deflate. Mitigation steps are provided to secure customer environments in the SolarWinds Trust Center if you are unable to deploy the update
Affected Products
serv-usolarwindsDetection & mitigation playbook
Vendor / applianceDetect
Inventory every solarwinds serv-u deployment and check each version against the affected-products list above.
Fix
Apply the solarwinds serv-u security patch or hotfix for CVE-2026-28318 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.
Frequently Asked Questions
Is CVE-2026-28318 being exploited in your environment?
Detect and block the exploit chain at execution, on systems you cannot patch yet.