# CVE-2026-32238: OpenEMR has Remote Code Execution in backup functionality

> Authenticated attackers can execute arbitrary commands via insufficient input validation in the backup functionality of OpenEMR.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-6pmc-3xm7-pm86

## What is CVE-2026-32238?

CVE-2026-32238 is a critical command injection vulnerability in Open-Emr Openemr, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenEMR is a free and open source electronic health records and medical practice management application. Versions prior to 8.0.0.2 contain a Command injection vulnerability in the backup functionality that can be exploited by authenticated attackers. The vulnerability exists due to insufficient input validation in the backup functionality. Version 8.0.0.2 fixes the issue.

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

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

It affects 1 product.


Products: Open-Emr Openemr.

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

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

## Is CVE-2026-32238 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32238 exists.

Public exploit code:

- Remote code execution vulnerability in OpenEMR <8.0.0.2. (github_poc): https://github.com/ChrisSub08/CVE-2026-32238_RemoteCodeExecutionOpenEMR8.0.0

## Other vulnerabilities in Open-Emr Openemr

- [CVE-2026-24898](https://insights.sbomify.com/CVE-2026-24898/): OpenEMR has an Unauthenticated MedEx Token Disclosure (critical 10.0)
- [CVE-2026-24849](https://insights.sbomify.com/CVE-2026-24849/): OpenEMR Arbitrary File Read Vulnerability (critical 10.0)
- [CVE-2026-24908](https://insights.sbomify.com/CVE-2026-24908/): OpenEMR has SQL Injection in Patient API Sort Parameter (critical 10.0)
- [CVE-2022-2734](https://insights.sbomify.com/CVE-2022-2734/): Improper Restriction of Rendered UI Layers or Frames in openemr/openemr (critical 10.0)
- [CVE-2024-22611](https://insights.sbomify.com/CVE-2024-22611/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32238 is a critical command injection vulnerability in Open-Emr Openemr, published on 19 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32238 exists.

Affected product: Open-Emr Openemr. 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-32238/ (Markdown: https://insights.sbomify.com/CVE-2026-32238/index.md)
```

## Sources

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

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