VulnerabilityPublished 29 Jan 2026

CVE-2026-24414: icinga-powershell-framework · Incorrect Default Permissions

Affects icinga-powershell-frameworkSource CVE Database V5

Mentioned vulnerabilities

CVE-2026-24413

Not known to be exploited · CVSS 6.8 Medium · fixed in 1.13.4 : update icinga-powershell-framework 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.1% 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 1.13.4, 1.12.4, 1.11.2

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

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade icinga-powershell-framework to 1.13.4, 1.12.4 or 1.11.2; icinga/icinga-powershell-framework to 1.11.2.

Affected software

Product	Affected	Fixed in
Icingaicinga-powershell-framework	Affected >=1.13.0 <1.13.4	Fixed in 1.13.4
Icingaicinga-powershell-framework	Affected >=1.12.0 <1.12.4	Fixed in 1.12.4
Icingaicinga-powershell-framework	Affected <1.11.2	Fixed in 1.11.2
GitHubicinga/icinga-powershell-framework`pkg:github/icinga/icinga-powershell-framework`Other threats	Affected <1.11.2	Fixed in 1.11.2

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

AI-suggested

European organizations should immediately assess their use of the Icinga PowerShell Framework and Icinga 2 agents on Windows hosts. The primary mitigation is to upgrade to the fixed versions 1.13.4, 1.12.4, or 1.11.2 or later, which address the permission issues. If immediate upgrading is not feasible, administrators must manually restrict the ACL permissions on the following directories: 'C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate' and 'C:\ProgramData\icinga2\var' including all subfolders and files. Access should be limited strictly to the Icinga service user and system administrators, removing read permissions from general users. Additionally, organizations should audit local user privileges to minimize unnecessary access, implement strict endpoint security controls to prevent unauthorized local access, and monitor for suspicious access to these directories. Regularly reviewing and hardening file system permissions and applying the principle of least privilege will reduce risk. Finally, organizations should integrate this vulnerability into their patch management and vulnerability scanning processes to ensure timely detection and remediation.

Description

The Icinga PowerShell Framework provides configuration and check possibilities to ensure integration and monitoring of Windows environments. In versions prior to 1.13.4, 1.12.4, and 1.11.2, permissions of the Icinga for Windows `certificate` directory grant every user read access, which results in the exposure of private key of the Icinga certificate for the given host. All installations are affected. Versions 1.13.4, 1.12.4, and 1.11.2 contains a patch. Please note that upgrading to a fixed version of Icinga for Windows will also automatically fix a similar issue present in Icinga 2, CVE-2026-24413. As a workaround, the permissions can be restricted manually by updating the ACL for the given folder `C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate` (and `C:\ProgramData\icinga2\var` to fix the issue for the Icinga 2 agent as well) including every sub-folder and item to restrict access for general users, only allowing the Icinga service user and administrators access.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality and trustworthiness of their monitoring infrastructure. Icinga is widely used for IT infrastructure monitoring, and exposure of private keys could allow attackers with local access to impersonate monitored hosts or intercept sensitive monitoring data. This could lead to undetected manipulation of monitoring results, false alerts, or suppression of alerts, impacting operational security and incident response. In critical sectors such as finance, healthcare, and energy, where monitoring integrity is paramount, exploitation could facilitate lateral movement or persistent footholds within networks. Although exploitation requires local access, insider threats or attackers who have compromised low-privilege accounts could leverage this vulnerability to escalate their capabilities. The vulnerability does not directly affect availability or integrity of the monitored systems but undermines the security of the monitoring framework itself, which is a critical component of overall cybersecurity posture.

Summary

The vulnerability identified as CVE-2026-24414 affects the Icinga PowerShell Framework, a tool used to integrate and monitor Windows environments. In affected versions prior to 1.13.4, 1.12.4, and 1.11.2, the permissions set on the 'certificate' directory within the Icinga for Windows installation are overly permissive, granting read access to all users on the system. This directory contains the private key of the Icinga certificate for the host, which is critical for secure communications and authentication within the monitoring framework. Exposure of this private key can allow an attacker with local access to the system to extract the key, potentially enabling them to impersonate the host or decrypt sensitive monitoring traffic. The vulnerability stems from CWE-276 (Incorrect Default Permissions), indicating a failure to restrict access to sensitive files appropriately. The CVSS 4.0 score of 6.8 reflects a medium severity, with the attack vector being local (AV:L), low complexity (AC:L), no privileges required beyond low-level user (PR:L), and no user interaction needed (UI:N). The impact is primarily on confidentiality (VC:H), with no direct impact on integrity or availability. The issue also affects Icinga 2 agents via a similar permissions problem (CVE-2026-24413), which is resolved by upgrading the Icinga for Windows framework. Mitigation involves upgrading to patched versions (1.13.4, 1.12.4, or 1.11.2 and later) or manually restricting ACL permissions on the certificate directories to allow access only to the Icinga service user and administrators. This ensures that private keys are not exposed to unauthorized users on the host system.

CWE-276Incorrect Default Permissions (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
During installation, installed file permissions are set to allow anyone to modify those files.
Architecture and Design · Operation
The architecture needs to access and modification attributes for files to only those users who actually require those actions.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jan 2026, 18:12 UTC

WeaknessesCWE-276

Technical details

References

Community reviews

Related threats