Security readout for executives and security teams
Plain-English summary
A flaw in SolarWinds Serv-U can let an already privileged domain administrator turn file access into full control of the server. Successful exploitation may execute code as root. The prerequisites narrow the attacker pool, but the potential business impact remains severe. Windows deployments have lower impact according to the CVE description.
Executive priority
Treat this as an urgent privileged-access risk. Prioritize internet-facing or business-critical Serv-U systems, verify versions immediately, and apply SolarWinds-supported remediation. Because exploitation needs an administrative domain account, pair remediation with credential review, permission reduction, and investigation of suspicious privileged activity.
Technical view
CVE-2026-28305 is a CWE-639 insecure direct object reference affecting Serv-U 15.5.4 HF1 and earlier. Exploitation requires a domain account with administrative privileges and read/write access to its home directory. The flaw is network-accessible, requires no user interaction, crosses a security boundary, and can produce root-level remote code execution.
Likely exposure
Exposure is most likely where an affected Serv-U instance is network-reachable and domain administrators have read/write home-directory access. Existing privileged-account compromise or misuse is a key prerequisite. The supplied evidence says versions after 15.5.4 HF1 are unaffected by default, but administrators should confirm exact applicability with SolarWinds.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. Exploitation requires high privileges, reducing opportunistic risk. However, low attack complexity, no user interaction, and possible root execution make it dangerous after administrative credentials are compromised or abused.
Researcher notes
The CVSS 3.1 score is 9.1 with AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. Root-level remote code execution is stated, but the bundle provides no exploit mechanics, observed attacks, or explicit fixed-version statement. Windows impact is described only as lower, without technical quantification.
Mitigation direction
- Inventory Serv-U deployments and identify versions 15.5.4 HF1 or earlier.
- Review SolarWinds guidance and move affected systems to a confirmed non-affected release.
- Restrict Serv-U network access to trusted systems and necessary users.
- Minimize domain administrator access and review home-directory read/write permissions.
- Monitor SolarWinds advisories for updated remediation or exploitation information.
Validation and detection
- Confirm each Serv-U version and compare it with the affected version range.
- Identify domain administrators with read/write access to Serv-U home directories.
- Verify network exposure, including internet-facing and partner-accessible interfaces.
- Review privileged-account and Serv-U activity for unexpected changes or code execution.
- Confirm remediation status against the latest SolarWinds advisory and release notes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28305 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H2.36SolarWindsCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L1.23.4SolarWindsVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Base CVSS 3.1 score
4.7MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.solarwinds.com/trust-center/security-advisories/CVE-2026-28305CVE reference, SolarWinds · vendor-advisory
- https://documentation.solarwinds.com/en/success_center/servu/content/release_notes/servu_2026-3_release_notes.htmCVE reference, SolarWinds
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.