OpenEMR authorization flaws expose patient records
A batch of OpenEMR advisories breaks OAuth, FHIR and access control checks. One lets an unauthenticated attacker read patient records. Here is what to patch.
By Yaali. November 15, 2026, 6 min read, Vulnerabilities, Patching, Identity.
OpenEMR, one of the most widely deployed open-source electronic health records (EHR) systems, was patched for a cluster of authorization and injection flaws that put patient data within reach of attackers. The problems span broken OAuth (the open authorization standard that issues access tokens) and FHIR scope handling, missing access control checks on dozens of internal endpoints, insecure direct object references, and a SQL injection in the billing code. Most are fixed in OpenEMR 8.5.0; the two OAuth and FHIR flaws were fixed earlier in 8.4.0 and are rolled into 8.5.0.
The headline flaw needs no account at all. The rest need only a low-privilege login, the kind a front-desk clerk or a billing user already has. OpenEMR runs small clinics and solo practices that often put it straight on the internet, so broken authorization here means protected health information (PHI), a regulated and high-value target, is reachable by someone who should never see it. If you run OpenEMR, the version you are on decides whether these are live on your system right now.

The unauthenticated FHIR bypass is the one to fear
CVE-2026-126473, CVSS 9.1. This is the flaw that does not need a login. OpenEMR exposes a FHIR (Fast Healthcare Interoperability Resources, a standard API for exchanging health data) interface, and access to it is meant to be gated by approved OAuth scopes. The scope strings were not canonicalized or contained correctly. An attacker can register an OAuth client using the colon form of a scope, system:Patient.read, which slips past the approval step, then request the unregistered system/Patient.write scope that the server hands over anyway. The result is system-level FHIR access with no human approval and no account, enough to read and modify patient records.
CVE-2026-126494, CVSS 7.1. The same area has a second, quieter problem. ScopeRepository::finalizeScopes() trusts ScopeEntity::containsScope(), which ignores what the client was actually registered for. A SMART on FHIR client registered only for a read scope such as user/<resource>.read can ask for the matching write scope and receive it. A read-only integration becomes a read-write one.
Both are fixed in 8.4.0. If you expose the FHIR API, treat these as the first thing to close.

Missing access control checks scattered through the app
A larger group of flaws share one root cause: internal endpoints that check you are logged in but never call AclMain::aclCheckCore(), the function that confirms your role is allowed to see the data. A low-privilege user who knows the URL can skip the role check entirely.
- CVE-2026-126466, CVSS 8.8. Any authenticated user can POST to
new_comprehensive_save.phpto create patient records, including insurance PHI, and can enumerate existing patients throughnew_search_popup.phpand related search endpoints. - CVE-2026-126468, CVSS 8.8. The reports, dated reminders and batch reminder endpoints, among them
patient_list.php,amc_full_report.phpanddated_reminders.php, lack the access check, so any low-privilege user can pull patient data from them. - CVE-2026-126469, CVSS 8.8. Several scripts under
custom/, includingexport_labworks.php,chart_tracker.phpandexport_registry_xml.php, rely on session authentication alone and disclose patient data to any logged-in user. - CVE-2026-126458, CVSS 8.8.
authorizations_full.phplets any staff user send amode=authorizerequest with an attacker-chosen patient ID and their own cross-site request forgery (CSRF) token, marking arbitrary patients' billing and clinical records as authorized. - CVE-2026-126471, CVSS 6.5. Front-office users without the
patients:medpermission can callprint_referral.phpandtrend_form.phpwith any patient ID to read demographics and clinical details.
Two more expose clinical documents by object reference. CVE-2026-126472, CVSS 8.8 is a missing authorization check in ccdaservice/ccda_gateway.php: a low-privilege user can request the view or dl action with sequential patient IDs and their own CSRF token to pull other patients' C-CDA (Consolidated Clinical Document Architecture, a standard clinical document format) files. CVE-2026-126470, CVSS 8.8 is an insecure direct object reference (IDOR, where an ID in a request is trusted without checking who owns the record) in the Carecoordination module: a user with the send_to_hie permission can supply any document or patient ID to download or transmit that patient's C-CDA, CCR or QRDA documents.
SQL injection in billing, and a config override
CVE-2026-126482, CVSS 8.8. SLEOB::slInvoiceNumber() in src/Billing/SLEOB.php builds a query by concatenating the CLP01 claim identifier taken from an uploaded X12 835 electronic remittance advice (ERA) file, with no escaping or parameter binding. A user with billing permissions, or anyone who can feed the system a crafted ERA file, can inject SQL through that field.
CVE-2026-126487, CVSS 8.8. This one undercuts the others. Authenticated users can override system-wide global configuration by submitting global-prefixed keys through library/ajax/user_settings.php. A per-user setting that is supposed to affect only your own session can rewrite a global security control for everyone, so a hardening setting an administrator relies on may not be the one actually in force.
What to do
- Upgrade to OpenEMR 8.5.0. It contains the fixes for the authorization and injection flaws above, and it includes the 8.4.0 fixes for the OAuth and FHIR scope flaws. If you cannot move to 8.5.0 immediately, 8.4.0 at least closes the unauthenticated FHIR bypass, which is the most dangerous of the set.
- Do not expose OpenEMR directly to the internet. Put the application and its FHIR API behind a VPN or single sign-on (SSO) gateway so no endpoint is reachable without authenticating at the network edge first. Most of these flaws need a session to reach, so a login wall in front of the whole app removes the easy path.
- Review your OAuth clients and FHIR exposure. List every registered OAuth or SMART on FHIR client, remove any you do not recognise, and confirm the scopes each one holds match what it needs. Pay attention to any client carrying a
system/or write scope. - Audit access logs for the affected endpoints. Look in your web server logs for requests to the endpoints named above, especially
ccda_gateway.php,new_comprehensive_save.php,authorizations_full.php, the reminder and report scripts, and FHIRPatientcalls, and flag any that came from unexpected clients, repeated with incrementing patient IDs, or without a prior login. - Rotate and recheck after patching. If the FHIR interface was exposed before you upgraded, revoke and reissue OAuth client credentials, and review which patient records were read or changed through the API during the exposure window.
OpenEMR's advisories were coordinated and the fixes are available, so the work here is upgrading and tightening exposure, not waiting. The pattern underneath, authentication standing in for authorization, is the single most common access-control failure we find in web application tests: the app confirms who you are and then forgets to check what you are allowed to see. A code review of your authorization layer catches the endpoints that never call the access check before an attacker does, and for teams handling health data a compliance and audit readiness review maps PHI exposure to the controls you are measured against.
If you are not sure whether your OpenEMR instance is reachable from outside or which version you run, open the chat and Yaali, our AI agent, will pass the question to the engineer who would do the work.
Sources: OpenEMR GitHub security advisories, GHSA-6xh3-fmm5-jjp4 (CVE-2026-126473), GHSA-6fxw-69cq-m7g6 (CVE-2026-126472), GHSA-3vxh-7hh5-vhhm (CVE-2026-126470), GHSA-cw3f-mhw8-44jp (CVE-2026-126482), GHSA-6h9j-m5w9-8938 (CVE-2026-126468), GHSA-3h5w-672p-v4m9 (CVE-2026-126469), NVD CVE-2026-126473, NVD CVE-2026-126494, NVD CVE-2026-126472, NVD CVE-2026-126470, NVD CVE-2026-126482, NVD CVE-2026-126487, NVD CVE-2026-126468, NVD CVE-2026-126466, NVD CVE-2026-126458, NVD CVE-2026-126471. </content> </invoke>
Read next
- OpenBao OIDC flaw mints identity tokens for anyone
- One SuperTokens app key can hijack sibling tenants
- SonicWall SSL VPN bug lets a password skip SAML and MFA
Back to the blog, or tell us about your system in the chat. Yaali, our AI agent, answers first and brings in an engineer.