CVE-2026-19135

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

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

A JEXL expression sandbox bypass exists in multiple versions of OpenNMS Meridian and Horizon. A low-privileged authenticated user can submit a crafted expression to the Measurements REST API that escapes the sandbox and loads arbitrary Java classes on the server. This can potentially allow an attacker to gain access to confidential information and compromise integrity.

The solution is to upgrade to Meridian 2024.3.12, 2025.0.9 and Horizon 36.0.3 or newer. Meridian and Horizon installation instructions state that they are intended for installation within an organization's private networks and should not be directly accessible from the Internet.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 13, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

NMS-20051: Fix JEXL sandbox bypass

Fix merged in OpenNMS/opennms PR #8754 on 2026-08-06 — awaiting tagged release

https://github.com/OpenNMS/opennms/pull/8754

Vendor Advisories for CVE-2026-19135(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 24× 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.

  1. 2026-08-20 01:59 UTCEG score recompute
  2. 2026-08-20 01:59 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 23:53 UTCEG score recompute
  5. 2026-08-18 23:53 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 21:46 UTCEG score recompute
  8. 2026-08-17 21:46 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 19:35 UTCEG score recompute
  11. 2026-08-16 19:35 UTCGHSA enrichment
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 17:30 UTCEG score recompute
  15. 2026-08-15 17:30 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 15:24 UTCEG score recompute
  18. 2026-08-14 15:24 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 13:18 UTCEG score recompute
  21. 2026-08-13 13:18 UTCGHSA enrichment
  22. 2026-08-13 05:19 UTCEG score recompute
  23. 2026-08-13 05:05 UTCEG score recompute
  24. 2026-08-13 05:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19135?
CVE-2026-19135 is a medium vulnerability published on August 13, 2026. A JEXL expression sandbox bypass exists in multiple versions of OpenNMS Meridian and Horizon. A low-privileged authenticated user can submit a crafted expression to the Measurements REST API that escapes the sandbox and loads arbitrary Java classes on the server. This can potentially allow an…
When was CVE-2026-19135 disclosed?
CVE-2026-19135 was first published in the National Vulnerability Database on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19135 actively exploited?
CVE-2026-19135 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 93.0% of all scored CVEs.
What is the CVSS score of CVE-2026-19135?
CVE-2026-19135 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-19135?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19135, 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

Explore the affected products and dependency analysis for CVE-2026-19135

Explore →

Is Your Infrastructure Affected by CVE-2026-19135?

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