# CVE-2026-24898: OpenEMR has an Unauthenticated MedEx Token Disclosure

> Unauthenticated attackers can obtain MedEx API tokens via a callback endpoint, enabling PHI exfiltration and third-party service compromise.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2026
- **Updated:** 4 Mar 2026
- **Also known as:** GHSA-qwff-3mw7-7rc7

## What is CVE-2026-24898?

CVE-2026-24898 is a critical vulnerability in Open-Emr Openemr, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, 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 8.0.0, an unauthenticated token disclosure vulnerability in the MedEx callback endpoint allows any unauthenticated visitor to obtain the practice's MedEx API tokens, leading to complete third-party service compromise, PHI exfiltration, unauthorized actions on the MedEx platform, and HIPAA violations. The vulnerability exists because the endpoint bypasses authentication ($ignoreAuth = true) and performs a MedEx login whenever $_POST['callback_key'] is provided, returning the full JSON response including sensitive API tokens. This vulnerability is fixed in 8.0.0.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Open-Emr Openemr.

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

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

## Is CVE-2026-24898 being exploited?

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

Public exploit code:

- OpenEMR < 8.0.0 - MedEx Callback Unauthenticated Token Disclosure (nuclei): http/cves/2026/CVE-2026-24898.yaml

## Other vulnerabilities in Open-Emr Openemr

- [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)
- [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-24898 and fix it if it is affected.

What it is: CVE-2026-24898 is a critical vulnerability in Open-Emr Openemr, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24898 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-24898/ (Markdown: https://insights.sbomify.com/CVE-2026-24898/index.md)
```

## Sources

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

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