Read the docs

OpenEMR SMART on FHIR Authorization Bypass Exposes Other Patients' Data

Priority LOW 26CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
High
Attack requirements
Present
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

OpenEMR before 8.4.0 contains an authorization bypass in its SMART on FHIR implementation, where checkUserHasAccessToPatient() in BearerTokenAuthorizationStrategy.php always returns true. An authenticated user or a malicious SMART app can manipulate the token launch context to bind requests to arbitrary patient UUIDs. This gives unauthorized read and write access to other patients' FHIR resources.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

Description from the CNA

OpenEMR before 8.4.0 contains an authorization bypass vulnerability in its SMART on FHIR implementation because checkUserHasAccessToPatient() in BearerTokenAuthorizationStrategy.php unconditionally returns true. Authenticated users or malicious SMART apps can manipulate token launch context to bind requests to arbitrary patient UUIDs, gaining unauthorized read/write access to other patients' FHIR resources.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00246 15th percentileScored 2026-11-16
Fix Fixed openemr (openemr): 8.4.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openemropenemrbefore 8.4.08.4.0Patch availableCNA
  • openemr Vendoropenemr Affected before 8.4.0 Fixed in 8.4.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*——Open-Emr
  • cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* Versions — — ·Open-Emr

Remediation

Update OpenEMR to version 8.4.0 or later, which fixes the flaw in the affected range.

Written with Claude Haiku 5.5 from the sources below · 2026-11-08

  • Fix · CNA openemr (openemr) Fixed in 8.4.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    openemr 8.4.0

    15 records Highest priority Priority HIGH 6 HIGH, 5 MEDIUM, 4 LOW

    Other records, highest priority first

    • TI-2026-86808 Token replay and PIN brute force in OpenEMR one-time authenticationPriority HIGH 81
    • TI-2026-86844 Missing authorization in OpenEMR portal onsite-document APIsPriority HIGH 73
    • TI-2026-86843 Improper authorization in OpenEMR REST API lets staff forge prescriptionsPriority HIGH 73

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-124451
  2. 2026-11-08 Alias added: GHSA-85p4-grr3-gp5m
  3. 2026-11-10 Priority changed: MEDIUM → LOW
  4. 2026-11-10 CISA SSVC decision points changed

References

  • TI-2026-91365 OpenEMR OAuth scope flaw exposes FHIR Patient records to attackers CVSS 4.0CRITICAL 9.3
  • TI-2026-86808 Token replay and PIN brute force in OpenEMR one-time authentication CVSS 4.0CRITICAL 9.3
  • TI-2026-24664 SQL Injection Vulnerability in ajax graphs library (OpenEMR) CVSS 3.1HIGH 8.8
  • TI-2026-85645 Missing access checks in OpenEMR let users reassign documents CVSS 3.1CRITICAL 9.6
  • TI-2026-28796 OpenEMR 8.2.0 Remote Code Execution via CategoryTree eval() Injection CVSS 4.0CRITICAL 9.4
  • TI-2026-20308 OpenEMR's payments gateway_api_key secret rendered into client JS code CVSS 3.1CRITICAL 9.6
See all 277 →

Sources