rootpwn

critical · CVSS v3 9.8

CVE-2026-61550

Icinga 2 certificate update JSON‑RPC handling fails to verify the sender, allowing an unauthenticated attacker on TCP port 5665 to replace n

Overview

Icinga 2 certificate update JSON‑RPC handling fails to verify the sender, allowing an unauthenticated attacker on TCP port 5665 to replace node and CA certificates. This lets the attacker impersonate a trusted node and take full control of the monitored system. The flaw is present in versions 2.8 through 2.14.9, 2.15.4, and 2.16.2.

Description

Icinga 2 is an open source monitoring system. From 2.8 until 2.14.9, 2.15.4, and 2.16.2, certificate update JSON-RPC message handling does not validate that the sender is a trusted endpoint. An unauthenticated network attacker able to connect to TCP port 5665 can replace the node certificate and trusted CA certificate, impersonate a trusted node, and take control of the node. This issue is fixed in versions 2.14.9, 2.15.4, and 2.16.2.

Impact

Confidentiality: attacker can read monitoring data; Integrity: attacker can alter monitoring configuration and inject false alerts; Availability: attacker can disrupt monitoring services by replacing certificates. System administrators and network operators are directly impacted.

Remediation

Apply the latest patch that includes the fix (2.14.9, 2.15.4, or 2.16.2). If patching is not immediately possible, restrict TCP port 5665 to trusted IPs using firewall rules or disable JSON‑RPC certificate updates. Verify that only authorized endpoints can send certificate updates and monitor logs for unexpected certificate changes.

Risk context

The CVE has a critical severity score of 9.8, indicating a high likelihood of exploitation and significant impact. Immediate remediation is advised to prevent potential takeover of monitoring nodes.

Affected products

  • Icinga 2 2.8-2.14.9
  • Icinga 2 2.15.4
  • Icinga 2 2.16.2

Scores

Severity
critical
CVSS v2
10
CVSS v3
9.8
CVSS v4
—
EPSS
—

icinga certificate json-rpc unauthenticated critical monitoring network

← All CVEs

Related CVEs

critical

CVE-2026-81321

CM2507 IP cameras store configured wireless network credentials in cleartext within the device filesystem. An attacker who obtains filesystem access through physical access, a debugging interface, or another vulnerability could recover the configured network identifier and pre-shared key.

View analysis

critical

CVE-2026-85497

CareCam CM2507 IP cameras store the device's root-account password using a fixed legacy password hash that provides insufficient resistance to offline cracking. An attacker who obtains the firmware image or password database could recover the associated credential, which may also be reusable across other devices running the same firmware.

View analysis

critical

CVE-2026-63374

AnyIO: TLSStream IDNA 2003 host name encoding enables potential TLS certificate spoofing

View analysis

critical

CVE-2025-66455

LMDeploy is a toolkit for compressing, deploying, and serving large language models. Starting in version 0.9.2 and prior to version 0.16.0, LMDeploy's PyTorch DistServe/PD-disaggregation control plane used `recv_pyobj()` to deserialize messages received through a ZeroMQ PULL socket. PyZMQ implements `recv_pyobj()` using Python pickle deserialization, which can execute arbitrary code while reconstructing an object. The peer address used by the receiver was supplied through the `POST /distserve/p2p_connect` HTTP endpoint. An attacker who could reach an affected DistServe API server could cause the server to connect to an attacker-controlled ZeroMQ endpoint and deserialize a crafted pickle payload. API-key authentication is not enabled unless the operator explicitly configures it. As a result, affected DistServe deployments without API keys allowed unauthenticated remote code execution with the privileges of the LMDeploy serving process. This issue affects the PyTorch backend when PD-disaggregation/DistServe is enabled. Ordinary deployments that do not use the affected disaggregated-serving path do not expose this data flow. The fix was released in LMDeploy 0.16.0. Users who cannot upgrade immediately should prevent untrusted clients from reaching `/distserve/*` endpoints, restrict the DistServe HTTP and ZeroMQ control planes to trusted cluster networks, configure API-key authentication, and block arbitrary outbound ZeroMQ connections from serving nodes. These measures reduce exposure but do not make pickle deserialization safe.

View analysis