{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-61909 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-61909 is a medium-severity vulnerability in icinga2, published on 16 Oct 2025. 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-2025-61909 and fix it if it is affected.\n\nWhat it is: CVE-2025-61909 is a medium-severity vulnerability in icinga2, published on 16 Oct 2025. 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-2025-61909 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-2025-61909/ (Markdown: https://insights.sbomify.com/CVE-2025-61909/index.md)","id":"CVE-2025-61909","markdown":"https://insights.sbomify.com/CVE-2025-61909/index.md","name":"CVE-2025-61909","record":{"aliases":["DEBIAN-CVE-2025-61909","GHSA-pg6g-g99v-mw46","UBUNTU-CVE-2025-61909"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Icinga 2 monitoring system","requires_auth":"high_privilege","summary":"A local attacker with Icinga daemon privileges can escalate to root by sending signals to arbitrary processes via a writable PID file.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga","vendor":"icinga"}],"cvss":{"score":4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:N/SC:N/SI:N/SA:H","version":"4.0"},"cwes":[{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"Icinga 2 is an open source monitoring system. From 2.10.0 to before 2.15.1, 2.14.7, and 2.13.13, the safe-reload script (also used during systemctl reload icinga2) and logrotate configuration shipped with Icinga 2 read the PID of the main Icinga 2 process from a PID file writable by the daemon user, but send the signal as the root user. This can allow the Icinga user to send signals to processes it would otherwise not permitted to. A fix is included in the following Icinga 2 versions: 2.15.1, 2.14.7, and 2.13.13.","ecosystems":[],"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 2 signals sent as root to processes based on PID file written by the Icinga 2 daemon user","id":"CVE-2025-61909","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"NASA ION-DTN BPv7 4.1.3s Uncontrolled Memory Allocation that leads to Denial-of-Service","id":"CVE-2025-61910"},"packages":[],"prev":{"headline":"Icinga 2 Denial of Service (DoS) By Dereferencing Invalid Reference","id":"CVE-2025-61908"},"products":["icinga2"],"published":"2025-10-16","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":"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":"2025-10-16","vendors":["Icinga"]},"summary":"A local attacker with Icinga daemon privileges can escalate to root by sending signals to arbitrary processes via a writable PID file.","url":"https://insights.sbomify.com/CVE-2025-61909/"}