Skip to main content

Ftl EUVDEUVD-2026-19711

| CVE-2026-35519 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 dns.hostRecord parameter
  3. Execution
    Inject dnsmasq directives
  4. Impact
    Execute arbitrary commands on system

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

Requires authenticated access to Pi-hole FTL API (versions 6.0-6.5). Attacker must inject newline characters into the dns.hostRecord configuration parameter to inject arbitrary dnsmasq directives and execute system commands.

Impact

The CVSS 8.8 score accurately reflects high severity with network attack vector (AV:N), low complexity (AC:L), and complete impact to confidentiality, integrity, and availability (C:H/I:H/A:H). However, the low-privilege authentication requirement (PR:L) provides meaningful defense-in-depth for properly secured deployments. Real-world risk depends heavily on organizational exposure: Pi-hole instances with weak admin credentials, shared administrative access, or internet-exposed management interfaces face immediate high risk. The vulnerability is classified as Command Injection and RCE in tags, confirming the critical nature. No EPSS probability data is available, but the straightforward exploitation path and clear advisory from GitHub Security suggest medium-to-high likelihood of weaponization once details spread. The lack of confirmed active exploitation (no KEV listing) and absence of public exploit code provides a window for remediation before widespread attacks. Organizations should prioritize patching based on their Pi-hole deployment model: internet-facing or multi-tenant environments warrant emergency response, while isolated home networks with strong authentication present lower immediate risk.

Exploit ScenarioDerived

An attacker with low-privilege authenticated access to a Pi-hole web interface navigates to the DNS host records configuration section and submits a malicious host record entry containing newline characters followed by dnsmasq directives such as 'conf-file=/tmp/malicious.conf' or direct exec statements. When FTL processes this configuration and reloads dnsmasq, the injected directives execute with the service's elevated privileges, allowing the attacker to execute arbitrary commands, establish persistence through cron jobs, exfiltrate network traffic data, or pivot to other systems on the network. In multi-user environments or deployments with compromised credentials, this provides a straightforward privilege escalation path from web interface access to full system compromise.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% 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 6.0 through 6.5 allows authenticated attackers to execute arbitrary commands via newline injection in DNS host record configuration. The vulnerability exploits improper input sanitization in the dns.hostRecord parameter, enabling injection of malicious dnsmasq directives that execute at the system level. With CVSS 8.8 (network-accessible, low complexity, requires low-privilege authentication), this represents a critical risk for Pi-hole deployments where administrative access controls are weak. No public exploit identified at time of analysis, though the attack vector is straightforward for authenticated users.

RemediationAI

Upgrade Pi-hole FTL to version 6.6 or later, which contains the complete fix for the newline injection vulnerability in DNS host record configuration. The vendor-released patch is available through standard Pi-hole update mechanisms using 'pihole -up' command or manual installation from the official Pi-hole repository. Organizations unable to immediately upgrade should implement compensating controls including restricting administrative access to the Pi-hole web interface to trusted networks only, enforcing strong authentication credentials for admin accounts, monitoring FTL logs for suspicious dnsmasq configuration changes, and implementing network segmentation to limit the blast radius of potential compromise. Complete remediation guidance and update procedures are documented in the GitHub Security Advisory at https://github.com/pi-hole/FTL/security/advisories/GHSA-wxhv-w77q-6qwp. No workarounds exist to fully mitigate the vulnerability without upgrading, as the flaw is architectural in the configuration parsing logic.

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) is the core DNS and DHCP engine powering Pi-hole network-wide ad blocking systems. The vulnerability stems from CWE-78 (OS Command Injection) in the DNS host record configuration interface. When authenticated users configure custom DNS host records through the dns.hostRecord parameter, FTL passes these values to the underlying dnsmasq daemon without proper sanitization of newline characters. An attacker can inject newline-delimited dnsmasq configuration directives, including exec statements or conf-file directives pointing to attacker-controlled configuration files. Since dnsmasq runs with elevated privileges to bind to port 53 and manage system DNS, any injected commands execute with the same privilege level as the FTL service. The affected product CPE cpe:2.3:a:pi-hole:ftl:*:*:*:*:*:*:*:* confirms this impacts the FTL component specifically across the 6.0-6.5 version range.

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:18 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 DNS host record configuration parameter (dns.hostRecord). 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 administrators to execute arbitrary system commands through DNS configuration manipulation. This vulnerability directly impacts any organization using Pi-hole for DNS filtering and threatens system integrity if administrative credentials are compromised or if access controls are inadequate.

Business Impact: High
Compensating Controls

Apply vendor patch. Interim mitigations pending patch deployment: (1) restrict network access to Pi-hole administrative interface to trusted IP ranges only; (2) enforce strong password policies for all administrative accounts; (3) disable remote web interface access if not required; (4) monitor DNS configuration changes through audit logging.

Threat Intelligence Overview

EPSS Score
0.2%
Top 58% 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.2%
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