Read the docs

Server-side request forgery in OpenEMR OAuth2 client jwks_uri

Priority HIGH 70CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
Low · Low · None
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

OpenEMR before 8.4.0 contains a server-side request forgery flaw in its OAuth2 client registration, where the jwks_uri value is not validated (CWE-918). An unauthenticated remote attacker can make the server send HTTP requests by registering a client and triggering the fetch through the token introspection endpoint. This lets the attacker probe internal services and reach cloud metadata endpoints.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00208 10th percentileScored 2026-11-16
Fix Fixed openemr (openemr): 8.4.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
openemropenemrbefore 8.4.08.4.0Patch availableCNA
  • openemr Vendoropenemr Affected before 8.4.0 Fixed in 8.4.0 Patch available CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*——Open-Emr
  • cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:* Versions — — ·Open-Emr

Remediation

Upgrade OpenEMR to 8.4.0, which fixes the issue.

Written with Claude Haiku 5.5 from the sources below · 2026-11-09

  • Fix · CNA openemr (openemr) Fixed in 8.4.0

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    openemr 8.4.0

    15 records Highest priority Priority HIGH 6 HIGH, 5 MEDIUM, 4 LOW

    Other records, highest priority first

    • TI-2026-86808 Token replay and PIN brute force in OpenEMR one-time authenticationPriority HIGH 81
    • TI-2026-86844 Missing authorization in OpenEMR portal onsite-document APIsPriority HIGH 73
    • TI-2026-86843 Improper authorization in OpenEMR REST API lets staff forge prescriptionsPriority HIGH 73

Timeline

  1. 2026-11-08 Threatist record created from CVE-2026-124466
  2. 2026-11-08 Alias added: GHSA-xj63-9399-3j6q
  3. 2026-11-09 CISA SSVC decision points changed
  4. 2026-11-09 Priority changed: MEDIUM → HIGH

References

  • TI-2026-91365 OpenEMR OAuth scope flaw exposes FHIR Patient records to attackers CVSS 4.0CRITICAL 9.3
  • TI-2026-86808 Token replay and PIN brute force in OpenEMR one-time authentication CVSS 4.0CRITICAL 9.3
  • TI-2026-24664 SQL Injection Vulnerability in ajax graphs library (OpenEMR) CVSS 3.1HIGH 8.8
  • TI-2026-85645 Missing access checks in OpenEMR let users reassign documents CVSS 3.1CRITICAL 9.6
  • TI-2026-28796 OpenEMR 8.2.0 Remote Code Execution via CategoryTree eval() Injection CVSS 4.0CRITICAL 9.4
  • TI-2026-20308 OpenEMR's payments gateway_api_key secret rendered into client JS code CVSS 3.1CRITICAL 9.6
See all 277 →

Sources