Home › Vulnerabilities

OpenEMR Project OpenEMR electronic health records platform Flaw CVE-2026-102940: Update Now

Published November 6, 2026 · Last updated November 6, 2026

CVE Critical Patch

The short version: CVE-2026-102940 is a critical-severity security flaw in OpenEMR Project OpenEMR electronic health records platform. The National Vulnerability Database (NVD) published it on November 5, 2026, and the score it lists is 9.6 out of 10. When FraudMeNot checked on November 6, 2026, CISA had not added CVE-2026-102940 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

What the official record says about CVE-2026-102940

The record was filed by github.com. In its own words: "OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.4.0, controllers/C_Document.class.php write actions, including move_action_process(), do not verify the caller's access to the source document, current patient and category, or destination patient and category before Document::change_patient() performs the mutation. A low-privilege authenticated user can reassign an arbitrary document to a patient or category the user can access and then retrieve it through the normally protected read path. The reassignment occurs before a later list rendering check, so a final HTTP 403 response does not mean the unauthorized write was blocked. This issue is fixed in version 8.4.0."

Why OpenEMR electronic health records platform admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on github.com rated CVE-2026-102940 9.6 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker needs a low-privilege account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping OpenEMR electronic health records platform running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N.

Affected OpenEMR electronic health records platform releases

According to the record, these releases are vulnerable:

  • version < 8.4.0

The type of bug behind CVE-2026-102940

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-639, Authorization Bypass Through User-Controlled Key. MITRE describes this class of bug as follows: "The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data."

Vendor remediation for CVE-2026-102940

The vendor advisory remediation for operators of OpenEMR electronic health records platform, quoted for this page, is: "Upgrade every OpenEMR clinic and hospital install to 8.4.0 or newer; 8.4.1 and 8.5.0 also contain the repair. GHSA-92rh-g949-4mvv explains that controller.php document write actions such as move_action_process never verified the caller's relationship to the source document, current patient, category, or destination patient before Document::change_patient ran, so any authenticated role could reassign an arbitrary chart document into a patient folder they already could read and then pull it through the protected retrieve_action path. Apply the vendor release notes for v8_4_0 and confirm the document controller ACL checks are present after upgrade."

What to do about it

  • Update now: Upgrade every OpenEMR clinic and hospital install to 8.4.0 or newer; 8.4.1 and 8.5.0 also contain the repair. GHSA-92rh-g949-4mvv explains that controller.php document write actions such as move_action_process never verified the caller's relationship to the source document, current patient, category, or destination patient before Document::change_patient ran, so any authenticated role could reassign an arbitrary chart document into a patient folder they already could read and then pull it through the protected retrieve_action path. Apply the vendor release notes for v8_4_0 and confirm the document controller ACL checks are present after upgrade.
  • Who should act: IT teams, managed service providers, and developers who run or ship OpenEMR electronic health records platform. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from OpenEMR Project (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 5, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-102940. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-102940 record details from CISA and NVD

  • Attack complexity for CVE-2026-102940: low
  • CVE-2026-102940 CVSS scope: changed
  • NVD sub-scores for CVE-2026-102940: exploitability 3.1, impact 5.8.
  • Who mapped the weakness type: the address listed on github.com (Secondary)
  • References in the NVD record: 5.
  • CISA SSVC decision points for CVE-2026-102940 (from NVD): exploitation=poc; automatable=no; technicalImpact=total (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • November 5, 2026: NVD publishes CVE-2026-102940.
  • November 6, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-102940 is not listed.
  • November 6, 2026: most recent NVD update (record status: Awaiting Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.