{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34055 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34055 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34055 is a high-severity missing authorization vulnerability in Open-Emr Openemr, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34055 and fix it if it is affected.\n\nWhat it is: CVE-2026-34055 is a high-severity missing authorization vulnerability in Open-Emr Openemr, published on 25 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34055 in the wild and no public exploit code.\n\nAffected product: Open-Emr Openemr. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-34055/ (Markdown: https://insights.sbomify.com/CVE-2026-34055/index.md)","id":"CVE-2026-34055","markdown":"https://insights.sbomify.com/CVE-2026-34055/index.md","name":"CVE-2026-34055","record":{"aliases":["GHSA-8gj5-r8vm-mghq"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenEMR EHR","requires_auth":"low_privilege","summary":"Attackers can access or modify patient notes belonging to other patients by manipulating note IDs in the web UI due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openemr","vendor":"open-emr"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"OpenEMR has IDOR in Patient Notes Web UI allows unauthorized note access/modification","id":"CVE-2026-34055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"open-emr:openemr","products":["open-emr:openemr"],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenEMR has a Privilege Escalation that Allows a Low-Level User to View Admin-Only Data","id":"CVE-2026-34056"},"packages":[],"prev":{"headline":"openssl on Windows built with openssldir set from the build machine (Uncontrolled Search Path Element)","id":"CVE-2026-34054"},"products":["openemr"],"published":"2026-03-25","related":[{"cvss_score":10,"headline":"OpenEMR has an Unauthenticated MedEx Token Disclosure","id":"CVE-2026-24898","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":10,"headline":"OpenEMR Arbitrary File Read Vulnerability","id":"CVE-2026-24849","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":10,"headline":"OpenEMR has SQL Injection in Patient API Sort Parameter","id":"CVE-2026-24908","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":10,"headline":"Improper Restriction of Rendered UI Layers or Frames in openemr/openemr","id":"CVE-2022-2734","kev_date_added":null,"published":"2022-08-09"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-22611","kev_date_added":null,"published":"2025-04-03"},{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-37734","kev_date_added":null,"published":"2024-06-26"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2019-17197","kev_date_added":null,"published":"2019-10-05"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["openemr"]},"summary":"Attackers can access or modify patient notes belonging to other patients by manipulating note IDs in the web UI due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2026-34055/"}