ZeroHour

CVE-2026-89054

moderate

Missing Authorization in OpenNMS Horizon allows unauthenticated config changes

CVSS 3.1
8.2 high
EPSS
Published
()
Modified
AI analysis

CVE-2026-89054 is a missing authorization flaw (CWE-862) in OpenNMS Horizon: the Spring Security policy for the /api/v2 REST API defines authorization rules for every HTTP method except PATCH, leaving the shipped @PATCH configuration endpoints for event configuration and SNMP data collection reachable with no authentication enforced. An unauthenticated attacker who can reach the web UI can send PATCH requests to disable event definitions and SNMP data-collection sources, with the change persisted and reloaded into the running system. The attacker gains suppression of event and alarm generation and cessation of metric collection, silently degrading monitoring and detection with no confidentiality impact (CVSS 3.1: 8.2, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L). All OpenNMS Horizon deployments running versions before 36.0.4 are affected; vendor documentation states Horizon and Meridian are intended for private networks and not direct Internet access, so exploitation most plausibly comes from attackers with internal network reach to the web UI or misconfigured Internet-exposed instances. No public proof-of-concept is known, the issue is not in the CISA KEV catalog, and no exploitation has been reported.

What to do: Upgrade to OpenNMS Horizon 36.0.4 or newer. Until patched, restrict network access to the Horizon web UI and /api/v2 REST endpoints (firewall/ACL rules or reverse-proxy authentication), consistent with vendor guidance that the product not be directly Internet-accessible. Review event configuration and SNMP data-collection settings for unauthorized changes and verify that event/alarm generation and metric collection have not been silently disabled.

Affected
OpenNMS HorizonVersions prior to 36.0.4 (fixed in 36.0.4 and later)
Estimated exposure
moderate≈1,000–10,000 installations worldwide (estimate), with Internet-exposed instances likely numbering only in the hundreds given private-network deployment… — OpenNMS Horizon is a specialized open-source network-monitoring platform with a modest install base that vendor guidance says is deployed on private networks rather than directly Internet-facing, so this order-of-magnitude estimate is…

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

A missing authorization vulnerability in OpenNMS Horizon allows configuration changes without authentication. The Spring Security policy for the /api/v2 REST API defines authorization rules for every HTTP method except PATCH, so the shipped @PATCH configuration endpoints for event configuration and SNMP data collection (which enable and disable event definitions and data-collection sources) are reachable with no authorization enforced. An unauthenticated attacker able to reach the web UI can disable event definitions and SNMP data collection, suppressing event and alarm generation and stopping metric collection - silently degrading monitoring and detection - with the change persisted and reloaded into the running system. The solution is to upgrade to Horizon 36.0.4 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.

Weakness
CWE-862
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

In the news

No ingested article mentions this CVE yet.