CVE-2026-126473 · Runtime
NO FIX YET · SEE WHAT TO DO
OpenEMR before 8.4.0 mishandles OAuth scope names, so an unauthenticated attacker can register a client that gets system-level FHIR access without approval. That access lets the attacker read, modify and create Patient records.
first public Oct 28, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Organisations running OpenEMR before 8.4.0 that expose its OAuth and FHIR API endpoints. The sources do not say whether instances that restrict client registration or keep the FHIR API off the internet are exposed.
Not affected if openemr-8.4.0-or-later
Who cares fhir, healthcare, openemr, self-hosted
8.4.0 are affected8.4.0 or laterOpenEMR before 8.4.0 contains OAuth scope canonicalization and containment flaws that allow unauthenticated attackers to obtain unapproved system-level FHIR access. Attackers can register a colon-form system:Patient.read client that bypasses approval, then request unregistered system/Patient.write scope to read, modify, and create Patient records.
This page as .md · .json · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.