CVE
FTL remote code execution via CivetWeb configuration injection
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
- Exploited
- No known exploitation
- Fix
- Fixed in 6.7
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Pi-hole FTL v6.6.2 is affected The webserver.advancedOpts setting accepts arbitrary CivetWeb options, including lua_* options, with no filtering The Teleporter import writes a dhcp.leases archive entry to disk without content validation
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Pi-hole FTL, the core engine of the Pi-hole network-level ad and tracker blocker, lets a remote attacker with administrator login run arbitrary commands as the pihole operating-system user. The attacker does this by placing a crafted file on disk through the teleporter feature and then changing the web server's advanced options so that FTL runs that file as Lua code, and the commands keep running across restarts while the configuration and file remain.
Written by a model from the sources below. Verify against them.
Original description
Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.6.2 until 6.7, PATCH /api/config accepts unfiltered CivetWeb lua_* options through webserver.advancedOpts, while POST /api/teleporter writes attacker-controlled content from a dhcp.leases archive entry through src/zip/teleporter.c without content validation. An authenticated administrator can place controlled file content on disk, point a Lua execution option at that file, and rely on the advancedOpts configuration change to restart FTL. CivetWeb then executes the file as Lua through the processing in src/webserver/webserver.c, allowing arbitrary commands to run as the pihole operating-system user and persist across restarts while the configuration and file remain. This issue is fixed in version 6.7.
Who should check
Teams running Pi-hole FTL 6.6.2 whose admins use the web API PATCH /api/config and POST /api/teleporter
“Affected component: Pi-hole FTL v6.6.2”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Pi-hole FTL v6.6.2 is affected The webserver.advancedOpts setting accepts arbitrary CivetWeb options, including lua_* options, with no filtering The Teleporter import writes a dhcp.leases archive entry to disk without content validationUpgrade to a fixed version: 6.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-65963 (Pi-hole FTL: Remote Code Execution (RCE) via CivetWeb Configuration Injection), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-65963 (entry last updated 2026-11-17):
Affected:
- pi-hole FTL: from 6.6.2, fixed in 6.7
Fixed versions: 6.7.
Conditions (all must be true for the bug to be hit):
- Pi-hole FTL v6.6.2 is affected (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-8j7w-m3cr-6q6x)
- The webserver.advancedOpts setting accepts arbitrary CivetWeb options, including lua_* options, with no filtering (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-8j7w-m3cr-6q6x)
- The Teleporter import writes a dhcp.leases archive entry to disk without content validation (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-8j7w-m3cr-6q6x)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-65963 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-65963 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pi-hole/FTL/security/advisories/GHSA-8j7w-m3cr-6q6x
- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/eb6ca080666788e16cd9405fd5899536d66c4947
- https://github.com/pi-hole/FTL/releases/tag/v6.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-65963
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-65963"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- pi-hole FTL
From 6.6.2 · fixed in 6.7
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-65963
Is CVE-2026-65963 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An authenticated admin can execute arbitrary commands on the Pi-hole server. The webserver.advancedOpts setting accepts arbitrary CivetWeb options, including lua_* options, with no filtering, and the Teleporter import writes a dhcp.leases archive entry to /etc/pihole/dhcp.leases without content validation.Source: github.com
Which versions are affected by CVE-2026-65963?
FTL: from 6.6.2 before 6.7.Source: cve.now feed data
Am I affected, and how do I check?
The advisory names Pi-hole FTL v6.6.2 as affected, and the affected range starts at 6.6.2 and ends before 6.7. Check the installed FTL version against that range, and check whether the webserver.advancedOpts setting is in use, since that setting is part of the flaw.Source: github.com
How do I fix CVE-2026-65963?
Upgrade Pi-hole FTL to 6.7 or later, which is the fixed version in the affected range.Source: github.com