Security readout for executives and security teams
Plain-English summary
On Windows, affected Icinga 2 installations stored sensitive runtime data in a folder readable by any local user. This may expose the agent private key and synced configuration. The issue requires local user access, so urgency depends on how tightly Windows hosts are controlled.
Executive priority
Prioritize remediation on Windows monitoring agents where multiple users can log in or where configuration secrets are sensitive. This is not a remote takeover issue based on current sources, but exposed monitoring keys and configuration can weaken trust in monitoring infrastructure.
Technical view
CVE-2026-24413 is a CWE-276 insecure permissions issue in the Icinga 2 MSI for Windows. Versions from 2.3.0 before 2.13.14, 2.14.0 before 2.14.8, and 2.15.0 before 2.15.2 expose contents under %ProgramData%\icinga2\var to all local users. CVSS v4.0 is 6.8, with local attack vector and high confidentiality impact.
Likely exposure
All Windows installations in the listed affected Icinga 2 version ranges are affected. Non-Windows installations are not described as affected in the provided sources. Exposure is most relevant on shared servers, jump hosts, or systems where untrusted users have local accounts.
Exploitation context
The sources do not report active exploitation, and the CVE is not marked in CISA KEV. Exploitation requires local low-privileged access and could allow reading sensitive Icinga material, including a private key and synced configuration. The sources do not indicate integrity or availability impact.
Researcher notes
The vulnerability is a Windows installer permissions flaw, not a protocol parsing issue. Key assessment points are installed Icinga 2 version, Windows deployment scope, ACL inheritance under the affected paths, and whether exposed private keys or configuration require rotation after remediation.
Mitigation direction
- Upgrade Icinga 2 to 2.13.14, 2.14.8, 2.15.2, or later as applicable.
- Alternatively upgrade Icinga for Windows to v1.13.4, v1.12.4, or v1.11.2 or later.
- If not upgrading, manually restrict ACLs on C:\ProgramData\icinga2\var and all child items.
- Also restrict the Icinga PowerShell Framework certificate folder if Icinga for Windows is present.
- Allow access only for the Icinga service user and administrators, per vendor guidance.
Validation and detection
- Inventory Windows hosts running Icinga 2 and record installed versions.
- Confirm whether versions fall within the affected ranges listed by Icinga.
- Inspect ACLs on C:\ProgramData\icinga2\var and child items for broad local-user read access.
- Check for Icinga for Windows and validate the PowerShell Framework certificate folder ACLs.
- After upgrade or ACL changes, recheck permissions and service functionality.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-276: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24413 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
6.8MediumVector: 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
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Icinga/icinga2/security/advisories/GHSA-vfjg-6fpv-4mmrCVE reference · x_refsource_CONFIRM
- https://github.com/Icinga/icinga-powershell-framework/security/advisories/GHSA-88h5-rrm6-5973CVE reference · x_refsource_MISC
- https://icinga.com/blog/releasing-icinga-2-v2-15-2-v2-14-8-v2-13-14-and-icinga-for-windows-v1-13-4-v1-12-4-v1-11-2CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Default Permissions
Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.