Skip to main content
VulnerabilityPublished

CVE-2026-24413: Icinga icinga2 · Incorrect Default Permissions

Affects Icinga icinga2Source CVE Database V5

0

Not known to be exploited · CVSS 6.8 Medium · fixed in 2.15.2 : update Icinga icinga2 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.07% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.15.2, 2.14.8, 2.13.14
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade icinga2 and icinga/icinga2 to 2.15.2, 2.14.8 or 2.13.14.

Affected software

ProductAffectedFixed in
Icingaicinga2Affected
  • >=2.15.0 <2.15.2
Fixed in
  • 2.15.2
Icingaicinga2Affected
  • >=2.14.0 <2.14.8
Fixed in
  • 2.14.8
Icingaicinga2Affected
  • >=2.3.0 <2.13.14
Fixed in
  • 2.13.14
GitHubicinga/icinga2pkg:github/icinga/icinga2Other threatsAffected
  • <2.13.14
  • <2.14.8
  • <2.15.2
Fixed in
  • 2.13.14
  • 2.14.8
  • 2.15.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

The primary mitigation is to upgrade Icinga 2 on Windows to versions 2.13.14, 2.14.8, or 2.15.2 or later, which include fixes for the ACL misconfiguration. For organizations unable to upgrade immediately, upgrading the Icinga for Windows agent to v1.13.4, v1.12.4, or v1.11.2 will automatically correct the ACLs for the agent components. Alternatively, administrators should manually audit and correct the ACLs on the %ProgramData%\icinga2\var directory and the C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate folder. This involves restricting read and write permissions to only the Icinga service user and system administrators, removing access for general local users. Regularly verifying ACL integrity and monitoring access logs for unusual local file access attempts can help detect exploitation attempts. Additionally, implementing strict local user account management and minimizing the number of users with local access to monitoring servers reduces risk. Organizations should also review and harden Windows host security policies and consider endpoint detection solutions to monitor for suspicious activity related to Icinga files.

Description

Icinga 2 is an open source monitoring system. Starting in version 2.3.0 and prior to versions 2.13.14, 2.14.8, and 2.15.2, the Icinga 2 MSI did not set appropriate permissions for the `%ProgramData%\icinga2\var` folder on Windows. This resulted in the its contents - including the private key of the user and synced configuration - being readable by all local users. All installations on Windows are affected. Versions 2.13.14, 2.14.8, and 2.15.2 contains a fix. There are two possibilities to work around the issue without upgrading Icinga 2. Upgrade Icinga for Windows to at least version v1.13.4, v1.12.4, or v1.11.2. These version will automatically fix the ACLs for the Icinga 2 agent as well. Alternatively, manually update the ACL for the given folder `C:\ProgramData\icinga2\var` (and `C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate` to fix the issue for the Icinga for Windows as well) including every sub-folder and item to restrict access for general users, only allowing the Icinga service user and administrators access.

References

Community reviews

Loading reviews…