# CVE-2026-24849: OpenEMR Arbitrary File Read Vulnerability

> Authenticated users can read arbitrary files from the server filesystem via a path traversal vulnerability in OpenEMR.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Feb 2026
- **Updated:** 25 Feb 2026
- **Also known as:** GHSA-w6vc-hx2x-48pc

## What is CVE-2026-24849?

CVE-2026-24849 is a critical path traversal vulnerability in Open-Emr Openemr, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 7.0.4, the `disposeDocument()` method in `EtherFaxActions.php` allows authenticated users to read arbitrary files from the server filesystem. Any authenticated user (regardless of privilege level) can exploit this vulnerability to read sensitive files. Version 7.0.4 patches the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Open-Emr Openemr.

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

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

## Is CVE-2026-24849 being exploited?

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

Public exploit code:

- Proof-of-concept exploit for CVE-2026-24849, an authenticated path-traversal / arbitrary file read in OpenEMR's Fax/SMS (EtherFax) module. Any authenticated user  regardless of privilege level  can read arbitrary files from the server filesystem as the web-server user (database credentials, patient documents/PHI, /etc/passwd, … (github_poc): https://github.com/doany1/CVE-2026-24849
- OpenEMR 7.0.2 - Arbitrary File Read (exploitdb)

## 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-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)
- [CVE-2024-37734](https://insights.sbomify.com/CVE-2024-37734/): Privilege escalation in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24849 is a critical path traversal vulnerability in Open-Emr Openemr, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24849 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-24849/ (Markdown: https://insights.sbomify.com/CVE-2026-24849/index.md)
```

## Sources

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

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