CVE-2026-126494: openemr · Incorrect Authorization
Affects openemrSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 8.4.0 soon.
Data as of 13 Nov 2026, 10:42 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 7.1 |
|---|---|---|
| CNA (VulnCheck) | CVSS 3.1 | 7.1 |
- Patch
- Available – fixed in 8.4.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 13 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 13 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 improper authorization vulnerability has been fixed. No other mitigations are specified or required beyond applying the official patch.
Description
OpenEMR versions prior to 8.4.0 have an improper authorization vulnerability in the ScopeRepository::finalizeScopes() function. This flaw allows read-only SMART/OAuth clients to escalate privileges and obtain write scopes. Specifically, clients registered with user/<resource>.read permissions can request user/<resource>.write scopes, enabling them to create, update, or delete appointments and patient data. The issue arises because ScopeEntity::containsScope() does not properly enforce registered permissions. This vulnerability has a high severity rating and was fixed in OpenEMR version 8.4.0.