{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25135 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-25135 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25135 is a medium-severity vulnerability in Open-Emr Openemr, published on 25 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-25135 and fix it if it is affected.\n\nWhat it is: CVE-2026-25135 is a medium-severity vulnerability in Open-Emr Openemr, published on 25 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-25135 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-25135/ (Markdown: https://insights.sbomify.com/CVE-2026-25135/index.md)","id":"CVE-2026-25135","markdown":"https://insights.sbomify.com/CVE-2026-25135/index.md","name":"CVE-2026-25135","record":{"aliases":["GHSA-fgxg-wg4w-rj23"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenEMR EHR system","requires_auth":"high_privilege","summary":"Attackers with specific high-trust API scopes can access all patient and user contact information in OpenEMR.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"openemr","vendor":"open-emr"}],"cvss":{"score":4.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"OpenEMR is a free and open source electronic health records and medical practice management application. Versions prior to 8.0.0 have an information disclosure vulnerability that leaks the entire contact information for all users, organizations, and patients in the system to anyone who has the system/(Group,Patient,*).$export operation and system/Location.read capabilities.  This vulnerability will impact OpenEMR versions since 2023. This disclosure will only occur in extremely high trust environments as it requires using a confidential client with secure key exchange that requires an administrator to enable and grant permission before the app can even be used. This will typically only occur in server-server communication across trusted clients that already have established legal agreements. Version 8.0.0 contains a patch. As a workaround, disable clients that have the vulnerable scopes and only allow clients that do not have the system/Location.read scope until a fix has been deployed.","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's location resource for Group.$export operation returns entire patient/user population contact information","id":"CVE-2026-25135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"open-emr:openemr","products":["open-emr:openemr"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Rucio WebUI has a Reflected Cross-site Scripting Vulnerability","id":"CVE-2026-25136"},"packages":[],"prev":{"headline":"Group-Office Argument Injection in MaintenanceController::actionZipLanguage","id":"CVE-2026-25134"},"products":["openemr"],"published":"2026-02-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":"partial"},"state":"PUBLISHED","updated":"2026-02-25","vendors":["openemr"]},"summary":"Attackers with specific high-trust API scopes can access all patient and user contact information in OpenEMR.","url":"https://insights.sbomify.com/CVE-2026-25135/"}