Icinga 2 is widely used for enterprise monitoring; unauthenticated remote compromise of nodes can disrupt monitoring and trust across organizations.
CVE-2026-61550
Unauthenticated attacker can replace certs and fully compromise Icinga 2 nodes via TCP/5665.
Is CVE-2026-61550 being exploited?
Not confirmed. CVE-2026-61550 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.67% probability of exploitation in the next 30 days.
How severe is CVE-2026-61550?
CVE-2026-61550 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61550?
Yes. A fix has been recorded for CVE-2026-61550. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-61550 affect?
CVE-2026-61550 affects Icinga 2 v2.8 through prior-to-2.14.9, Icinga 2 v2.15.0-2.15.3, Icinga 2 v2.16.0-2.16.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61550?
Upgrade to 2.14.9, 2.15.4 or 2.16.2 and restrict access to TCP/5665
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated network attacker connecting to TCP/5665 can replace node and CA certificates, impersonate trusted nodes, and take full control of the node.
Immediate action required
- affected>= 2.8 and < 2.14.9
- affected>= 2.15.0 and < 2.15.4
- affected>= 2.16.0 and < 2.16.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- total
Assessed by CISA 21 Sept 2026 (SSVC 2.0.3).
timeline
- 18 Sept 2026Published
- 21 Sept 2026Analysed by vulneraibility.com · 3 days later
- 21 Sept 2026CISA SSVC assessment: exploitation none · same day later
- 21 Sept 2026CVE record last updated · same day later
also known as
- Linkgithub.com /Icinga/icinga2/security/advisories/GHSA-vj39-ww8j-vvx5
- Linkgithub.com /Icinga/icinga2/pull/10907
- Linkgithub.com /Icinga/icinga2/commit/4b7fb3405f4616a24b2b55e20f603a56b7dd6ad0
- Linkgithub.com /Icinga/icinga2/commit/6c2e0db3819f859910a4ae265461cb51b1d2039c
- Linkgithub.com /Icinga/icinga2/commit/a6f7cc7a4ef8beed023b24416106822d6940c4c0
- Linkgithub.com /Icinga/icinga2/commit/d37b0cfd7d9595ae2f02fadb3d724c98d8620f81
- Linkgithub.com /Icinga/icinga2/releases/tag/v2.14.9
- Linkgithub.com /Icinga/icinga2/releases/tag/v2.15.4
Show 2 more
- Linkgithub.com /Icinga/icinga2/releases/tag/v2.16.2
- Linkicinga.com /blog/icinga2-security-release-v2-16-2
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- OSV: advisory aliases and downstream package versions
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.