CVE-2026-24414
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Icinga PowerShell Framework versions prior to 1.13.4, 1.12.4, and 1.11.2 expose private keys for Icinga certificates due to overly permissive file system ACLs on the certificate directory, allowing any local user to read sensitive cryptographic material.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.11.2>= 1.12.0, < 1.12.4>= 1.13.0, < 1.13.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Icinga PowerShell Framework versionRun 'Get-Module -ListAvailable Icinga' or check the module version via PowerShell with 'Import-Module Icinga; $module = Get-Module Icinga; $module.Version'Affected if The installed version is less than 1.11.2, or falls in the range >= 1.12.0 and < 1.12.4, or >= 1.13.0 and < 1.13.4
-
Locate the Icinga certificate directoryIdentify the directory where Icinga stores its certificate files and private keys, typically found in the Icinga installation or configuration data directoryAffected if The certificate directory exists on the system and contains certificate files
-
Inspect file system ACLs on the certificate directoryUse 'Get-Acl -Path "<certificate_directory>" | Format-List' to review the access control list, or use 'icacls "<certificate_directory>"' from command prompt to list all granted permissionsAffected if The ACLs grant Read permission to the 'Users' group, 'Everyone', or other non-privileged local accounts
-
Verify private key file permissionsCheck individual .key, .pem, or private certificate files within the directory using 'Get-Acl' or 'icacls' to confirm if read access is granted beyond the Icinga service account and administratorsAffected if Private key files are readable by standard user accounts or have overly permissive access granted to Users or Everyone
-
Confirm exposure by testing read access as a non-privileged userRun a command as a standard local user (not administrator) to attempt reading a private key file, such as 'Get-Content "<path_to_private_key>"'Affected if A standard non-privileged user account can successfully read the private key file contents
The environment is affected if the Icinga PowerShell Framework version is within any of the vulnerable ranges AND the certificate directory or its private key files have overly permissive ACLs allowing non-administrative users to read them.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.11.21.12.41.13.4
Upgrade to a fixed version (1.13.4, 1.12.4, or 1.11.2) or manually restrict ACLs on the certificate directory to limit access to only the Icinga service user and administrators.
Upgrade to 1.13.4 (or 1.12.4 or 1.11.2 depending on current version branch)
- 1. Identify the currently installed Icinga PowerShell Framework version by running `Get-Module -ListAvailable icinga-powershell-framework`
- 2. Determine which upgrade path applies based on current version: if < 1.11.2 upgrade to 1.11.2; if >= 1.12.0 and < 1.12.4 upgrade to 1.12.4; if >= 1.13.0 and < 1.13.4 upgrade to 1.13.4
- 3. Download the fixed version from the official Icinga repository (github.com/icinga/icinga-powershell-framework)
- 4. Install the new version using `Install-Module -Name icinga-powershell-framework -RequiredVersion <fixed_version> -Force` or via the Icinga Director
- 5. Verify the installation completed successfully and the module loads without errors
- 6. Alternatively (if immediate upgrade is not possible), manually restrict permissions: Right-click the folder `C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate`, select Properties > Security, remove 'Users' and 'Everyone' groups, add only the Icinga service account and Administrators with Full Control
- 7. Apply the same permission restrictions to `C:\ProgramData\icinga2\var` and all subfolders to address the related CVE-2026-24413
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24414 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24414 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data