CVE-2026-41258: Openmrs api Remote Code Execution Vulnerability

CRITICAL
Advisory Identifier: GHSA-xj4f-8jjg-vx4q
CVSS 9.1
CWE-94
Published
Advisory Summary

CVE-2026-41258 is a CRITICAL (CVSS 9.1) remote code execution vulnerability (CWE-94: Improper Control of Generation of Code ('Code Injection')) affecting Openmrs api libraries in the Maven ecosystem. The issue involves openmrs has stored velocity ssti to rce via conceptreferencerange. Remediation is available by upgrading affected packages to version 2.7.9, 2.8.6.

CVE-2026-41258 at a Glance

CVE Identifier CVE-2026-41258
GHSA Identifier GHSA-xj4f-8jjg-vx4q
Severity CRITICAL
CVSS v3.1 Base Score 9.1
CWE Classification CWE-94: Improper Control of Generation of Code ('Code Injection')
Affected Product Openmrs api
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 9.1

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required High (PR:H)
User Interaction None (UI:N)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2026-41258

To remediate this vulnerability, upgrade all affected Openmrs api dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

org.openmrs.api:openmrs-api fixed: 2.7.9
<dependency>
    <groupId>org.openmrs.api</groupId>
    <artifactId>openmrs-api</artifactId>
    <version>2.7.9</version>
</dependency>
org.openmrs.api:openmrs-api fixed: 2.8.6
<dependency>
    <groupId>org.openmrs.api</groupId>
    <artifactId>openmrs-api</artifactId>
    <version>2.8.6</version>
</dependency>
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree -Dincludes=org.openmrs.api

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-41258, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree -Dincludes=org.openmrs.api

Analyze the terminal output to locate any version of Openmrs api in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.7.9), your application is affected.

Note: The mvn dependency:tree -Dincludes=org.openmrs.api command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-94: Improper Control of Generation of Code ('Code Injection'), where the product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. In Openmrs api, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

CVE-2026-41258 Affected Openmrs api Versions

2 component(s)
Fixed Versions:
2.7.92.8.6
Product / Package Ecosystem Affected Versions Fixed Version
org.openmrs.api:openmrs-api
Maven
≥ 2.7.0
< 2.7.9
2.7.9
org.openmrs.api:openmrs-api
Maven
≥ 2.8.0
< 2.8.6
2.8.6

References

Frequently Asked Questions

What is CVE-2026-41258?
CVE-2026-41258 is a security vulnerability in Openmrs api involving OpenMRS has Stored Velocity SSTI to RCE via ConceptReferenceRange under CWE-94: Improper Control of Generation of Code ('Code Injection').
Which Openmrs api versions are affected?
Affected versions include releases prior to 2.7.9, 2.8.6 across affected packages: org.openmrs.api:openmrs-api.
What version fixes CVE-2026-41258?
Upgrading to 2.7.9, 2.8.6 (or the latest patched release for your respective branch) resolves the vulnerability.
Is openmrs-api affected?
Yes, org.openmrs.api:openmrs-api is affected in releases prior to 2.7.9, 2.8.6. Upgrade your dependency to 2.7.9, 2.8.6 or later.
What is the CVSS score of CVE-2026-41258?
CVE-2026-41258 has a CVSS v3.1 base score of 9.1 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2026-41258?
CVE-2026-41258 is classified under CWE-94: Improper Control of Generation of Code ('Code Injection') (The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.).
How can I check Maven dependencies for CVE-2026-41258?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=org.openmrs.api'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-xj4f-8jjg-vx4q",
  "modified" : "2026-05-15T23:48:35Z",
  "published" : "2026-05-04T19:31:22Z",
  "aliases" : [ "CVE-2026-41258" ],
  "summary" : "OpenMRS has Stored Velocity SSTI to RCE via ConceptReferenceRange",
  "details" : "### Impact\n\nThe `ConceptReferenceRangeUtility.evaluateCriteria()` method in OpenMRS Core\nevaluates 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\nunrestricted Java reflection through template expressions.\n\nA user with the `Manage Concepts` privilege can store a malicious Velocity template\nexpression in a concept's reference range criteria field. This payload is then executed\nautomatically whenever a user or API call validates an observation against the affected\nconcept. 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).\n\n**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.\n\n**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.\n\n**PHI Exfiltration**: The Velocity context objects directly expose patient data without requiring OS-level RCE.\n\n### Patches\n\nThis is fixed in 2.8.6 and 2.7.9 as well as future versions.\n\n### Workarounds\n\nEnsure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database.\n\n### Resources\nhttps://github.com/openmrs/openmrs-core/commit/8d1c193\nhttps://www.machinespirits.com/advisory/1e8430/",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openmrs.api:openmrs-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.7.0"
      }, {
        "fixed" : "2.7.9"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Maven",
      "name" : "org.openmrs.api:openmrs-api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.8.0"
      }, {
        "fixed" : "2.8.6"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/openmrs/openmrs-core/security/advisories/GHSA-xj4f-8jjg-vx4q"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41258"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/openmrs/openmrs-core/commit/8d1c193"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/openmrs/openmrs-core"
  }, {
    "type" : "WEB",
    "url" : "https://www.machinespirits.com/advisory/1e8430"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-94" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-04T19:31:22Z",
    "nvd_published_at" : "2026-05-15T17:16:46Z"
  }
}