CVE-2026-35518: pi-hole FTL · OS Command Injection
Affects pi-hole FTLSource CVE Database V5
Not known to be exploited · CVSS 8.8 High : upgrade to 6.6 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.6
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 7 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade FTL and pi-hole/FTL to 6.6.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pi-holeFTL | Affected
| Fixed in
|
GitHubpi-hole/FTLpkg:github/pi-hole/FTLOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Pi-hole FTL to version 6.6 or later, where this vulnerability is fixed. Since the vulnerability requires authentication, ensure that access to the Pi-hole administration interface is tightly controlled. Patch status is confirmed fixed in version 6.6; no other official remediation level is provided. Patch status is not explicitly stated in a vendor advisory here, but the description confirms the fix in 6.6.
Description
FTLDNS (pihole-FTL) provides an interactive API and also generates statistics for Pi-hole's Web interface. From 6.0 to before 6.6, the Pi-hole FTL engine contains a Remote Code Execution (RCE) vulnerability in the DNS CNAME records configuration parameter (dns.cnameRecords). This vulnerability allows an authenticated attacker to inject arbitrary dnsmasq configuration directives through newline characters, ultimately achieving command execution on the underlying system. This vulnerability is fixed in 6.6.