# CVE-2026-23501: Command injection in RecoverPoint for Virtual Machines

> A high-privileged remote attacker can execute arbitrary OS commands on Dell RecoverPoint for VMs via an OS command injection vulnerability.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-3r26-v5mf-w4gg

## What is CVE-2026-23501?

CVE-2026-23501 is a high-severity command injection vulnerability in Dell RecoverPoint for Virtual Machines, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Dell RecoverPoint for VMs, versions 6.0.3 and 6.0.3.1, contains an Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') vulnerability. A high privileged attacker with remote access could potentially exploit this vulnerability, leading to Command execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-23501?


## How do I fix CVE-2026-23501?

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

## Is CVE-2026-23501 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-23501 and fix it if it is affected.

What it is: CVE-2026-23501 is a high-severity command injection vulnerability in Dell RecoverPoint for Virtual Machines, published on 19 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-23501 in the wild and no public exploit code.

Affected product: Dell RecoverPoint for Virtual Machines. 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-2026-23501/ (Markdown: https://insights.sbomify.com/CVE-2026-23501/index.md)
```

## Sources

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

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