CVE-2026-63194: Bahmni Core file write in admin CSV import

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.

Read the original 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.

Who should check

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

Read the source excerpt

“Should be applied to bahmnicore-omod 0.93 and above”

github.com

cve.now Index

26Pcve.now Index 26 of 100 · methodology v3 · provisional

Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
Reach?/20Unknown. No tracked technology or package matched
Severity8.7/10CVSS 8.7
No patch0/5No signal

What would change the score

Would score about 71 if added to CISA KEV
Would score about 66 if CISA's SSVC rates exploitation active
Would score about 31 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

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: On the ingress-controller or proxy, block or restrict access to /openmrs/ws/rest/v1/bahmnicore/admin/upload/* to trusted IP addresses.

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

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.

Timeline

Nov 11, 2026, 2:34 AM UTCCVE published
Nov 11, 2026, 2:40 AM UTCFirst seen by cve.now

Affected versions

Bahmni bahmni-core
0.93

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · Bahmni/bahmni-core · Advisory GHSA-pmw7-2mfv-4592

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-63194
Record
NVD · CVE-2026-63194

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-63194

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: cve.now feed data

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: github.com

Which versions are affected by CVE-2026-63194?

bahmni-core: version 0.93.Source: cve.now feed data

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: github.com

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: github.com

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