Quick answers
- Is CVE-2026-124486 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-124486 being exploited in the wild.
- How severe is CVE-2026-124486?
- High severity, with a CVSS score of 8.8, published 8 November 2026.
- Which products and versions are affected?
- OpenEMR before 8.3.0.
- Is there a fix for CVE-2026-124486?
- Yes: fixed in 8.3.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-124486 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-124486?
- 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.3.0
Technical details
The classic document controller is missing from CONTROLLER_ACL_MAP, so the dispatcher applies no base ACL check to controller=document requests. The move_action_process() method updates document categorizations without validating source-document ownership or patient context. The retrieve_action() method then relies only on the document's current category and bypasses the document-to-patient binding check when patient_id is empty, allowing an attacker to move a document into a readable category and retrieve it as cross-patient PHI.
Affected products
- OpenEMR OpenEMR before 8.3.0
Timeline
- 2026-08-18: disclosed
- 2026-11-08: advisory