How severe is CVE-2026-34055?

CVE-2026-34055 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-34055 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-34055?

CVE-2026-34055 affects Open-emr Openemr. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-34055?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-34055 have an EU (EUVD) identifier?

Yes. CVE-2026-34055 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-16048.

When was CVE-2026-34055 published?

CVE-2026-34055 was published on 2026-03-26 and last updated on 2026-06-17.

CVE-2026-34055

CVE-2026-34055 is a high-severity vulnerability in Open-emr Openemr with a CVSS 3.x base score of 8.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: High (CVSS 3.x base score 8.1)
EPSS exploit prediction: 0% (19th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-16048
Weakness: CWE-639
Affected product: Open-emr Openemr
Published: 2026-03-26
Last modified: 2026-06-17

Description

OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, the legacy patient notes functions in `library/pnotes.inc.php` perform updates and deletes using `WHERE id = ?` without verifying that the note belongs to a patient the user is authorized to access. Multiple web UI callers pass user-controlled note IDs directly to these functions. This is the same class of vulnerability as CVE-2026-25745 (REST API IDOR), but affects the web UI code paths. Version 8.0.0.3 patches the issue.

Frequently asked questions

What is CVE-2026-34055?: OpenEMR is a free and open source electronic health records and medical practice management application. Prior to version 8.0.0.3, the legacy patient notes functions in `library/pnotes.inc.php` perform updates and deletes using `WHERE id = ?` without verifying that the note belongs to a patient the user is authorized to access. Multiple web UI callers pass user-controlled note IDs directly to these functions. This is the same class of vulnerability as CVE-2026-25745 (REST API IDOR), but affects the web UI code paths. Version 8.0.0.3 patches the issue.
How severe is CVE-2026-34055?: CVE-2026-34055 has a CVSS 3.x base score of 8.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-34055 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (19th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-34055?: CVE-2026-34055 affects Open-emr Openemr. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-34055?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-34055 have an EU (EUVD) identifier?: Yes. CVE-2026-34055 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-16048.
When was CVE-2026-34055 published?: CVE-2026-34055 was published on 2026-03-26 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:open-emr:openemr:*:*:*:*:*:*:*:*

More vulnerabilities in Open-emr Openemr

CVE-2026-24898 — Critical (CVSS 10.0): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
CVE-2026-24848 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. In 7.0.4 and…
CVE-2026-24908 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
CVE-2026-24849 — Critical (CVSS 9.9): OpenEMR is a free and open source electronic health records and medical practice management application. Prior to…
CVE-2024-22611 — Critical (CVSS 9.8): OpenEMR 7.0.2 is vulnerable to SQL Injection via \openemr\library\classes\Pharmacy.class.php,…
CVE-2024-37734 — Critical (CVSS 9.8): An issue in OpenEMR 7.0.2 allows a remote attacker to escalate privileges viaa crafted POST request using the noteid…

All CVEs affecting Open-emr Openemr →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-62283 — Critical (CVSS 9.9): Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&M tool. Nezha versions 1.14.13…
CVE-2026-73656 — Critical (CVSS 9.9): Trigger.dev is a platform for building and deploying fully managed AI agents and workflows. Prior to 4.5.6, POST…
CVE-2026-48765 — Critical (CVSS 9.9): TypeBot is a chatbot builder tool. Versions prior to 3.17.0 allow a low-privilege read collaborator to extract a…
CVE-2026-67622 — Critical (CVSS 9.9): Flowise through 3.1.4 contains an insecure direct object reference vulnerability in the OpenAI Assistants integration…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →