Loading...
Skip to main content

CVE-2026-41258 — Vulnerability in org.openmrs.api:openmrs-api —...

CRITICAL

OpenMRS has Stored Velocity SSTI to RCE via ConceptReferenceRange

Published May 4, 2026Updated May 16, 2026Source: osv

Summary

### Impact The `ConceptReferenceRangeUtility.evaluateCriteria()` method in OpenMRS Core evaluates database-stored criteria strings as Apache Velocity templates without any sandbox configuration. The `VelocityEngine` is initialized with only logging properties and no`SecureUberspector`, leaving the default `UberspectImpl` in place, which allows unrestricted Java reflection through template expressions. A user with the `Manage Concepts` privilege can store a malicious Velocity template expression in a concept's reference range criteria field. This payload is then executed automatically whenever a user or API call validates an observation against the affected concept. The Velocity context exposes `$patient` (the `Person` / `Patient` object), `$obs` (the `Obs` object), and `$fn` (the `ConceptReferenceRangeUtility` instance with access to the full OpenMRS service layer). **Persistent Remote Code Execution**: The payload persists in the concept_reference_range database table (VARCHAR 65535). A single compromised concept for a common clinical measurement executes the payload on every subsequent observation validation across all users, API clients, and integrations in the facility. **Privilege Escalation**: The Manage Concepts privilege is a content-management function, defined as "Able to add/edit/delete concept entries", not an administrative privilege. Multiple non-admin staff per facility typically hold this privilege. The attacker escalates from concept dictionary management to arbitrary code execution as the Tomcat application server process. **PHI Exfiltration**: The Velocity context objects directly expose patient data without requiring OS-level RCE. ### Patches This is fixed in 2.8.6 and 2.7.9 as well as future versions. ### Workarounds Ensure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database. ### Resources https://github.com/openmrs/openmrs-core/commit/8d1c193 https://www.machinespirits.com/advisory/1e8430/

Advisory Timeline

  • First published May 4, 2026 (161 days ago).
  • Last revised May 16, 2026 — 11 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.openmrs.api:openmrs-api to 2.8.6 or later
<!-- Update pom.xml dependency version to 2.8.6 for org.openmrs.api:openmrs-api -->
Maven
Update org.openmrs.api:openmrs-api to 2.7.9 or later
<!-- Update pom.xml dependency version to 2.7.9 for org.openmrs.api:openmrs-api -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (2)

Affects 1 ecosystem: maven (1).

PackageEcosystemAffectedFixed In
org.openmrs.api:openmrs-api
maven
All versions2.8.6
org.openmrs.api:openmrs-api
maven
All versions2.7.9

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 9.1 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Frequently Asked Questions

What is CVE-2026-41258?
OpenMRS has Stored Velocity SSTI to RCE via ConceptReferenceRange This vulnerability has been assigned a severity rating of CRITICAL (CVSS score: 9.1/10).
How do I check if my project is affected by CVE-2026-41258?
CVE-2026-41258 affects org.openmrs.api:openmrs-api. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-41258 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
9.1

Exploitation is straightforward and causes maximum impact. Patch immediately.

Also Known As

GHSA-xj4f-8jjg-vx4q

Related CVEs

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies