---
id: "CVE-2026-124466"
page: "https://infrastack.ai/live/CVE-2026-124466"
kind: "vulnerability"
aliases: ["CVE-2026-124466"]
title: "OpenEMR: unauthenticated server-side request forgery via OAuth2 jwks_uri"
severity: "high"
cvss: 7.2
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "OpenEMR", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["cloud", "oauth2", "openemr", "other", "self-hosted"]
not_affected_if: ["no-oauth2-endpoints-exposed", "version-8.4.0-or-later"]
published_at: "2026-11-08T14:18:14+00:00"
first_seen_at: "2026-11-08T14:48:40+00:00"
updated_at: "2026-11-08T14:49:25+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-124466", "first_seen_at": "2026-11-08T14:48:40+00:00"}]
exploit_sources: []
---

# OpenEMR: unauthenticated server-side request forgery via OAuth2 jwks_uri

Link for people: https://infrastack.ai/live/CVE-2026-124466 (this .md is for agents)

OpenEMR before 8.4.0 lets anyone register an OAuth2 client with an unvalidated jwks_uri, then make the server fetch that URL through the token introspection endpoint. An attacker can use the server to probe internal services and reach cloud metadata endpoints.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:OpenEMR affected range not listed fixed no fixed version listed

## How to check

- Check the OpenEMR version in the installed application; a version below `8.4.0` is in the affected range.
- Confirm whether OAuth2 client registration is reachable from the internet on your OpenEMR instance.

## Fix

- OpenEMR: move to `8.4.0` or later.

## Timeline

- 2026-11-08T14:48:40+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-124466

## Documents

- [advisory] Vendor advisory: github.com https://github.com/openemr/openemr/security/advisories/GHSA-mf6h-xc62-9fg4
- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/openemr-before-8.4.0-unauthenticated-ssrf-via-oauth2-client-jwks-uri

## From the sources

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.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_