Skip to main content

Ftl CVE-2026-35521

| EUVDEUVD-2026-19715 HIGH
OS Command Injection (CWE-78)
2026-04-07 GitHub_M
8.8
CVSS 3.1 · Vendor: GitHub_M
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to Pi-hole FTL API
  2. Exploit
    Inject newline characters in dhcp.hosts parameter
  3. Execution
    Inject dnsmasq configuration directives
  4. Impact
    Execute arbitrary system commands

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK

2 techniques across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Authenticated attacker with access to Pi-hole FTL Web interface versions 6.0–6.5. Attacker must modify the DHCP hosts configuration parameter (dhcp.hosts) to inject newline characters and arbitrary dnsmasq directives, achieving command execution on the host system.

Impact

The CVSS score of 8.8 reflects critical impact across confidentiality, integrity, and availability with straightforward network-based exploitation requiring only low-privilege authentication. However, real-world risk assessment reveals nuanced prioritization factors. The PR:L (low privilege required) vector indicates attackers need valid Pi-hole administrative credentials, substantially reducing the attack surface compared to unauthenticated vulnerabilities. EPSS data was not provided, but the combination of high technical impact (full system compromise) and low attack complexity suggests elevated exploitation probability once credentials are obtained. No public exploit code exists and the vulnerability is not listed in CISA KEV, indicating no confirmed active exploitation campaigns at analysis time. The primary risk scenario involves credential compromise through phishing, credential stuffing, or lateral movement in already-breached networks where Pi-hole instances serve as pivot points. Environments with single-administrator Pi-hole deployments face lower immediate risk than multi-user configurations or managed service scenarios. The SSVC framework assessment would likely categorize this as 'attend' priority rather than 'immediate' given the authentication prerequisite, though organizations using Pi-hole in production network infrastructure should prioritize patching due to the complete system compromise potential.

Exploit ScenarioDerived

An attacker who has obtained valid Pi-hole administrative credentials through phishing or password reuse accesses the web interface and navigates to the DHCP configuration settings. They add a malicious DHCP host entry containing an embedded newline character followed by a dnsmasq directive such as 'dhcp-script=/tmp/payload.sh' where payload.sh contains a reverse shell or credential harvesting script. When FTL processes this configuration and reloads dnsmasq, the injected directive executes the attacker's script with elevated privileges, granting complete system control. The attacker then establishes persistence, exfiltrates DNS query logs containing network intelligence, and potentially pivots to other network segments using the compromised Pi-hole as a foothold in the infrastructure.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 07, 2026

Remote code execution in Pi-hole FTL engine versions 6.0 through 6.5 allows authenticated attackers to execute arbitrary system commands by injecting malicious dnsmasq configuration directives through newline characters in the DHCP hosts configuration parameter. Exploitation requires low-complexity network access with low-level authentication (CVSS 8.8, AV:N/AC:L/PR:L). No public exploit identified at time of analysis, though the vulnerability's straightforward injection mechanism and the popularity of Pi-hole as a DNS/DHCP solution elevate practical risk for environments with multiple administrative users or compromised credentials.

RemediationAI

Immediately upgrade Pi-hole FTL to version 6.6 or later, which contains input validation fixes that properly sanitize newline characters in the dhcp.hosts configuration parameter. The vendor-released patch in version 6.6 addresses the underlying command injection vulnerability by implementing strict input filtering and escaping mechanisms for DHCP configuration entries. Administrators should access the GitHub security advisory at https://github.com/pi-hole/FTL/security/advisories/GHSA-vfmq-jrx3-wv3c for upgrade instructions and release notes. As a temporary risk mitigation measure for environments unable to immediately patch, restrict administrative access to the Pi-hole interface through network segmentation, implement multi-factor authentication if supported by deployment configuration, audit existing DHCP host entries for suspicious newline characters or unexpected configuration directives, and monitor FTL process execution for anomalous child processes. However, these workarounds do not eliminate the vulnerability and should only serve as interim controls pending upgrade to version 6.6.

Affected VersionsENISA

FTL 6.0, < 6.6

Affected Packages

euvd ftl_6_0 fix: 6.6

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Pi-hole FTL (Faster Than Light DNS) serves as the core DNS and DHCP engine for Pi-hole network-wide ad blocking systems, interfacing directly with dnsmasq for DNS/DHCP services. This vulnerability exploits CWE-78 (OS Command Injection) through insufficient input sanitization in the dhcp.hosts configuration parameter processing. When FTL translates user-supplied DHCP host entries into dnsmasq configuration directives, newline characters are not properly escaped or validated, allowing attackers to break out of the intended configuration context. By injecting newline-delimited dnsmasq directives such as 'dhcp-script=' or 'conf-file=', an authenticated attacker can specify arbitrary shell scripts to be executed with the privileges of the FTL process, which typically runs with elevated system permissions to manage network services. The affected product is specifically cpe:2.3:a:pi-hole:ftl:*:*:*:*:*:*:*:* covering the FTL component rather than the broader Pi-hole web interface.

Know when Ftl gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Analysis Updated
Apr 16, 2026 - 06:04 EUVD-patch-fix
executive summary
Patch available
Apr 16, 2026 - 05:29 EUVD
6.6
CVE Published
Apr 07, 2026 - 15:20 nvd
HIGH 8.8

DescriptionCVE.org

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 DHCP hosts configuration parameter (dhcp.hosts). 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.

Executive ViewAI

Why It Matters

Pi-hole FTL versions 6.0-6.5 contain a remote code execution vulnerability allowing authenticated users to execute arbitrary system commands through DHCP configuration injection, directly compromising DNS/DHCP infrastructure integrity. Organizations operating Pi-hole in multi-admin environments or with credential exposure face immediate risk of complete DNS poisoning, network redirection, and potential lateral movement.

Business Impact: High
Compensating Controls

Apply vendor patch. Interim mitigations if patching is delayed: (1) Restrict DHCP hosts configuration access to single trusted administrator account; (2) Implement network segmentation to limit Pi-hole admin interface exposure; (3) Enable comprehensive audit logging of all configuration changes; (4) Monitor DNS query patterns for anomalous redirects or command execution indicators.

Threat Intelligence Overview

EPSS Score
0.3%
Top 50% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

OS command injection occurs when an application passes unsanitized user input directly into system shell commands.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy