Skip to content
major vulnerability· requires attention

Widely used SolarWinds product; IDOR enables privilege escalation and root RCE, risking large-scale enterprise compromise.

Applications

CVE-2026-28302

9.1
Critical
EPSS 0.72%Patch availableJul 22, 2026

IDOR in SolarWinds Serv-U enabling privilege escalation and root RCE.

common questions

Is CVE-2026-28302 being exploited?

Not confirmed. CVE-2026-28302 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.

How severe is CVE-2026-28302?

CVE-2026-28302 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-28302?

Yes. A fix has been recorded for CVE-2026-28302. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-28302 affect?

CVE-2026-28302 affects SolarWinds Serv-U (Linux - high impact), SolarWinds Serv-U (Windows - reduced impact). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-28302?

Patch immediately when available; restrict group-admin accounts; isolate and monitor affected hosts.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
SolarWinds Serv-U (Linux - high impact)SolarWinds Serv-U (Windows - reduced impact)
impact

An attacker with group-administrator access can exploit an IDOR to escalate privileges and execute code as root, fully compromising servers and data.

action required

Immediate action required

affected versions
SolarWinds Serv-U
  • affected15.5.4 HF1 and below

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free