CVE-2026-65964: Pi-hole FTL: Log injection in webserver access-log writer chains to remote code execution via Lua-server-page evaluation

Published Nov 17, 2026
·
Updated

Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to 6.7, loghttpaccess 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 luaserverpagepattern, 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.

Affected Software

1 affected component
Pi-hole FTL<6.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Pi-hole FTL to a version that resolves this vulnerability.

    Fixed in 6.7

Event History

Nov 17, 2026
CVE Published
via MITRE·08:57 PM
Data Sourced
via MITRE·08:57 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to remote code execution?

Remote code execution requires debug.api to be enabled and files.log.webserver to be configured inside webserver.paths.webroot with a filename that matches lua_server_page_pattern. Deployments where the access log is not served by the Lua handler do not meet the described RCE condition, though they remain exposed to log forgery and downstream log-parser injection.

2

What does an attacker need to exploit the remote code execution path?

An attacker only needs to send an unauthenticated HTTP request containing Lua markup in the User-Agent header, then cause a later request to reach the planted log through CivetWeb's Lua server-page evaluation. No authentication is required for the request that injects the log content.

3

What privileges would successful code execution have?

Commands execute as the pihole operating-system user. They can access or modify pihole-owned configuration, credentials, databases, logs, and rendered interface content.

4

What can be done before upgrading?

Disable debug.api and ensure files.log.webserver is not placed under webserver.paths.webroot with a filename matching lua_server_page_pattern. If the log is not handled as a Lua server page, the described RCE chain is prevented, although unneutralized log entries can still enable log forgery or affect downstream log parsers.

5

Which version contains the fix?

The issue is fixed in Pi-hole FTL version 6.7. The affected condition is described as applying prior to 6.7.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203