# CVE-2026-24414: Icinga for Windows certificate can have too-open permissions

> Local users can read private keys due to overly permissive directory permissions, exposing sensitive monitoring credentials.

- **Severity:** Medium 6.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026

## What is CVE-2026-24414?

CVE-2026-24414 is a medium-severity vulnerability in icinga-powershell-framework, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2026-24414?

It affects 1 product.


Products: Icinga Icinga Powershell Framework.

## How do I fix CVE-2026-24414?

No fix has been published for CVE-2026-24414 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24414 being exploited?

There is no known exploitation of CVE-2026-24414 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24414 and fix it if it is affected.

What it is: CVE-2026-24414 is a medium-severity vulnerability in icinga-powershell-framework, published on 29 Jan 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-24414 in the wild and no public exploit code.

Affected product: icinga-powershell-framework. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24414/ (Markdown: https://insights.sbomify.com/CVE-2026-24414/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24414
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24414
- OSV: https://osv.dev/vulnerability/CVE-2026-24414

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24414/
Summaries are generated and may contain mistakes; the official description above is the record.