Description
OpenEMR before 8.4.0 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make the server send HTTP requests by registering an OAuth2 client with an unvalidated jwks_uri. Attackers can trigger the fetch via the token introspection endpoint with an unsigned client_assertion to probe internal services and reach cloud metadata endpoints.
Published: 2026-11-08
Score: 6.9 Medium
EPSS: n/a
KEV: No
Impact: Unauthenticated Server‑Side Request Forgery
Action: Immediate Patch
AI Analysis

Impact

This vulnerability allows an unauthenticated attacker to configure an OAuth2 client with an arbitrary jwks_uri, causing the OpenEMR server to issue HTTP requests to any destination specified by the attacker. The flaw permits the attacker to reach internal services and cloud metadata endpoints via the token introspection endpoint, potentially exposing sensitive configuration data, enabling lateral movement, and providing a foothold for further exploitation. The weakness is a classic SSRF reflected through unvalidated input, categorized as CWE‑918.

Affected Systems

The vulnerability affects the OpenEMR application for all versions released prior to 8.4.0. No specific service packs or sub‑versions are listed as mitigated; use the version information supplied by the vendor for confirmation.

Risk and Exploitability

The CVSS base score of 6.9 indicates a medium severity risk. With no EPSS score available, the current exploitation probability is unknown but could be non‑negligible given the lack of defensive controls. The software is not listed in the CISA KEV catalog. The attack vector is inferred to be internal network access over HTTP, delegated through the unauthenticated client registration flow. Publicly available references suggest that exploitation has been demonstrated in a proof‑of‑concept context, reinforcing the need for timely action.

Generated by OpenCVE AI on November 8, 2026 at 14:44 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade OpenEMR to version 8.4.0 or later, which removes the unvalidated jwks_uri default.
  • Disable or restrict the OAuth2 client registration endpoint until the update is applied, preventing new vulnerable clients from being configured.
  • Apply network segmentation or firewall rules to block outbound requests from the OpenEMR server to internal IP ranges and cloud metadata services, thereby mitigating the impact of any residual SSRF.

Generated by OpenCVE AI on November 8, 2026 at 14:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 08 Nov 2026 13:30:00 +0000

Type Values Removed Values Added
Description OpenEMR before 8.4.0 contains a server-side request forgery vulnerability that allows unauthenticated attackers to make the server send HTTP requests by registering an OAuth2 client with an unvalidated jwks_uri. Attackers can trigger the fetch via the token introspection endpoint with an unsigned client_assertion to probe internal services and reach cloud metadata endpoints.
Title OpenEMR before 8.4.0 Unauthenticated SSRF via OAuth2 Client jwks_uri
First Time appeared Open-emr
Open-emr openemr
Weaknesses CWE-918
CPEs cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*
Vendors & Products Open-emr
Open-emr openemr
References
Metrics cvssV3_1

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

cvssV4_0

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


Subscriptions

Open-emr Openemr
cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-11-08T13:15:51.231Z

Reserved: 2026-11-08T02:16:30.558Z

Link: CVE-2026-124466

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-08T14:18:14.650

Modified: 2026-11-08T14:18:14.650

Link: CVE-2026-124466

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-11-08T15:15:14Z

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)