Bahmni-Core: Exfiltration of patient data stored in Bahmni through SQL injection through boolean blind and error based exfil
Affects Bahmni-Core installations that use the High Risk Patients SQL search query, where the global property emrapi.sqlSearch.highRiskPatients is set. Fixed in 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1 and 2.0.1.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, and 1 more
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The "High Risk Patients" SQL search query is in use (global property emrapi.sqlSearch.highRiskPatients set)
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Bahmni-Core, the OpenMRS core modules used by Bahmni, contains a SQL injection flaw that lets an attacker with a low-privilege login read sensitive data from the database, including patient records. The flaw can be reached remotely over the network, and the attacker needs to be logged in first.
Read the original description
OpenMRS module bahmnicore contains Core OpenMRS modules for Bahmni (including ERP & ELIS Atom Feed Clients). In version 0.93, an attacker with authenticated access could potentially exfiltrate sensitive data from the database. This issue has been patched in version 0.93.1.
Who should check
Teams running Bahmni bahmni-core 0.93 or later that use the High Risk Patients SQL search query
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
The "High Risk Patients" SQL search query is in use (global property emrapi.sqlSearch.highRiskPatients set)Upgrade to a fixed version: 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or one of 1 more.
Workaround: Remove the global property emrapi.sqlSearch.highRiskPatients if the High Risk Patients search query is not used
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-63192 (Bahmni-Core: Exfiltration of patient data stored in Bahmni through SQL injection through boolean blind and error based exfil), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-63192 (entry last updated 2026-11-11): Affected: - Bahmni bahmni-core: versions 0.93 Fixed versions: 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, 2.0.1. Conditions (all must be true for the bug to be hit): - The "High Risk Patients" SQL search query is in use (global property emrapi.sqlSearch.highRiskPatients set) (source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5) Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. Attacker needs: network access, low-privilege login, no user action. Workaround: Remove the global property emrapi.sqlSearch.highRiskPatients if the High Risk Patients search query is not used (source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5) CISA KEV: CVE-2026-63192 is not listed as of cve.now's last read. This KEV status is for CVE-2026-63192 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-63192 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-63192.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- Bahmni bahmni-core
0.93
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-63192
Is CVE-2026-63192 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The SQL search query accepts crafted input that changes the database query it runs, so a request can read sensitive patient data from the Bahmni database. The advisory describes this using boolean blind and error-based techniques.Source: github.com
Which versions are affected by CVE-2026-63192?
bahmni-core: version 0.93.Source: cve.now feed data
Am I affected, and how do I check?
The issue applies to Bahmni-Core installations where the High Risk Patients SQL search query is in use, which is when the global property emrapi.sqlSearch.highRiskPatients is set. Check for that global property in the Bahmni configuration to see whether the query is in use.Source: github.com
How do I fix CVE-2026-63192?
Upgrade bahmni-core to 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1 or 2.0.1, whichever matches the release line in use. If the High Risk Patients search query is not used, removing the global property emrapi.sqlSearch.highRiskPatients is a workaround.Source: github.com