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

CVE-2026-111235: OpenNMS Auth Bypass Vulnerability

CVE-2026-111235 is an authorization bypass flaw in OpenNMS Meridian and Horizon that allows unauthenticated attackers to access REST APIs. This vulnerability enables unauthorized inventory access and resource manipulation.

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-111235 Overview

CVE-2026-111235 is an authorization bypass vulnerability in the REST API of OpenNMS Meridian and Horizon. The /rest/** Spring Security filter chains define intercept-url rules that match HTTP methods as uppercase tokens and compare them case-sensitively. The chains also lack a terminal deny rule. A request using a non-canonical method token, such as a lowercase verb, matches no rule and bypasses authentication. A remote, unauthenticated attacker can read monitored inventory and can create, modify, or delete REST resources, including injecting events to fabricate or suppress alarms [CWE-204].

Critical Impact

Unauthenticated remote attackers can read, modify, or delete REST API resources and manipulate alarm state on affected OpenNMS deployments.

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 exposing the /rest/** and /rest/alarms endpoints

Discovery Timeline

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

Technical Details for CVE-2026-111235

Vulnerability Analysis

The flaw resides in the Spring Security configuration guarding the OpenNMS REST API. Each intercept-url rule names an HTTP method as an uppercase token (for example GET, POST) and the matcher compares methods case-sensitively. When a request arrives with a lowercase or otherwise non-canonical method token, no rule matches. Because the filter chain lacks a terminal deny rule, unmatched requests fall through and reach the controller without authentication.

The /rest/alarms chain has the same defect and additionally leaks alarm existence through differential responses. An attacker can enumerate alarms, suppress active alerts, or inject synthetic events that trigger downstream automation. The fix adds a terminal deny rule to each REST filter chain so unmatched requests are rejected by default.

Root Cause

The root cause is Response Discrepancy information exposure combined with incomplete authorization logic [CWE-204]. The Spring Security intercept-url matchers were written as an allow-list keyed on uppercase HTTP verbs, without a default-deny fallback. Case-sensitive method comparison combined with no catch-all rule produces an authorization gap for any non-canonical method token.

Attack Vector

Exploitation is network-based, requires no authentication, and no user interaction. A remote attacker sends an HTTP request to /rest/** using a non-canonical method token, for example get instead of GET. The request bypasses the Spring Security filter chain and is dispatched to the REST controller as an unauthenticated call. The attacker can then enumerate monitored inventory, create or delete resources, and inject events against /rest/events to fabricate or suppress alarms. See the upstream fix in GitHub Pull Request #8934 for the authoritative patch details.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-111235

Indicators of Compromise

  • HTTP access log entries targeting /rest/** paths with non-uppercase method tokens such as get, post, put, or delete.
  • Unauthenticated REST calls that successfully return 2xx responses for inventory, nodes, or alarm resources.
  • Unexpected event injection into /rest/events or state changes on /rest/alarms with no corresponding operator action.

Detection Strategies

  • Parse reverse proxy and application logs for request lines where the HTTP method does not match the canonical uppercase form.
  • Correlate successful REST responses with the absence of an authenticated session identifier or Authorization header.
  • Alert on bursts of /rest/alarms reads from a single source, which may indicate alarm enumeration via response-difference probing.

Monitoring Recommendations

  • Enable verbose access logging on the fronting web server or load balancer and retain HTTP method strings exactly as received.
  • Baseline normal /rest/** traffic by source IP and user, then alert on deviations from that baseline.
  • Forward OpenNMS access logs to a centralized SIEM for retention and correlation with downstream alert suppression events.

How to Mitigate CVE-2026-111235

Immediate Actions Required

  • Upgrade OpenNMS Meridian to 2024.3.14, 2025.0.11, or 2026.0.1, or OpenNMS Horizon to 36.0.5 or newer.
  • Verify the OpenNMS instance is not directly reachable from the public Internet, per vendor installation guidance.
  • Audit REST API access logs for prior exploitation using non-canonical HTTP method tokens.

Patch Information

The vendor fix adds a terminal deny rule to each REST Spring Security filter chain so that any request not matching an explicit allow rule is rejected. Patched releases are OpenNMS Meridian 2024.3.14, 2025.0.11, 2026.0.1, and OpenNMS Horizon 36.0.5. The code change is documented in GitHub Pull Request #8934.

Workarounds

  • Place OpenNMS behind a reverse proxy that rejects or normalizes HTTP requests whose method token is not uppercase canonical.
  • Restrict /rest/** access to trusted management networks using firewall or proxy ACLs until the patch is applied.
  • Disable or network-isolate the REST API if it is not required for current operations.
bash
# Example nginx reverse proxy rule to block non-canonical HTTP methods
location /rest/ {
    if ($request_method !~ ^(GET|POST|PUT|DELETE|PATCH|HEAD|OPTIONS)$) {
        return 405;
    }
    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.