# CVE-2026-124479: OpenEMR before 8.4.0 Arbitrary File Read via REST Document Download


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jg97-vcwh-pc35, GHSA-xgxv-36g2-hq5g

## What is CVE-2026-124479?

CVE-2026-124479 is a high-severity vulnerability in openemr, published on 8 Nov 2026. 

### Official description

OpenEMR before 8.4.0 contains an arbitrary local file read vulnerability in REST document download, where the controller passes stored uploaded document bytes to Symfony's BinaryFileResponse as a filesystem path instead of returning them as content. Authenticated users with document upload and download access can upload a document containing an absolute pathname, such as the sqlconf.php location, then download it to read server files and recover database credentials.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-124479 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124479 is a high-severity vulnerability in openemr, published on 8 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-124479 exists.

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

## Sources

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

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