{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-24414 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-24414 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-24414 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-24414 in the wild and no public exploit code.\n\nAffected product: icinga-powershell-framework. 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-24414/ (Markdown: https://insights.sbomify.com/CVE-2026-24414/index.md)","id":"CVE-2026-24414","markdown":"https://insights.sbomify.com/CVE-2026-24414/index.md","name":"CVE-2026-24414","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Icinga monitoring agent","requires_auth":"low_privilege","summary":"Local users can read private keys due to overly permissive directory permissions, exposing sensitive monitoring credentials.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga_powershell_framework","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":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Icinga for Windows certificate can have too-open permissions","id":"CVE-2026-24414","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"OpenSTAManager affected by reflected XSS in modifica_iva.php via righe parameter","id":"CVE-2026-24415"},"packages":[],"prev":{"headline":"Icinga has insecure permission of %ProgramData%\\icinga2\\var on Windows","id":"CVE-2026-24413"},"products":["icinga-powershell-framework"],"published":"2026-01-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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 private keys due to overly permissive directory permissions, exposing sensitive monitoring credentials.","url":"https://insights.sbomify.com/CVE-2026-24414/"}