OAuth2 grant type enforcement bypass in OpenEMR
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA. Impact type from CWE-862.
Summary
OpenEMR before 8.5.0 does not enforce the grant types registered for OAuth2 clients, so clients can use grant types they were never registered for. Missing authorization checks let a remote attacker request tokens with grant_type=password to bypass the user consent screen. Disabled clients can also redeem authorization codes by presenting JWT client assertions. The flaw is tracked as CWE-862 and needs no privileges or user interaction.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
Description from the CNA
OpenEMR before 8.5.0 contains an authorization bypass vulnerability that allows OAuth2 clients to use unregistered grant types because oauth_clients.grant_types is never enforced. Attackers can request tokens with grant_type=password to bypass the user consent screen, and disabled clients can redeem authorization codes using JWT client assertions.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- 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
Remediation
Upgrade OpenEMR to version 8.5.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-13
- Fix · CNA openemr (openemr) Fixed in 8.5.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
openemr 8.5.0
77 records Highest priority Priority HIGH 4 HIGH, 16 MEDIUM, 57 LOW
Other records, highest priority first
- TI-2026-91361 Missing authorization in OpenEMR custom export and chart-tracker scriptsPriority HIGH 73
- TI-2026-91381 Second-order SQL injection in OpenEMR IPPF contraceptive issue featurePriority HIGH 72
- TI-2026-91321 Unrestricted file upload in OpenEMR lets billing users execute PHPPriority HIGH 69
Timeline
- 2026-11-13 Threatist record created from CVE-2026-126436
- 2026-11-13 Alias added: GHSA-h6wr-v3m9-4h99
- 2026-11-13 CISA SSVC decision points changed
References
More openemr vulnerabilities
- 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
Sources
- CVE-2026-126436 · CVE Program
- CVE-2026-126436 · NVD
- FIRST EPSS
- GHSA-h6wr-v3m9-4h99 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences