What is CVE-2026-28318?

CVE-2026-28318 is SolarWinds Serv-U Unauthenticated Denial of Service Vulnerability. The supplied enrichment data classifies it as Denial of Service mapped to CWE-400 Uncontrolled Resource Consumption.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Is there a public exploit?

12 public PoC repositories reported; 0 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2026-28318 using CVSS 7.5, EPSS 40%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

Workarounds are not confirmed from current sources. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

No public threat actor linkage is confirmed from current sources. Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighDenial of Servicepublic exploit

CVE-2026-28318

CVE-2026-28318 — SolarWinds Serv-U Unauthenticated Denial of Service Vulnerability

Q: Is it in CISA KEV?

Yes. The supplied enrichment data lists CVE-2026-28318 in CISA KEV with 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.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

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

Published Jun 4, 2026Updated Jul 22, 2026Sources: NVD, SolarWinds (CNA), CISA, FIRST EPSS, GitHub, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Jun 5, 2026

EPSS

40%

ahead of 99% of scored CVEs

Affects

SolarWinds

Serv-U

CVSS base

7.5

high

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

Yes

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade to SolarWinds Serv-U 15.5.4 Hotfix 1. Use the mitigation steps until the upgrade is possible.

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.

Federal deadline Jun 19, 2026 — passed 89 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

Identify exposed assets running affected vendor/product/version combinations.
Treat as emergency remediation because CISA KEV status is present.
Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

Vendor	Product	Versions	Status
SolarWinds	Serv-U	15.5.4 and previous versions	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

None

Integrity

None

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

None

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

Score	Version	Severity	Expl.	Impact	Source
7.5	CVSS 3.1	high	3.9	3.6	solarwinds.com (CNA), SolarWinds (CNA)

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

What this weakness leads to

MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.

MITRE

CWE-400 · Uncontrolled Resource Consumption

DoS: Crash, Exit, or Restart
DoS: Resource Consumption (CPU)
DoS: Resource Consumption (Memory)
DoS: Resource Consumption (Other)

Mitigation: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.

Weakness & attack patterns

CWE-400Uncontrolled Resource Consumption

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-147 · XML Ping of the DeathCAPEC-492 · Regular Expression Exponential BlowupCAPEC-197 · XML Entity Expansion

T1499Endpoint Denial of Service

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Jun 5, 2026

Federal deadline

Jun 19, 2026

passed 89 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

35 more posts on this CVEShowing 5 of 40 · Who is discussing this CVE, and how loudlyUnlock free

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

Prioritize edge telemetry for network-reachable Serv-U.
Monitor for scanner or exploit-pattern traffic after 12 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

2026
Added · CVSS 3.1 7.5 (AV:N)
Jul 22, 2026 · NVD
Cve is exploited EaEa0001/servu-cve-2026-28318-poc
Jun 10, 2026 · SOCRadar CTI
Added to CISA KEV catalog
Jun 5, 2026 · CISA
Initial · CVE published
Jun 4, 2026 · NVD

Source activity

Readings a source repeats on a schedule, counted rather than listed.

19×SvrsJun 6, 2026 – Jul 5, 2026 · SOCRadar CTI
11×TweetsJun 7, 2026 – Jun 29, 2026 · SOCRadar CTI
4×TelegramJun 6, 2026 – Jun 17, 2026 · SOCRadar CTI
4×Github ReposJun 6, 2026 – Jun 12, 2026 · SOCRadar CTI

References

5 on the record

documentation.solarwinds.com/en/success_center/servu/content/release_notes/servu_15-5-4-hotfix-1_release_notes.htm
Release Notes, NIST
www.solarwinds.com/trust-center/security-advisories/CVE-2026-28318
Vendor Advisory, NIST
www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-28318
US Government Resource, NIST
documentation.solarwinds.com/en/success_center/servu/content/release_notes/servu_15-5-4-hotfix-1_release_notes.htm#link7
Vendor Advisory
nvd.nist.gov/vuln/detail/CVE-2026-28318
Vendor Advisory

Coverage

18 stories from the feeds we poll

13 more reports on this CVEShowing 5 of 18 · Vendor research and security press coverageUnlock free

Elsewhere on this site

SolarWindsevery CVE for this vendor
June 2026what else CISA listed
Denial of Servicesame class
CWE-400other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record1

What should defenders know first?

CVE-2026-28318 is SolarWinds Serv-U Unauthenticated Denial of Service Vulnerability, a high vulnerability affecting Serv-U from SolarWinds. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 12 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.5 describes technical severity, while EPSS 40% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.