# CVE-2026-124479: OpenEMR arbitrary local file read in REST document download

Source: https://junglewise.ai/threats/cve-2026-124479-openemr-before-8-4-0-contains-an-arbitrary-local-file-read  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-08. Updated: 2026-11-08  
License: CC BY 4.0 with a link back

CVE-2026-124479 · Severity: medium · CVSS 6.5 · Published 2026-11-08

OpenEMR is a web-based electronic health records system used by healthcare providers to manage patient data. An authenticated attacker with document upload access can upload a specially crafted file containing a server file path, then download it to read sensitive files like database configuration files containing credentials. This could lead to complete compromise of patient data and system access.

Technologies: [OpenEMR Project OpenEMR](https://junglewise.ai/threats/technologies/openemr-project-openemr). Vendors: [OpenEMR Project](https://junglewise.ai/threats/vendors/openemr-project).

## Quick answers

**Is CVE-2026-124479 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-124479 being exploited in the wild.

**How severe is CVE-2026-124479?** Medium severity, with a CVSS score of 6.5, published 8 November 2026.

**Which products and versions are affected?** OpenEMR Project OpenEMR before 8.4.0.

**Is there a fix for CVE-2026-124479?** Yes: fixed in 8.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-124479 attacked?** It is attacked over the network, in a web application.

**Am I affected by CVE-2026-124479?** Check whether you run OpenEMR Project OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- Fixed in 8.4.0

## Technical details

The vulnerability exists in the REST document download service where the controller passes attacker-controlled document bytes directly to Symfony's BinaryFileResponse as a filesystem path rather than as content. An authenticated user with document upload and download privileges can upload a document with an absolute pathname (e.g., /path/to/sqlconf.php) as its body; when retrieved, the REST handler interprets this string as a file path and streams the referenced file instead of the uploaded content. This requires prior authentication and document access permissions.

## Affected products

- OpenEMR Project OpenEMR before 8.4.0

## Timeline

- 2026-09-13: disclosed: GitHub Security Advisory (GHSA-xgxv-36g2-hq5g) published
- 2026-11-08: advisory

## References

- [https://github.com/openemr/openemr/security/advisories/GHSA-xgxv-36g2-hq5g](https://github.com/openemr/openemr/security/advisories/GHSA-xgxv-36g2-hq5g)
- [https://www.vulncheck.com/advisories/openemr-before-8.4.0-arbitrary-file-read-via-rest-document-download](https://www.vulncheck.com/advisories/openemr-before-8.4.0-arbitrary-file-read-via-rest-document-download)

## Related threats

- [OpenEMR account enumeration via timing attack in pre-authentication](https://junglewise.ai/threats/cve-2026-103021-openemr-is-a-free-and-open-source-electronic-health-records-and)
- [OpenEMR open redirect in OIDC logout endpoint](https://junglewise.ai/threats/cve-2026-103019-openemr-is-a-free-and-open-source-electronic-health-records-and)