CVE-2026-39849: Pi-hole FTL remote code execution via newline injection in dns.interface configuration
Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. In versions before 6.6.1, the dns.interface configuration field in Pi-hole FTL accepted newline characters without validation, allowing an attacker to inject arbitrary directives into the generated dnsmasq configuration file. On installations with no admin password set (the default for many deployments), the configuration API is fully accessible without credentials, allowing a network-adjacent attacker to inject the payload, enable the built-in DHCP server, and achieve arbitrary command execution on the host the next time any device on the network requests a DHCP lease. The injected value is persisted to /etc/pihole/pihole.toml and survives restarts. The strncpy in the code path limits the total interface field to 31 bytes, but payloads such as wlan0\ndhcp-script=/tmp/p fit within this constraint. The dnsmasq config validation introduced in FTL 6.6 only checks syntactic validity, so valid directives injected via newline pass validation successfully. This issue has been fixed in version 6.6.1.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Pi-hole FTLto a version that resolves this vulnerability.Fixed in 6.6.1 - Compensating control
Until Pi-hole FTL is upgraded to 6.6.1, restrict access to the Pi-hole FTL configuration API (e.g., via firewall/ACL) so a network-adjacent attacker cannot set dns.interface and inject directives.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39849?
CVE-2026-39849 is rated as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2026-39849?
To mitigate CVE-2026-39849, it is essential to upgrade Pi-hole FTL to version 6.6.1 or later.
What products are affected by CVE-2026-39849?
CVE-2026-39849 affects versions of Pi-hole FTL prior to 6.6.1.
What is the nature of the vulnerability in CVE-2026-39849?
CVE-2026-39849 involves a newline injection in the dns.interface configuration, leading to potential remote code execution.
Can CVE-2026-39849 be exploited remotely?
Yes, CVE-2026-39849 can be exploited remotely due to its nature of accepting newline characters in a configuration field.