CVE-2026-67611
OAuth2 client registration allows MFA bypass and API token issuance in OpenEMR.
Is CVE-2026-67611 being exploited?
Not confirmed. CVE-2026-67611 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.53% probability of exploitation in the next 30 days.
How severe is CVE-2026-67611?
CVE-2026-67611 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-67611?
Yes. A fix has been recorded for CVE-2026-67611. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67611 affect?
CVE-2026-67611 affects OpenEMR <= 8.2.0, OpenEMR OAuth2 API endpoints. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67611?
Apply vendor patch when available; disable OAuth2 password grant and unauthenticated client registration; restrict access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can register an OAuth2 client via unauthenticated endpoint, use password grant to obtain API tokens, bypass MFA and access patient data/APIs.
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.