Unauthorized FHIR access via self-supplied client keys
Published Aug 3, 2026 · Updated Aug 3, 2026
Improper authentication in OpenEMR through 8.2.0 allows unauthenticated attackers to register clients with system-level FHIR scopes. The dynamic registration endpoint accepts an attacker-controlled RSA public key in jwks and binds the requested scopes to the new client. An administrator must approve that client before its matching private key can obtain tokens that read every patient's FHIR resources.
Summary
What happened
Improper authentication in OpenEMR through 8.2.0 allows unauthenticated attackers to register clients with system-level FHIR scopes. The dynamic registration endpoint accepts an attacker-controlled RSA public key in jwks and binds the requested scopes to the new client. An administrator must approve that client before its matching private key can obtain tokens that read every patient's FHIR resources.
The record
- CVE
- CVE-2026-67610
- Published
- Aug 3, 2026
- Updated
- Aug 3, 2026
- Vendor
- OpenEMR Foundation
- Product
- OpenEMR
- Classifications
- CWE-306, T1550.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 3, 2026CVE publishedPublication date reported by the CVE source.
- Aug 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=8.2.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- The Open Door Unauthenticated OAuth2 Client Registration in OpenEMRproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo