OpenEMR: Arbitrary Patient Recall and Contact Detail Read
- Exploited
- No known exploitation
- Fix
- Fixed in 8.3.0
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 8.3.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
OpenEMR, a free electronic health records and medical practice management application, has a flaw in its recall feature that lets an attacker on the network, with a low-privilege login, read patient details, contact fields, HIPAA notification preferences, recent appointment information, and existing recall records for any patient whose identifier they know or can enumerate. No user action is needed, because the feature does not check whether the requester is authorized to view the patient record they specify.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
OpenEMR is a free and open source electronic health records and medical practice management application. Prior to 8.3.0, the new_recall branch of interface/main/messages/save.php accepts a caller-supplied pid without enforcing patient-level or recall-workflow authorization. A low-privilege authenticated user who knows or enumerates a patient identifier can retrieve patient details, contact fields, HIPAA notification preferences, recent appointment information, and existing recall information. This issue is fixed in version 8.3.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Upgrade to a fixed version: 8.3.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.3.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-104136
Is CVE-2026-104136 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in OpenEMR lets a user read patient recall and contact details for arbitrary patients they should not be able to see. The exposed data includes patient details, HIPAA notification preferences, recent appointment information, and existing recall information.Source: github.com
Which versions are affected by CVE-2026-104136?
openemr: before 8.3.0.Source: cve.now feed data
Am I affected, and how do I check?
The advisory lists OpenEMR versions before 8.3.0 as affected. To check a installation, look at the OpenEMR version shown in the application or in the installed package, and compare it with 8.3.0.Source: github.com
How do I fix CVE-2026-104136?
Upgrade OpenEMR to version 8.3.0 or later, which the advisory names as the patched release.Source: github.com