{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67610 exists.","fix":"No fix has been published for CVE-2026-67610 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67610 is a high-severity authentication bypass vulnerability in openemr, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-67610 and fix it if it is affected.\n\nWhat it is: CVE-2026-67610 is a high-severity authentication bypass vulnerability in openemr, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67610 exists.\n\nAffected product: 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-67610/ (Markdown: https://insights.sbomify.com/CVE-2026-67610/index.md)","id":"CVE-2026-67610","markdown":"https://insights.sbomify.com/CVE-2026-67610/index.md","name":"CVE-2026-67610","record":{"aliases":["GHSA-7h45-2j8g-37rm"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenEMR EHR system","requires_auth":"none","summary":"Unauthenticated attackers can register malicious OAuth2 clients to gain unauthorized read access to all patient FHIR data in OpenEMR.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"OpenEMR through 8.2.0 contains an improper authentication vulnerability in the OAuth2 dynamic client registration endpoint that allows unauthenticated attackers to register a malicious client with system-level FHIR scopes by supplying a self-generated RSA keypair via the jwks field. Once an administrator approves the registered client, attackers can use the client_credentials grant with a self-signed JWT assertion to obtain access tokens granting read access to all FHIR resources across all patients in the system.","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 Dynamic Client Registration Unauthorized FHIR Access","id":"CVE-2026-67610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenEMR 8.2.0 OAuth2 Password Grant Authentication Bypass via SMART Configuration","id":"CVE-2026-67611"},"packages":[],"prev":{"headline":"Telenia TVox 26.5.3 Privilege Escalation via Insecure sudoers Configuration","id":"CVE-2026-67609"},"products":["openemr"],"published":"2026-08-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"Unauthenticated attackers can register malicious OAuth2 clients to gain unauthorized read access to all patient FHIR data in OpenEMR.","url":"https://insights.sbomify.com/CVE-2026-67610/"}