Approved changes feed: RSS · Atom

cpe:2.3:a:icinga:icinga_powershell_framework:*:*:*:*:*:*:*:*

part: a version: * update: *

VendorIcinga (f3c2076d-deab-53f8-8d1d-6154f519c3cc)
ProductIcinga Powershell Framework (a92e1a9b-0c46-5b12-9b4e-3be0c7ec0cea)
Edition*
Language*
Software edition*
Target software*
Target hardware*
Other*
NotesImported from purl2cpe mapping

PURL mappings

PURLSourceLast updated
pkg:github/icinga/icinga-powershell-framework purl2cpe 2026-06-01 10:11:14.148293

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-24414 vulnerable 2026-06-03 15:16:52.435936 Icinga for Windows certificate can have too-open permissions
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.
Published: 2026-01-29T17:35:43.323Z
Updated: 2026-01-29T21:17:16.794Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.