CVE-2026-19182

OpenNMS v2 Alarm REST API inverted authorization check lets ROLE_REST users acknowledge alarms as any user and bypass read-only

Published Aug 13, 2026 CVSS 3.1 · 4.3 Medium EPSS < 1% KEV · Not listed
Description
An incorrect authorization check in the v2 Alarm REST API in OpenNMS Meridian and Horizon allows a low-privileged authenticated user (ROLE_REST) to acknowledge, escalate, or clear alarms recorded as an arbitrary username, and, when also assigned ROLE_READONLY, to modify alarm state despite the read-only restriction. A credential check that should restrict these operations is guarded by an inverted condition, so it never executes for a real (non-blank) username. This can potentially allow an attacker to compromise the integrity of alarm state and audit records.



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.

Analysis

AI-generated

Technical impact

A faulty authorization check in the v2 Alarm REST API of OpenNMS allows an authenticated user with the ROLE_REST privilege to acknowledge, elevate, or clear alarms recorded under any username. When the user also possesses ROLE_READONLY, the same vulnerability permits changes to alarm state even though read‑only access is intended. This flaw gives the attacker the ability to alter alarm data and audit records, potentially compromising the integrity and trustworthiness of the monitoring system.

Affected Systems

All installations of OpenNMS Meridian and Horizon running versions older than Meridian 2024.3.12, 2025.0.9 or Horizon 36.0.3 are affected. These products are distributed by The OpenNMS Group under the Horizon and Meridian brands.

Risk and Exploitability

The CVSS score of 4.3 indicates a moderate severity vulnerability. No EPSS score is available, so the likelihood of exploitation cannot be quantified from current data. The vulnerability is not listed in CISA’s KEV catalog. Attackers must have authenticated access to the REST API, typically within an organization’s private network, and possess the ROLE_REST privilege to exploit the flaw. Because the check is inverted, the condition is never enforced for genuine users, which means the flaw is always present for the targeted roles.

Remediation

Vendor Solution

Upgrade to Meridian 2024.3.12, 2025.0.9 and Horizon 36.0.3 or newer.


OpenCVE Recommended Actions

  • Upgrade to Meridian 2024.3.12, 2025.0.9, or Horizon 36.0.3 or later to apply the vendor fix.
  • If an upgrade cannot be performed immediately, block or remove the acknowledgement, escalation, and clear endpoints from the REST API for users with the ROLE_REST privilege, or use an access control policy to deny these actions to that role.
  • Review user accounts to ensure that no user has both ROLE_REST and ROLE_READONLY unless explicitly required, and apply least‑privilege principles to mitigate accidental state changes.

Generated by OpenCVE AI on August 13, 2026 at 06:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Opennms
Opennms horizon
Opennms meridian
Vendors & Products Opennms
Opennms horizon
Opennms meridian
Type Values Removed Values Added
Description An incorrect authorization check in the v2 Alarm REST API in OpenNMS Meridian and Horizon allows a low-privileged authenticated user (ROLE_REST) to acknowledge, escalate, or clear alarms recorded as an arbitrary username, and, when also assigned ROLE_READONLY, to modify alarm state despite the read-only restriction. A credential check that should restrict these operations is guarded by an inverted condition, so it never executes for a real (non-blank) username. This can potentially allow an attacker to compromise the integrity of alarm state and audit records. 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.
Title OpenNMS v2 Alarm REST API inverted authorization check lets ROLE_REST users acknowledge alarms as any user and bypass read-only
Weaknesses CWE-863
References
Metrics cvssV3_1

{'score': 4.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
OpenNMS
Published
Updated
Aug 13, 2026, 1:01 PM
Reserved
Aug 6, 2026, 6:03 PM
Status
Awaiting Analysis
Published
Aug 13, 2026, 5:17 AM
Modified
Sep 8, 2026, 7:20 PM