Is CVE-2026-124482 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-124482 being exploited in the wild.

How severe is CVE-2026-124482?

Medium severity, with a CVSS score of 6.5, published 8 November 2026.

Is there a fix for CVE-2026-124482?

Yes: fixed in 8.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-124482 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-124482?

Check whether you run OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-124482: OpenEMR authorization bypass in SMART patient-launch

CVE-2026-124482 · Severity: medium · CVSS 6.5 · Published 2026-11-08

OpenEMR is an open-source electronic health record (EHR) system that manages patient medical data. The vulnerability allows a low-privileged user with basic patient access to trick the system into granting them access to any other patient's clinical notes and documents by manipulating the authorization process. An attacker could read sensitive medical records, diagnoses, and treatment plans for patients they should not have access to.

Technologies: OpenEMR. Vendors: OpenEMR.

Quick answers

Is CVE-2026-124482 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-124482 being exploited in the wild.
How severe is CVE-2026-124482?: Medium severity, with a CVSS score of 6.5, published 8 November 2026.
Which products and versions are affected?: OpenEMR before 8.4.0.
Is there a fix for CVE-2026-124482?: Yes: fixed in 8.4.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-124482 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-124482?: Check whether you run OpenEMR at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: 8.4.0

Technical details

An authorization bypass in OpenEMR's SMART standalone-launch implementation allows a low-privileged user with patients|demo ACL to bind arbitrary patient UUIDs into the OAuth token context. The vulnerability stems from the patient picker checking only coarse ACL permissions, storing the chosen UUID in session, and later trusting that token context without re-validation. Attackers can exfiltrate protected health information (PHI) through patient-scoped FHIR DocumentReference and Binary endpoints.

Affected products

OpenEMR OpenEMR before 8.4.0

Timeline

2026-09-13: disclosed: GitHub Security Advisory GHSA-rm4j-gxwp-qh48 published
2026-11-08: advisory: NVD listing published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.