Skip to content
Fencer Intel
high 7.5

CVE-2026-28318 kev in the critical feed json

SolarWinds Serv-U Unauthenticated Denial of Service Vulnerability

published 5mo ago modified 19d ago also EUVD-2026-34268

cvss
7.5
version 3.1, CNA
cisa kev
Exploited
added 2026-06-05
epss
48.0%
EPSS 48.0% chance of exploitation in 30 days, percentile 98%
public exploits
0
none known

Summary

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

Patch / fix

cisa required action Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

  • solarwinds serv-u 15.5.4

Is CVE-2026-28318 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 Fencer

Timeline

  1. Published
  2. CISA SSVC: exploitation active
  3. Added to CISA KEV
  4. CISA patch deadline

Known exploited

Added
5mo ago
Patch by
2026-06-19 (4mo ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor, product
SolarWinds, Serv-U
CISA name
SolarWinds Serv-U Uncontrolled Resource Consumption Vulnerability

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

48.00% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • SolarWinds Serv-U

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

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.