Description
OpenEMR through 8.2.0 contains an improper authentication vulnerability in the OAuth2 dynamic client registration endpoint that allows unauthenticated attackers to register a malicious client with system-level FHIR scopes by supplying a self-generated RSA keypair via the jwks field. Once an administrator approves the registered client, attackers can use the client_credentials grant with a self-signed JWT assertion to obtain access tokens granting read access to all FHIR resources across all patients in the system.
Published: 2026-08-03
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability allows an attacker to register a malicious OAuth2 client without authentication. By supplying a self‑generated RSA key pair in the jwks field, the attacker obtains a client with system‑level FHIR scopes. After an administrator approves the client, the attacker can use the client_credentials grant with a self‑signed JWT to acquire access tokens that permit reading every FHIR resource for all patients. This results in full data exfiltration potential, compromising patient confidentiality and violating privacy regulations.

Affected Systems

OpenEMR version 8.2.0 and earlier are affected. Any installation that uses the default OAuth2 dynamic client registration endpoint and accepts self‑generated key material without strict authentication is vulnerable. The problem is tied to the OpenEMR application, not specific operating system platforms.

Risk and Exploitability

The CVSS score of 8.6 indicates high severity, but the EPSS score is not available, suggesting we lack recent exploitation data. The vulnerability is not listed in CISA KEV, so it has not yet been confirmed as widely exploited in the wild. An attacker can exploit it remotely by sending unauthenticated requests to the registration endpoint; no special privileges are required before administrative approval. Once the client is approved, payloads can be sent over the network to obtain read tokens, providing unrestricted access to sensitive healthcare information.

Generated by OpenCVE AI on August 4, 2026 at 10:07 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade OpenEMR to the latest patched release that addresses this registration vulnerability.
  • If an upgrade is not immediately possible, disable or restrict the dynamic client registration endpoint to trusted IP ranges or require mutual authentication before accepting client registrations.
  • Verify the list of approved FHIR clients and revoke any that were added without proper authorization; audit scope assignments to ensure no excessive permissions are granted.

Generated by OpenCVE AI on August 4, 2026 at 10:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 14 Aug 2026 17:15:00 +0000

Type Values Removed Values Added
First Time appeared Open-emr
Open-emr openemr
CPEs cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*
Vendors & Products Open-emr
Open-emr openemr

Mon, 03 Aug 2026 18:15:00 +0000

Type Values Removed Values Added
First Time appeared Openemr
Openemr openemr
Vendors & Products Openemr
Openemr openemr

Mon, 03 Aug 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Mon, 03 Aug 2026 16:30:00 +0000

Type Values Removed Values Added
Description OpenEMR through 8.2.0 contains an improper authentication vulnerability in the OAuth2 dynamic client registration endpoint that allows unauthenticated attackers to register a malicious client with system-level FHIR scopes by supplying a self-generated RSA keypair via the jwks field. Once an administrator approves the registered client, attackers can use the client_credentials grant with a self-signed JWT assertion to obtain access tokens granting read access to all FHIR resources across all patients in the system.
Title OpenEMR 8.2.0 OAuth2 Dynamic Client Registration Unauthorized FHIR Access
Weaknesses CWE-306
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N'}

cvssV4_0

{'score': 8.6, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-08-14T16:50:59.963Z

Reserved: 2026-07-29T21:07:39.202Z

Link: CVE-2026-67610

cve-icon Vulnrichment

Updated: 2026-08-03T16:57:25.269Z

cve-icon NVD

Status : Received

Published: 2026-08-03T17:16:43.703

Modified: 2026-08-03T17:16:43.703

Link: CVE-2026-67610

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T10:15:04Z

Weaknesses
  • CWE-306

    Missing Authentication for Critical Function