Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 7.5 CISA Known Exploited Vulnerability

CVE-2026-28318

SolarWinds Serv-U Uncontrolled Resource Consumption Vulnerability

SolarWinds Serv-U

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

CVSS
7.5
HIGH
EPSS
1.9%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
4 Jun 2026
CWE-400

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 5 June 2026. US federal agencies were required to remediate it by 19 June 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 1.9%, which is higher than 79.6% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Frequently asked questions

Is CVE-2026-28318 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2026-28318.

What does CVE-2026-28318 affect?

CVE-2026-28318 affects SolarWinds Serv-U. 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

How severe is CVE-2026-28318?

CVE-2026-28318 is rated HIGH with a CVSS base score of 7.5. EPSS puts the probability of exploitation in the next 30 days at 1.9%, higher than 79.6% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 19 June 2026.

How should organisations respond to CVE-2026-28318?

Apply the vendor patch for SolarWinds Serv-U as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.