# CVE-2025-26396: SolarWinds Dameware Mini Remote Control Service Incorrect Permissions Local Privilege Escalation Vulnerability

> Local attackers with low-privilege accounts can escalate privileges due to incorrect permissions in SolarWinds Dameware Mini Remote Control Service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-hwrj-qgq6-7mh4

## What is CVE-2025-26396?

CVE-2025-26396 is a high-severity vulnerability in SolarWinds Dameware Mini Remote Control Service, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The SolarWinds Dameware Mini Remote Control was determined to be affected by Incorrect Permissions Local Privilege Escalation Vulnerability. This vulnerability requires local access and a valid low privilege account to be susceptible to this vulnerability.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2025-26396?


## How do I fix CVE-2025-26396?

No fix has been published for CVE-2025-26396 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-26396 being exploited?

There is no known exploitation of CVE-2025-26396 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-26396 and fix it if it is affected.

What it is: CVE-2025-26396 is a high-severity vulnerability in SolarWinds Dameware Mini Remote Control Service, published on 2 Jun 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26396 in the wild and no public exploit code.

Affected product: SolarWinds Dameware Mini Remote Control Service. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-26396/ (Markdown: https://insights.sbomify.com/CVE-2025-26396/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-26396
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-26396
- OSV: https://osv.dev/vulnerability/CVE-2025-26396

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-26396/
Summaries are generated and may contain mistakes; the official description above is the record.