# CVE-2026-76614: OpenEMR < 8.3.0 Path Traversal Information Disclosure via EDI Archive Restore

> Authenticated attackers can probe arbitrary filesystem paths to determine file existence via unsanitized input in the EDI archive restore function.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 19 Aug 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-7994-gr8j-h7xp, GHSA-gfwc-jg5p-jcp4

## What is CVE-2026-76614?

CVE-2026-76614 is a medium-severity path traversal vulnerability in openemr, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenEMR before 8.3.0 contains a path traversal vulnerability in the EDI archive restore function. The archrestore_sel POST parameter is passed to the archive restore handler without sanitization for path traversal sequences. The handler checks whether the supplied path exists on the filesystem, and the differing response messages leak whether the target path exists. An authenticated user with EOB Data Entry permissions can probe arbitrary filesystem paths on the server to determine file existence.

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

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


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

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

## Is CVE-2026-76614 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-76614 is a medium-severity path traversal vulnerability in openemr, published on 19 Aug 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-76614 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-76614/ (Markdown: https://insights.sbomify.com/CVE-2026-76614/index.md)
```

## Sources

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

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