CVSS 4.0
7.1 highCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NCVE-2026-104136 open-emr openemr: Improper Access Control
High (7.1) in open-emr openemr. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
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.
Severity
CVSS 3.1
6.5 mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N- EPSS
- 0.4% (unchanged from 0.3% a week ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CISA's assessment (SSVC)
- Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
- CWE
- CWE-284 Improper Access Control
- OWASP Top 10
- A01:2025 Broken Access Control
- Published
- Modified
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-104136 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104136?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104136?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104136 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-104136)
HTML:
<a href="https://cve.bz/cve/CVE-2026-104136"><img src="https://cve.bz/cve/badge/CVE-2026-104136.svg" alt="CVE-2026-104136"></a>
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| open-emr:openemr | before 8.3.0 |
Fix and patched versions
- Patch: https://github.com/openemr/openemr/commit/12fb549fd16ceed488c9d20281dba46f098ff107
- Patch: https://github.com/openemr/openemr/pull/13343
- Vendor advisory: https://github.com/openemr/openemr/security/advisories/GHSA-x6w3-3g4m-5m5v
Attack patterns (CAPEC)
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).
History
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.