/

CVE-2026-61550

Severity:

CRITICAL RISK

(9.8)

Missing Authorization (CWE-862) in Icinga 2 Node Agent

CVE-2026-61550

Awaiting Analysis

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Node Takeover and Trusted-Endpoint Impersonation

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Icinga 2 certificate-update JSON-RPC handling does not verify that certificate changes originate from a trusted endpoint. An unauthenticated attacker who can connect to the node's network service may replace certificate material, impersonate a trusted node, and take control of the affected node.

Affected context

The issue can occur in Icinga 2 deployments that expose the certificate-update JSON-RPC service on TCP port 5665 and process certificate changes without validating the sender's authorization. Risk is highest when the service is reachable by untrusted or insufficiently restricted networks.

Exploit preconditions

  • Attack surface: Icinga 2 JSON-RPC service on TCP port 5665
  • Required access: Network connectivity to the affected node; authentication is not required
  • Trigger point: Processing of a certificate update message
  • Why exploitation is possible: The handler accepts certificate changes without confirming that the sender is a trusted endpoint

Why this happens

The underlying flaw is an authorization failure in certificate-management message handling. The implementation verifies or processes certificate update data without enforcing the required trust relationship with the sending endpoint, allowing an untrusted party to alter security-critical identity material. This maps to CWE-862: Missing Authorization, in which a sensitive operation is exposed without an adequate permission check.

Potential impact

  • An attacker may replace the node certificate or trusted CA certificate
  • An attacker could impersonate a trusted Icinga endpoint
  • The affected node may be taken over
  • Monitoring integrity and administrative trust relationships may be compromised
  • An attacker could use the compromised node to support further network intrusion

General mitigation guidance

Mitigation generally focuses on enforcing authorization before processing certificate-management operations and reducing exposure of the management service.

Defensive patterns include:

  • Require strong mutual authentication and explicit endpoint authorization for certificate updates
  • Reject certificate changes that are not associated with an already trusted administrative relationship
  • Restrict TCP port 5665 to approved management networks and peer addresses
  • Separate certificate-management privileges from routine monitoring permissions
  • Protect private keys and trusted CA material with restrictive filesystem and service permissions
  • Treat certificate updates as security-sensitive changes requiring auditable approval
  • Use secure-by-default network policies that deny unsolicited access to node management interfaces

How teams detect issues like this

Organizations can detect this class of issue through:

  • Static analysis and code review rules requiring authorization checks before security-sensitive state changes
  • Review of JSON-RPC handlers that modify certificates, trust stores, or identity metadata
  • Network monitoring for unexpected connections to TCP port 5665
  • Audit logging for certificate updates, trust-store changes, and changes from previously unseen endpoints
  • Policy enforcement requiring mutual authentication and approved source networks for management APIs
  • Automated security review tools that flag unauthenticated handlers affecting privileged configuration

Sources

SourceLink
github.comgithub.com/Icinga/icinga2/commit/4b7fb3405f4616a24b2b55e20f603a56b7dd6ad0
github.comgithub.com/Icinga/icinga2/commit/6c2e0db3819f859910a4ae265461cb51b1d2039c
github.comgithub.com/Icinga/icinga2/commit/a6f7cc7a4ef8beed023b24416106822d6940c4c0
github.comgithub.com/Icinga/icinga2/commit/d37b0cfd7d9595ae2f02fadb3d724c98d8620f81
github.comgithub.com/Icinga/icinga2/pull/10907
github.comgithub.com/Icinga/icinga2/releases/tag/v2.14.9
github.comgithub.com/Icinga/icinga2/releases/tag/v2.15.4
github.comgithub.com/Icinga/icinga2/releases/tag/v2.16.2
github.comgithub.com/Icinga/icinga2/security/advisories/GHSA-vj39-ww8j-vvx5
icinga.comicinga.com/blog/icinga2-security-release-v2-16-2

Frequently asked

questions

Yes. An attacker does not need local access if they can establish a network connection to the affected Icinga 2 service on TCP port 5665.

No authentication is required according to the vulnerability description. Network reachability to the certificate-update interface is the key prerequisite.

Enforce sender authentication and explicit authorization before accepting any certificate or trusted-CA update, while limiting the service to approved management networks.

Treat identity and trust-store changes as privileged operations, apply deny-by-default network policies, require auditable approval, and test all management handlers for authorization enforcement.

Find out what's already
exploitable in your codebase.