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.
References10
- github.com/Icinga/icinga2/commit/4b7fb3405f4616a24b2b55e20f603a…
- github.com/Icinga/icinga2/commit/6c2e0db3819f859910a4ae265461cb…
- github.com/Icinga/icinga2/commit/a6f7cc7a4ef8beed023b2441610682…
- github.com/Icinga/icinga2/commit/d37b0cfd7d9595ae2f02fadb3d724c…
- github.com/Icinga/icinga2/pull/10907
- github.com/Icinga/icinga2/releases/tag/v2.14.9
- github.com/Icinga/icinga2/releases/tag/v2.15.4
- github.com/Icinga/icinga2/releases/tag/v2.16.2
- github.com/Icinga/icinga2/security/advisories/GHSA-vj39-ww8j-vv…
- icinga.com/blog/icinga2-security-release-v2-16-2
Metrics
- CVSS 3.1
-
9.8
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 52 · as of 8 November 2026
- CWE
- CWE-862
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.