# CVE-2026-24413: Icinga has insecure permission of %ProgramData%\icinga2\var on Windows

> Local users can read sensitive private keys and configuration files due to insecure folder permissions in Icinga 2 on Windows.

- **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:** Yes
- **Published:** 29 Jan 2026
- **Updated:** 29 Jan 2026
- **Also known as:** UBUNTU-CVE-2026-24413, openSUSE-SU-2026:10113-1

## What is CVE-2026-24413?

CVE-2026-24413 is a medium-severity vulnerability in icinga2, 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

Icinga 2 is an open source monitoring system. Starting in version 2.3.0 and prior to versions 2.13.14, 2.14.8, and 2.15.2, the Icinga 2 MSI did not set appropriate permissions for the `%ProgramData%\icinga2\var` folder on Windows. This resulted in the its contents - including the private key of the user and synced configuration - being readable by all local users. All installations on Windows are affected. Versions 2.13.14, 2.14.8, and 2.15.2 contains a fix. There are two possibilities to work around the issue without upgrading Icinga 2. Upgrade Icinga for Windows to at least version v1.13.4, v1.12.4, or v1.11.2. These version will automatically fix the ACLs for the Icinga 2 agent as well. Alternatively, manually update the ACL for the given folder `C:\ProgramData\icinga2\var` (and `C:\Program Files\WindowsPowerShell\modules\icinga-powershell-framework\certificate` to fix the issue for the Icinga for Windows 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-24413?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `icinga2` | openSUSE:Tumbleweed | All versions | 2.15.2-1.1 |

Products: Icinga Icinga.

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

Upgrade to a fixed version.

## Is CVE-2026-24413 being exploited?

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

## Other vulnerabilities in icinga2

- [CVE-2025-48057](https://insights.sbomify.com/CVE-2025-48057/): Icinga 2 certificate renewal might incorrectly renew an invalid certificate (critical 9.3)
- [CVE-2020-29663](https://insights.sbomify.com/CVE-2020-29663/): Security feature bypass in n/a (critical 9.1)
- [CVE-2024-24820](https://insights.sbomify.com/CVE-2024-24820/): Icinga Director configuration is susceptible to Cross-Site Request Forgery (high 8.3)
- [CVE-2018-6535](https://insights.sbomify.com/CVE-2018-6535/): Information disclosure in n/a (high 8.1)
- [CVE-2020-14004](https://insights.sbomify.com/CVE-2020-14004/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24413 is a medium-severity vulnerability in icinga2, 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-24413 in the wild and no public exploit code.

Affected product: icinga2. 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-24413/ (Markdown: https://insights.sbomify.com/CVE-2026-24413/index.md)
```

## Sources

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

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