On this page (6 sections)

A critical vulnerability, CVE-2026-124445, has been published for OpenEMR, the open source electronic health records and practice management system. According to the NVD record, the one-time authentication code in OpenEMR from 7.0.1 before 8.4.0 does not enforce its own limits, so a captured token can be reused and a login PIN can be guessed without restriction.

If you host or administer an OpenEMR instance with the patient portal enabled, this one is worth acting on quickly, because the portal exposes protected health information (PHI). At the time of writing, only the NVD record and the advisories it references describe the issue, so some details below are marked as unconfirmed.

What happened

The flaw sits in src/Common/Auth/OneTimeAuth.php. Per the NVD description, this code ignores the enforce_onetime_use and max_access_count flags, never revokes service_auth tokens after they have been consumed, and checks login_pin without rate limiting or strict comparison.

The stated impact is that an attacker who already holds a captured token can replay it, or brute-force the PIN, to open patient-portal sessions that expose PHI. The record references a GitHub advisory, a project advisory on the OpenEMR repository and a VulnCheck advisory. The research available to us contains only the NVD text, so we cannot add detail beyond it, and we have not seen the vendor's release notes or a statement of the exact fixed release.

The weakness in plain terms

One-time links and PINs are meant to work like a single-use ticket: valid once, for a limited number of tries, then dead. This code has three gaps that undo that idea:

  • Single-use is not enforced. The flags that say a token should work only once, or only a set number of times, are ignored.
  • Used tokens stay valid. Consumed service_auth tokens are never revoked, so an old token that leaks (from a log, an email, a browser history or a proxy) keeps working.
  • The PIN can be guessed. The login_pin check has no rate limiting and no strict comparison, so repeated guesses are not slowed down, and the comparison itself is loose. The NVD text does not say what the loose comparison allows, so we do not speculate.

The attacker needs a captured token to start with. That makes it less severe than a fully unauthenticated flaw would be, but tokens do leak in practice, and what sits behind the portal is sensitive health data.

Who is affected

Any OpenEMR installation running a version from 7.0.1 up to but not including 8.4.0. Clinics, small practices, hosting providers and agencies that run OpenEMR for clients are all in scope. Risk is likely highest where the patient portal is reachable from the internet, since that is where portal sessions are opened.

The research does not say whether the issue is being exploited, and it is not listed in CISA's Known Exploited Vulnerabilities catalog. Treat the absence of reports as unknown, not as safe.

How to check your exposure

First find out which OpenEMR version you run. Check your deployment records, your package manager or container image tags, or the project's documentation for how to read the installed version. If you deployed from a git checkout, this read-only command, run from the OpenEMR directory on the server, shows the current tag or commit:

Show the checked-out release or commit of an OpenEMR git install (run in the OpenEMR directory)Shell
git describe --tags --always

If the result is 7.0.1 or later but earlier than 8.4.0, you are in the affected range. You can also confirm the file named in the NVD description is present. This read-only command, run in the OpenEMR directory, prints a listing if the file exists:

Check that the affected file exists (run in the OpenEMR directory)Shell
ls -l src/Common/Auth/OneTimeAuth.php

Presence of the file alone does not prove you are vulnerable. The version is what decides it.

What to do now

  1. Identify every OpenEMR instance you run or manage, including staging and demo copies, and note each version.
  2. Back up the database and the OpenEMR files before changing anything, and test that the backup restores.
  3. Upgrade to OpenEMR 8.4.0 or later, which is outside the affected range in the NVD record, following the project's upgrade documentation. Check the project advisory for the vendor's own fix statement, which we have not seen.
  4. If you cannot upgrade immediately, consider restricting access to the patient portal (VPN, IP allowlist or temporarily disabling it) until you can. This is a general risk-reduction step, not a fix named in the advisory.
  5. Review access logs for repeated portal login or PIN attempts from a single address, and for the same one-time link being used many times.
  6. Because consumed tokens are never revoked in affected versions, treat outstanding one-time links and portal tokens as potentially exposed and reissue them after the upgrade, particularly if you suspect any leaked.
  7. If you find suspicious portal sessions, ask your compliance contact whether breach-notification obligations apply to you.
Caution. Upgrading an electronic health records system can interrupt clinical workflows and, if done wrongly, damage data. Schedule a maintenance window, take a verified backup first and test on a copy where you can.

Detection and monitoring

Because the PIN check has no rate limiting in affected versions, guessing attempts would show up as many requests to the portal login in a short time. If your web server writes Apache-style access logs, this read-only search, run on the server, lists the client addresses with the most requests to portal paths. Adjust the log path to your setup and look for a few addresses with unusually high counts:

Count requests per client IP to portal URLs in an Apache-style access log (adjust the path)Shell
grep -i portal /var/log/apache2/access.log | awk '{print $1}' | sort | uniq -c | sort -rn | head -20

Beyond the logs, put a rate limit or web application firewall rule in front of the portal login as defense in depth (see what a WAF is), keep the portal on HTTPS only, and watch certificate and DNS changes on the portal hostname with monitoring. None of this replaces the upgrade. For broader guidance, see our small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-124445: OpenEMR from 7.0.1 before 8.4.0 contains a flaw in src/Common/Auth/OneTimeAuth.php that ignores the enforce_onetime_use and max_access_count flags, never…nvd.nist.gov ·
  • OpenEMR
  • CVE-2026-124445
  • healthcare security
  • authentication
  • patient portal