CVE-2026-41489: Pi-hole: Local privilege escalation via config-controlled path in root-executed service hooks
Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. From 6.0 to before Core 6.4.2 and FTL 6.6.1, two shell scripts executed as root by systemd (pihole-FTL-prestart.sh and pihole-FTL-poststop.sh) read the files.pid path from this config without validation and use it in privileged file operations (install and rm -f). By writing an arbitrary path into files.pid, an attacker with pihole privilege can cause root to delete and then recreate any file on the system outside the ProtectSystem=full-restricted directories, gaining write access to it. On a default Pi-hole installation this yields local privilege escalation to root via SSH authorized keys manipulation. If /root/.ssh/authorizedkeys does not exist (default on fresh installs), only ExecStartPre is required. If the file exists, ExecStopPost deletes it first, and the same restart triggers both hooks in sequence. This vulnerability is fixed in Core 6.4.2 and FTL 6.6.1.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41489?
CVE-2026-41489 has been rated as a high severity vulnerability due to its potential for privilege escalation.
How do I fix CVE-2026-41489?
To fix CVE-2026-41489, users should upgrade Pi-hole to versions 6.4.2 or higher for Core and 6.6.1 or higher for FTL.
What versions of Pi-hole are affected by CVE-2026-41489?
CVE-2026-41489 affects Pi-hole versions from 6.0 up to but not including 6.4.2 for Core and 6.6.1 for FTL.
What type of vulnerability is CVE-2026-41489?
CVE-2026-41489 is a shell script vulnerability that allows execution of scripts with elevated privileges.
What is the impact of CVE-2026-41489 on my systems?
The impact of CVE-2026-41489 may include unauthorized access to system resources and the ability to execute code with root privileges.