CVE-2026-67610
OAuth2 dynamic registration flaw allows system-wide FHIR read access via malicious client
Is CVE-2026-67610 being exploited?
Not confirmed. CVE-2026-67610 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-67610?
CVE-2026-67610 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67610?
Not known from our data. No patch reference has been recorded for CVE-2026-67610, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-67610 affect?
CVE-2026-67610 affects OpenEMR <= 8.2.0, OpenEMR OAuth2 dynamic client registration endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67610?
Disable dynamic client registration, revoke suspicious clients, enforce strict admin review, apply vendor patch when available
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can register a malicious OAuth2 client and, after admin approval, obtain tokens to read all FHIR patient records across the system.
Immediate action required
- affected<= 8.2.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.