{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67611 exists.","fix":"No fix has been published for CVE-2026-67611 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67611 is a high-severity authentication bypass vulnerability in Open-Emr Openemr, published on 3 Aug 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-67611 and fix it if it is affected.\n\nWhat it is: CVE-2026-67611 is a high-severity authentication bypass vulnerability in Open-Emr Openemr, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67611 exists.\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-67611/ (Markdown: https://insights.sbomify.com/CVE-2026-67611/index.md)","id":"CVE-2026-67611","markdown":"https://insights.sbomify.com/CVE-2026-67611/index.md","name":"CVE-2026-67611","record":{"aliases":["GHSA-g6r6-jr7g-hg95"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenEMR medical software","requires_auth":"low_privilege","summary":"Attackers with valid credentials can bypass multi-factor authentication by exploiting an exposed OAuth2 password grant flow in OpenEMR.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"openemr","vendor":"open-emr"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-308","name":"Use of Single-factor Authentication"}],"description":"OpenEMR through 8.2.0 contains an authentication bypass vulnerability that allows attackers with valid credentials to circumvent multi-factor authentication by exploiting the exposed OAuth2 password grant flow through an unauthenticated client registration endpoint. Attackers can register an OAuth2 client via the unauthenticated registration endpoint and use the password grant to exchange credentials for an API access token, bypassing the normal web interface authentication and any enforced multi-factor authentication controls.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"OpenEMR 8.2.0 OAuth2 Password Grant Authentication Bypass via SMART Configuration","id":"CVE-2026-67611","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"open-emr:openemr","products":["open-emr:openemr"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenEMR 8.2.0 Stored XSS via import_template.php Template Management","id":"CVE-2026-67612"},"packages":[],"prev":{"headline":"OpenEMR 8.2.0 OAuth2 Dynamic Client Registration Unauthorized FHIR Access","id":"CVE-2026-67610"},"products":["openemr"],"published":"2026-08-03","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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-14","vendors":["openemr"]},"summary":"Attackers with valid credentials can bypass multi-factor authentication by exploiting an exposed OAuth2 password grant flow in OpenEMR.","url":"https://insights.sbomify.com/CVE-2026-67611/"}