CVE-2026-41258

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

OpenMRS is an open source electronic medical record system platform. From 2.7.0 to before 2.7.9 and 2.8.6, 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 noSecureUberspector, 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). This vulnerability is fixed in 2.7.9 and 2.8.6.

CVSS v3
9.1
EG Score
9.1(medium)
EPSS
23.6%
KEV
Not listed

Published

May 15, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated May 15, 2026
Patch available. Sources: github.
github Patch Available

Stored Velocity SSTI to RCE via ConceptReferenceRange · Advisory · openmrs/openmrs-core · GitHub

Affected: 2.8.6 and 2.7.9 as well as future versions.

https://github.com/openmrs/openmrs-core/security/advisories/GHSA-xj4f-8jjg-vx4q

Vendor Advisories for CVE-2026-41258(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.openmrs.api:openmrs-api—2.8.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 68× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 176 total refreshes for this CVE.

  1. 2026-07-12 05:46 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-09 19:10 UTCEPSS rescore
  4. 2026-07-08 15:15 UTCEPSS rescore
  5. 2026-07-07 13:46 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 16:27 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-06 02:23 UTCEPSS rescore
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 06:31 UTCEPSS rescore
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-06-30 23:22 UTCEPSS rescore
  14. 2026-06-29 21:30 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 12:32 UTCEG score recompute
  18. 2026-06-28 08:01 UTCEG score recompute
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 02:09 UTCEG score recompute
  21. 2026-06-27 21:54 UTCEG score recompute
  22. 2026-06-27 13:10 UTCEG score recompute
  23. 2026-06-27 07:46 UTCEG score recompute
  24. 2026-06-27 03:08 UTCEPSS rescore
  25. 2026-06-26 20:12 UTCEG score recompute
Show 75 more
  1. 2026-06-26 03:54 UTCEG score recompute
  2. 2026-06-25 23:21 UTCEG score recompute
  3. 2026-06-25 18:47 UTCEG score recompute
  4. 2026-06-25 13:49 UTCEPSS rescore
  5. 2026-06-25 13:49 UTCEPSS rescore
  6. 2026-06-24 14:05 UTCEPSS rescore
  7. 2026-06-23 21:33 UTCEPSS rescore
  8. 2026-06-22 14:25 UTCEPSS rescore
  9. 2026-06-22 14:25 UTCEPSS rescore
  10. 2026-06-21 14:56 UTCEPSS rescore
  11. 2026-06-21 14:56 UTCEPSS rescore
  12. 2026-06-21 01:59 UTCEPSS rescore
  13. 2026-06-19 19:25 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-18 04:03 UTCEG score recompute
  17. 2026-06-17 20:16 UTCEG score recompute
  18. 2026-06-17 17:53 UTCEPSS rescore
  19. 2026-06-17 13:26 UTCEG score recompute
  20. 2026-06-17 06:06 UTCEG score recompute
  21. 2026-06-17 01:59 UTCEG score recompute
  22. 2026-06-16 21:50 UTCEG score recompute
  23. 2026-06-16 17:52 UTCEPSS rescore
  24. 2026-06-16 11:57 UTCEG score recompute
  25. 2026-06-16 07:49 UTCEG score recompute
  26. 2026-06-16 03:42 UTCEG score recompute
  27. 2026-06-15 23:34 UTCEG score recompute
  28. 2026-06-15 17:49 UTCEPSS rescore
  29. 2026-06-15 04:14 UTCEG score recompute
  30. 2026-06-15 00:04 UTCEG score recompute
  31. 2026-06-14 19:56 UTCEG score recompute
  32. 2026-06-14 15:48 UTCEG score recompute
  33. 2026-06-14 11:40 UTCEG score recompute
  34. 2026-06-14 07:33 UTCEG score recompute
  35. 2026-06-14 03:26 UTCEG score recompute
  36. 2026-06-13 23:18 UTCEG score recompute
  37. 2026-06-13 23:00 UTCEPSS rescore
  38. 2026-06-13 08:11 UTCEG score recompute
  39. 2026-06-13 04:04 UTCEG score recompute
  40. 2026-06-12 23:12 UTCEPSS rescore
  41. 2026-06-12 23:12 UTCEPSS rescore
  42. 2026-06-12 23:02 UTCEG score recompute
  43. 2026-06-12 18:54 UTCEG score recompute
  44. 2026-06-12 14:46 UTCEG score recompute
  45. 2026-06-12 10:34 UTCEG score recompute
  46. 2026-06-12 06:27 UTCEG score recompute
  47. 2026-06-12 02:20 UTCEG score recompute
  48. 2026-06-11 22:12 UTCEG score recompute
  49. 2026-06-11 18:05 UTCEG score recompute
  50. 2026-06-11 14:00 UTCEPSS rescore
  51. 2026-06-11 13:56 UTCEG score recompute
  52. 2026-06-11 09:49 UTCEG score recompute
  53. 2026-06-11 05:42 UTCEG score recompute
  54. 2026-06-11 01:35 UTCEG score recompute
  55. 2026-06-10 22:18 UTCEPSS rescore
  56. 2026-06-10 21:27 UTCEG score recompute
  57. 2026-06-10 17:20 UTCEG score recompute
  58. 2026-06-10 13:22 UTCEPSS rescore
  59. 2026-06-10 13:22 UTCEPSS rescore
  60. 2026-06-10 13:13 UTCEG score recompute
  61. 2026-06-10 09:06 UTCEG score recompute
  62. 2026-06-10 04:59 UTCEG score recompute
  63. 2026-06-10 00:52 UTCEG score recompute
  64. 2026-06-09 20:45 UTCEG score recompute
  65. 2026-06-09 16:25 UTCEG score recompute
  66. 2026-06-09 12:16 UTCEG score recompute
  67. 2026-06-09 08:09 UTCEG score recompute
  68. 2026-06-09 04:02 UTCEG score recompute
  69. 2026-06-08 23:54 UTCEG score recompute
  70. 2026-06-08 19:47 UTCEG score recompute
  71. 2026-06-08 14:52 UTCEG score recompute
  72. 2026-06-08 14:17 UTCEPSS rescore
  73. 2026-06-08 14:17 UTCEPSS rescore
  74. 2026-06-08 10:45 UTCEG score recompute
  75. 2026-06-08 06:38 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-41258?
CVE-2026-41258 is a critical vulnerability published on May 15, 2026. OpenMRS is an open source electronic medical record system platform. From 2.7.0 to before 2.7.9 and 2.8.6, the ConceptReferenceRangeUtility.evaluateCriteria() method in OpenMRS Core evaluates database-stored criteria strings as Apache Velocity templates without any sandbox configuration. The…
When was CVE-2026-41258 disclosed?
CVE-2026-41258 was first published in the National Vulnerability Database on May 15, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-41258 actively exploited?
CVE-2026-41258 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 23.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41258?
CVE-2026-41258 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-41258?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41258, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-41258

Explore →

Is Your Infrastructure Affected by CVE-2026-41258?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs