Root process interruption via writable PID file
Published Oct 16, 2025 · Updated Oct 16, 2025
Privilege escalation in affected Icinga 2 releases allows local users controlling the daemon account to signal arbitrary root processes. The safe-reload script and logrotate postrotate hook read a daemon-writable PID file, then invoke kill as root with that untrusted process ID. Access to the Icinga service account and execution of a reload or log rotation are required; impact is limited to SIGHUP or SIGUSR1 delivery.
Summary
What happened
Privilege escalation in affected Icinga 2 releases allows local users controlling the daemon account to signal arbitrary root processes. The safe-reload script and logrotate postrotate hook read a daemon-writable PID file, then invoke kill as root with that untrusted process ID. Access to the Icinga service account and execution of a reload or log rotation are required; impact is limited to SIGHUP or SIGUSR1 delivery.
The record
- CVE
- CVE-2025-61909
- Published
- Oct 16, 2025
- Updated
- Oct 16, 2025
- Vendor
- Icinga
- Product
- Icinga 2
- Classifications
- CWE-250, T1489
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 16, 2025CVE publishedPublication date reported by the CVE source.
- Oct 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>=2.10.0, < 2.13.13
- Affected versionversion=>=2.14.0, < 2.14.7
- Affected versionversion=>=2.15.0, < 2.15.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo