Quick answers
- Is CVE-2026-124487 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124487 being exploited in the wild.
- How severe is CVE-2026-124487?
- 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-124487?
- 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-124487 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-124487?
- 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 improper authorization flaw in the non-patient POST /fhir/DocumentReference/$docref route fails to properly validate patient context, allowing authenticated users with only patients/demo permissions to supply an arbitrary patient parameter and trigger generation of that patient's full clinical CCDA. The generated document is persisted with permissive ACLs (patients|docs), allowing immediate retrieval by the same low-privileged user, enabling cross-patient PHI exfiltration at scale.
Affected products
- OpenEMR OpenEMR before 8.4.0
Timeline
- 2026-09-13: disclosed: GitHub Security Advisory published
- 2026-11-08: advisory: Published to NVD