CVE
OpenEMR unauthorized access to patient records in Carecoordination
Only affects OpenEMR before 8.5.0 for users holding the send_to_hie permission, such as Front Office or care-coordination staff, with the Carecoordination module enabled. Fixed in 8.5.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 8.5.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. OpenEMR before 8.5.0 User holds the send_to_hie permission (Front Office or care-coordination staff, not administrators) Carecoordination module enabled
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.44% · 38th percentile
- 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? →
- 17/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 before 8.5.0 contains an insecure direct object reference vulnerability in the Carecoordination module that allows authenticated users with send_to_hie permission to access any patient's CCDA/CCR/QRDA documents. Attackers can supply arbitrary document or patient IDs to download, transmit, or export patient health records, inject falsified clinical data, and delete audit records.
Who should check
Teams running OpenEMR before 8.5.0 with the Carecoordination module enabled; any user holding send_to_hie (Front Office or care-coordination staff) is in scope.
Read the source excerpt
“OpenEMR before 8.5.0 contains an insecure direct object reference vulnerability in the Carecoordination module”
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
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
OpenEMR before 8.5.0 User holds the send_to_hie permission (Front Office or care-coordination staff, not administrators) Carecoordination module enabledUpgrade to a fixed version: 8.5.0.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126470 (OpenEMR before 8.5.0 IDOR in Carecoordination CCDA/CCR/QRDA Document Actions), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126470 (entry last updated 2026-11-13):
Affected:
- openemr openemr: fixed in 8.5.0
Fixed versions: 8.5.0.
Conditions (all must be true for the bug to be hit):
- OpenEMR before 8.5.0 (source: https://www.vulncheck.com/advisories/openemr-before-8.5.0-idor-in-carecoordination-ccda-ccr-qrda-document-actions)
- User holds the send_to_hie permission (Front Office or care-coordination staff, not administrators) (source: https://github.com/openemr/openemr/security/advisories/GHSA-3vxh-7hh5-vhhm)
- Carecoordination module enabled (source: https://github.com/openemr/openemr/security/advisories/GHSA-3vxh-7hh5-vhhm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-126470 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126470 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/openemr/openemr/security/advisories/GHSA-3vxh-7hh5-vhhm
- https://www.vulncheck.com/advisories/openemr-before-8.5.0-idor-in-carecoordination-ccda-ccr-qrda-document-actions
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126470
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126470"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- openemr openemr
fixed in 8.5.0
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126470
Is CVE-2026-126470 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?
The Carecoordination module fails to check that a user may access the specific document or patient they name, so an authenticated user with the send_to_hie permission can supply arbitrary document or patient IDs. This can allow downloading, transmitting, or exporting patient health records, injecting falsified clinical data, and deleting audit records.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-126470?
openemr: before 8.5.0.Source: cve.now feed data
Am I affected, and how do I check?
Installations of OpenEMR before 8.5.0 with the Carecoordination module enabled are affected, and the exposure is limited to users holding the send_to_hie permission, which is typically Front Office or care-coordination staff rather than administrators. To check, look at the OpenEMR version in the installation's footer or administration information, and check whether the Carecoordination module is enabled and which users hold send_to_hie.Source: vulncheck.com, github.com
How do I fix CVE-2026-126470?
Upgrade OpenEMR to version 8.5.0 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com, github.com