Skip to main content
Vulnerability Database/CVE-2026-111252

CVE-2026-111252: OpenNMS XML Entity Expansion DOS Vulnerability

CVE-2026-111252 is a denial of service flaw in OpenNMS Meridian and Horizon caused by unchecked XML entity expansion that exhausts server memory. This post covers the technical details, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-111252 Overview

CVE-2026-111252 is a denial of service vulnerability in the XML parsing logic of OpenNMS Meridian and Horizon. OpenNMS parses XML documents without an effective limit on entity expansion. An authenticated user with provisioning access can submit a crafted requisition or foreign-source import that contains a DOCTYPE declaring internal entities. The parser expands these entities until server memory is exhausted. Both deeply nested entities and a single large entity referenced many times trigger the condition. The weakness is tracked under CWE-400: Uncontrolled Resource Consumption.

Critical Impact

An authenticated provisioning user can exhaust server memory and take the OpenNMS monitoring platform offline through a single malicious XML requisition.

Affected Products

  • OpenNMS Meridian versions prior to 2024.3.14, 2025.0.11, and 2026.0.1
  • OpenNMS Horizon versions prior to 36.0.5
  • Deployments that expose provisioning or foreign-source import to lower-privileged accounts

Discovery Timeline

  • 2026-10-15 - CVE-2026-111252 published to the National Vulnerability Database
  • 2026-10-16 - Last updated in NVD database

Technical Details for CVE-2026-111252

Vulnerability Analysis

The vulnerability is a classic XML entity expansion attack, often referred to as a billion laughs attack. OpenNMS accepts XML through its requisition and foreign-source import workflows. The underlying parser processes DOCTYPE declarations and expands any internal entities they define. Because no cap existed on the total number of expansions, a small input could generate gigabytes of in-memory data.

Two attack shapes trigger the condition. The first nests entity references so each level multiplies the expanded output. The second declares a single large entity string and references it many times in the document body. Either approach drives the Java heap to exhaustion and crashes or stalls the OpenNMS process.

The fix caps the number of entity expansions across all XML parsing paths in OpenNMS. It also rejects any DOCTYPE declaration inside requisition and foreign-source XML, closing the entry point entirely for provisioning data.

Root Cause

The root cause is missing hardening on the XML parser configuration. OpenNMS did not disable DOCTYPE processing for untrusted provisioning input and did not set a jdk.xml.entityExpansionLimit style constraint on expansion counts. Any authenticated provisioning user supplied XML the parser treated as trusted.

Attack Vector

An authenticated user with provisioning privileges submits a crafted XML document through a requisition or foreign-source import. The import mechanism can also fetch a remote requisition URL that the server retrieves and parses. The attacker therefore has two delivery options: direct upload or hosting the payload on an attacker-controlled URL that OpenNMS fetches.

The attack requires network access to the OpenNMS web interface and valid credentials with provisioning rights. OpenNMS documentation states Meridian and Horizon are intended for private networks, which limits exposure but does not eliminate insider or compromised-account risk. Technical details are documented in OpenNMS Pull Request #8898 and OpenNMS Pull Request #8952.

Detection Methods for CVE-2026-111252

Indicators of Compromise

  • XML requisition payloads containing <!DOCTYPE> declarations submitted to the provisioning API
  • Requisition imports referencing external URLs that return XML with internal entity declarations such as <!ENTITY lol "lol">
  • Sudden spikes in Java heap usage on the OpenNMS server correlated with provisioning API requests
  • OutOfMemoryError exceptions in OpenNMS logs following requisition import activity

Detection Strategies

  • Inspect HTTP request bodies to /opennms/rest/requisitions and foreign-source endpoints for DOCTYPE and ENTITY tokens
  • Correlate provisioning API activity with JVM metrics to catch memory exhaustion patterns before a crash
  • Alert on repeated or large requisition uploads from a single authenticated account within a short window

Monitoring Recommendations

  • Enable audit logging for all provisioning and foreign-source import operations with user attribution
  • Monitor outbound HTTP requests from the OpenNMS server triggered by remote requisition URLs
  • Track JVM heap, garbage collection pauses, and process restart events on OpenNMS hosts

How to Mitigate CVE-2026-111252

Immediate Actions Required

  • Upgrade to OpenNMS Meridian 2024.3.14, 2025.0.11, or 2026.0.1, or Horizon 36.0.5 or newer
  • Audit accounts that hold provisioning privileges and remove the role from users who do not need it
  • Confirm the OpenNMS web interface is not reachable from the public internet, consistent with vendor guidance
  • Review recent requisition imports for DOCTYPE declarations and unexpected remote URLs

Patch Information

The fix is delivered in OpenNMS Meridian 2024.3.14, 2025.0.11, 2026.0.1, and Horizon 36.0.5. The patch caps entity expansions across all XML parsing and rejects any DOCTYPE declaration in requisition and foreign-source XML. Source changes are available in OpenNMS Pull Request #8898 and OpenNMS Pull Request #8952.

Workarounds

  • Restrict provisioning role membership to a small set of trusted administrators until patched
  • Place a reverse proxy or WAF rule in front of OpenNMS that strips or blocks <!DOCTYPE in requisition request bodies
  • Block outbound HTTP egress from the OpenNMS server to prevent remote requisition URL fetches to untrusted hosts
  • Set JVM heap limits and process supervision so a memory exhaustion event triggers a controlled restart
bash
# Example reverse proxy rule to block DOCTYPE in requisition submissions
# NGINX location block for the OpenNMS provisioning API
location /opennms/rest/requisitions {
    if ($request_body ~* "<!DOCTYPE") {
        return 403;
    }
    proxy_pass http://opennms_backend;
}

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.