CVE-2026-40076
HighCVSS 8.8Exploitation Probability (EPSS)
Elevated risk58th percentile - higher than 58% of all known CVEs
Summary
In OpenMRS Core versions 2.7.8 and earlier and 2.8.0 through 2.8.5, the module upload endpoint is vulnerable to a Zip Slip path traversal attack. A crafted archive can write files outside the intended module directory, allowing an authenticated attacker to achieve remote code execution by uploading a JSP file.
Risk Assessment
An authenticated attacker with module upload access can write arbitrary files to the web application root and achieve remote code execution, potentially leading to full system compromise.
Recommendation
Upgrade OpenMRS Core to a version after 2.7.8 in the 2.7.x line or to version 2.8.6 or later.
Other vulnerabilities in OpenMRS Core
See all- CVE-2026-41258Critical
In OpenMRS, from version 2.7.0 to before 2.7.9 and 2.8.6, the ConceptReferenceRangeUtility.evaluateCriteria() method evaluates database-stored criteria as Apache Velocity templates without proper sandbox configuration. This allows unrestricted Java reflection through template expressions.
- CVE-2026-40075High
OpenMRS Core up to version 2.7.8 and versions 2.8.0-2.8.5 contain a path traversal vulnerability in the `/openmrs/moduleResources/{moduleid}` endpoint. The getFile() function does not validate the path, allowing an unauthenticated attacker to read arbitrary files, including /etc/passwd and configuration files with database credentials. Exploitation is only possible on Apache Tomcat versions prior to 8.5.31.
Original NVD description (English source)
OpenMRS Core is an open source electronic medical record system platform. In versions 2.7.8 and earlier and versions 2.8.0 through 2.8.5, the module upload endpoint at POST `/openmrs/ws/rest/v1/module` is vulnerable to a Zip Slip path traversal attack. During automatic extraction of uploaded .omod archives in `WebModuleUtil.startModule()`, ZIP entries under web/module/ are checked only to see whether the full entry path starts with `..,` and the remaining path is then concatenated into the destination path without normalization or a boundary check. A crafted archive can therefore include entries such as `web/module/../../../../malicious.jsp` and cause files to be written outside the intended module directory. An authenticated attacker with module upload access can write arbitrary files to locations such as the web application root and achieve remote code execution by uploading a JSP file and then requesting it. The issue is compounded by the fact that the module.allow_web_admin runtime property is enforced in the legacy UI controller but not in the REST API upload path, so deployments relying on that property to block web-based module administration remain exposed through the REST endpoint. This issue has been fixed in versions after 2.7.8 in the 2.7.x line and in version 2.8.6 and later.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS