Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-41258 critical CVSS 9.1

Code Injection in org.openmrs.api:openmrs-api (CVE-2026-41258)

Summary

code injection in org.openmrs.api:openmrs-api (CVE-2026-41258). Successful exploitation can lead to full system takeover. Exploitable via ``VelocityEngine``. Mitigation: upgrade to `2.8.6` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-41258** has been found in org.openmrs.api:openmrs-api. Attackers can target a specific entry point like ``VelocityEngine`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: 9.1/10. What to do: upgrade org.openmrs.api:openmrs-api to **2.8.6** or later. If unsure, ask your IT team or search "org.openmrs.api:openmrs-api CVE-2026-41258" on the vendor's site.
CVE-2026-41258 (org.openmrs.api:openmrs-api) — CWE-94 / CVSS v3 9.1 Attack vector: remote (network-reachable) / no user interaction Attack surface: `VelocityEngine` / `SecureUberspector` / `UberspectImpl` / `Person` Patched: `2.8.6` — apply immediately Workaround: Ensure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database. Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**arbitrary code execution** (CWE-94) exists in org.openmrs.api:openmrs-api. Attackers reach the vulnerable code path via ``VelocityEngine`` without authentication.
📍 Affected scope
org.openmrs.api:openmrs-api — . Attack surface: `VelocityEngine` / `SecureUberspector` / `UberspectImpl` / `Person`.
🔥 Severity
Severity: Critical (CVSS 9.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.8.6**.
🛡️ Workaround
Workaround: Ensure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'org.openmrs.api:openmrs-api' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'org.openmrs.api:openmrs-api' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.openmrs.api:openmrs-api` を grep し、稼働しているサービス・バージョンを把握する。

  2. 5
    Apply temporary workaround mitigate 
    Ensure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database.

    パッチが適用されるまでの応急処置として、Ensure the `Manage Concepts` privilege is restricted to only authorized users and carefully audit any `ConceptReferenceRanges` in the database. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade org.openmrs.api:openmrs-api to 2.8.6

    ステージング環境で 2.8.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  4. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

maven org.openmrs.api:openmrs-api
[{"type":"ECOSYSTEM","events":[{"introduced":"2.8.0"},{"fixed":"2.8.6"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →