CVE-2026-24414

Icinga for Windows certificate can have too-open permissions

MEDIUM
5.5
CVSS Score
Published: January 29, 2026 at 05:35 PM UTC
Updated: June 17, 2026 at 10:23 AM UTC
2 products affected across 1 vendorIcinga PowerShell FrameworkIcinga PowerShell Framework

Using icinga-powershell-framework by Icinga?

Get instant alerts when new vulnerabilities affect icinga-powershell-framework - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.11.21.12.0 ≤ v < 1.12.41.13.0 ≤ v < 1.13.4
v < 1.11.2v < 1.12.4v < 1.13.4
Affected range stops below 1.11.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.12.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.13.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusANALYZED
CWE
CWE-276NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card