CVE-2026-124466: openemr · Server-Side Request Forgery (SSRF)
Affects openemrSource CVE Database V5
Not known to be exploited · CVSS 6.9 Medium : upgrade to 8.4.0 when convenient.
Data as of 8 Nov 2026, 13:47 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 6.9 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.2 |
- Patch
- Available – fixed in 8.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade openemr to 8.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| openemropenemr | Affected
| Fixed in
|
AI-suggested
Upgrade OpenEMR to version 8.4.0 or later, where this SSRF vulnerability is fixed. No other mitigations are specified or required once the official fix is applied.
Description
OpenEMR versions prior to 8.4.0 contain a server-side request forgery (SSRF) vulnerability. This flaw allows unauthenticated attackers to register an OAuth2 client with an unvalidated jwks_uri, enabling the server to send arbitrary HTTP requests. Attackers can exploit this via the token introspection endpoint using an unsigned client_assertion, potentially probing internal services and cloud metadata endpoints. The vulnerability is fixed in OpenEMR version 8.4.0.