{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24413 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-24413 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-24413 in the wild and no public exploit code.\n\nAffected product: icinga2. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-24413/ (Markdown: https://insights.sbomify.com/CVE-2026-24413/index.md)","id":"CVE-2026-24413","markdown":"https://insights.sbomify.com/CVE-2026-24413/index.md","name":"CVE-2026-24413","record":{"aliases":["UBUNTU-CVE-2026-24413","openSUSE-SU-2026:10113-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Icinga monitoring system","requires_auth":"low_privilege","summary":"Local users can read sensitive private keys and configuration files due to insecure folder permissions in Icinga 2 on Windows.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga","vendor":"icinga"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"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.","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Icinga has insecure permission of %ProgramData%\\icinga2\\var on Windows","id":"CVE-2026-24413","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"Icinga for Windows certificate can have too-open permissions","id":"CVE-2026-24414"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.15.2-1.1"],"introduced":["0"],"last_affected":[],"package":"icinga2","purl":"pkg:rpm/opensuse/icinga2\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2026:10113-1"}],"prev":{"headline":"iccDEV has Heap Buffer Overflow in icCurvesFromXml()","id":"CVE-2026-24412"},"products":["icinga2"],"published":"2026-01-29","related":[{"cvss_score":9.3,"headline":"Icinga 2 certificate renewal might incorrectly renew an invalid certificate","id":"CVE-2025-48057","kev_date_added":null,"published":"2025-05-27"},{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-29663","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.3,"headline":"Icinga Director configuration is susceptible to Cross-Site Request Forgery","id":"CVE-2024-24820","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-6535","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2020-14004","kev_date_added":null,"published":"2020-06-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-6533","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16882","kev_date_added":null,"published":"2017-11-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-29","vendors":["Icinga"]},"summary":"Local users can read sensitive private keys and configuration files due to insecure folder permissions in Icinga 2 on Windows.","url":"https://insights.sbomify.com/CVE-2026-24413/"}