Pi-hole Security Update: Change Your Password If You Ever Shared a Debug Log (FTL v6.9 and Core v6.6)

Pi-hole's November 11, 2026 release fixes four high-severity flaws and a debug log that leaked the admin password hash and two-factor secret. Here is who should change their password, how to update on a Pi or in Docker, and the regex change that can alter what your filters block.

Updated on
Pi-hole Security Update: Change Your Password If You Ever Shared a Debug Log (FTL v6.9 and Core v6.6)

Last updated: November 18, 2026

This guide is for anyone running Pi-hole on a Raspberry Pi, a Linux box or in Docker. It covers what Pi-hole's November 11, 2026 release of FTL v6.9 and Core v6.6 fixes, why anyone who has ever uploaded a Pi-hole debug log should change their password and re-enroll two-factor authentication, how to update (including the Docker tag), and the one regex change that can alter which domains your filters block. Details were checked on November 18, 2026 against Pi-hole's release post and update documentation. If you are setting Pi-hole up for the first time, start with our Pi-hole setup guide and come back here for the update.

Key Takeaways

  • Pi-hole FTL v6.9 and Core v6.6, released November 11, 2026, fix four High advisories (CVSS 7.2 to 7.3), one Medium and six Low. The web interface is unchanged at v6.6.1, and the Docker image is tagged 2026.11.0.
  • The Medium advisory is the one that reaches past your network: until this release, the pihole -d debug log, and therefore any tricorder upload of it, contained the admin password hash and the two-factor (TOTP) secret. Pi-hole's advice is to change your password and app password and set up 2FA again if you ever uploaded a debug log.
  • Update with pihole -up after a Teleporter backup. The bundled regex engine changed how {,n} is read, so check any custom regex filters after updating.

What did Pi-hole fix in FTL v6.9 and Core v6.6?

The release fixes eleven security advisories: four rated High, one Medium and six Low. The High advisories all require an attacker who already has admin access to the web interface or a shell on the host, so they matter most to households that share Pi-hole admin access or run it on a machine other people can log in to.

FTL is the Pi-hole engine that answers DNS queries and runs the web API; Core is the set of scripts (pihole -up, pihole -d, the installer) around it. A GHSA identifier is GitHub's security advisory number; Pi-hole published no CVE numbers for this release.

Advisory Component Severity (CVSS) What it allowed before the fix
GHSA-pj9m-9623-2g75 and GHSA-cq9w-mv93-mxh7 FTL and Core High (7.2) An admin could run commands as the pihole user through an unescaped files.gravity path. Pi-hole says to update both components.
GHSA-wp3p-45h3-2v82 Core High (7.3) The installer followed symlinks in /etc/pihole while writing files as root during pihole -r and pihole -up.
GHSA-5w4v-f65m-323f Core High (7.3) Root followed pihole-controlled paths during the macvendor.db download, pihole checkout and pihole uninstall.
GHSA-jvg9-fm8x-2jqq Core High (7.3) The pihole -d debug script followed symlinks. It now runs as the pihole user inside pihole-owned directories.
GHSA-qfq3-88xg-765w Core Medium (5.3) The debug log included the admin password hash and the TOTP secret, so a tricorder upload shared them.
GHSA-x6xh-vxcm-g8rm FTL Low (3.8) A limited session could list and end other sessions, including the admin's IP address and browser string.
GHSA-87wp-wm3p-8cxm FTL Low (3.7) IPv4 entries in webserver.acl were ignored on dual-stack ports such as +80.
GHSA-cg4p-5r3r-m54p, GHSA-fj2f-pgf2-j888, GHSA-9mh9-95wj-4w4q, GHSA-9hh4-j8jf-6c96 FTL Low (2.2 to 3.1) A password change racing a config write could leave the old password valid; queries could be stored after privacy level was lowered; two crashes reachable only with a valid session.

Why should I change my Pi-hole password if I uploaded a debug log?

Because every debug log generated before Core v6.6 contained your admin password hash and, if you use two-factor authentication, the TOTP secret that generates your codes. Anyone who received that log, or anyone who later obtains a copy of a tricorder upload, holds enough to attack the password offline and to generate valid 2FA codes.

The pihole -d command collects system information into a debug log, and the tricorder option uploads that log to Pi-hole's servers so a volunteer can read it when you ask for help on the forum. A password hash is a one-way scrambled form of the password; it cannot be read directly, but a weak or reused password can be recovered from it by guessing. A TOTP secret is the shared key behind the six-digit codes in your authenticator app; whoever has it can produce the same codes. Pi-hole's release post puts the advice in one sentence: "If you have uploaded a debug log, consider changing your password and app password and setting up 2FA again."

  1. Update first, so the new debug script no longer records the secrets.
  2. Change the web interface password from a shell with sudo pihole setpassword, or use the password setting in the web interface under Settings.
  3. If you created an app password for scripts or Home Assistant, generate a new one and update whatever uses it.
  4. If you use 2FA, turn it off and set it up again so a new TOTP secret is issued, then remove the old entry from your authenticator app.
  5. If the same password is used anywhere else, change it there too.

If you have never run pihole -d, or ran it and kept the log on your own machine, the exposure is limited to anyone who could read that file. Changing the password is still cheap insurance.

How do I update Pi-hole to FTL v6.9 and Core v6.6?

On a standard install, run sudo pihole -up. Pi-hole's update documentation says to read the release notes first, and the release post recommends a Teleporter backup before updating.

  1. Back up: in the web interface go to Settings, then Teleporter, and download the archive, or run sudo pihole-FTL --teleporter from a shell.
  2. Update: run sudo pihole -up. Core v6.6 now drops from root to the pihole user with setpriv instead of sudo, but Pi-hole says admin commands such as pihole -up still need to run as root.
  3. Confirm: run pihole -v. The output should show Core v6.6, FTL v6.9 and Web v6.6.1.
  4. Then do the password and 2FA steps above.

On Docker, pull the image tagged 2026.11.0 and recreate the container as you normally would. Pi-hole's update page points Docker users to its Docker upgrading guide and to the docker-pi-hole release notes on GitHub for container-specific changes; the release post lists no Docker changes beyond the new tag.

Will the update change what my Pi-hole blocks?

It can, if you use custom regex filters with a bounded repetition written as {,n}. FTL v6.9 updates its bundled TRE regex engine, and Pi-hole says the update "changes how some stored regex filters match": {,n} and {,} now mean {0,n} and {0,}, more than three nested approximate-matching groups are rejected, and a back-reference inside an unbounded repetition is rejected.

A regex filter is a pattern that matches many domains at once, such as every subdomain of an ad network. After updating, open Domains in the web interface, review each regex entry, and test a few domains against them with pihole-FTL regex-test or the Query Log. Standard domain blocklists are not affected. Two other behavior changes to know about: IPv4 entries in webserver.acl now apply on every port, and an IPv6 entry of [::]/0 no longer admits IPv4 clients, so a Pi-hole whose admin page was reachable by IPv4 only through that rule needs an explicit IPv4 entry.

What else is new in FTL v6.9 and Core v6.6?

Beyond the security fixes, the release updates the embedded dnsmasq to v2.93+42 and SQLite to v3.54.1, speeds up regex matching, and stops reopening gravity.db unless it changed on disk, which Pi-hole says was most of FTL's idle CPU use. Quad9's unfiltered upstream is now labelled as validating DNSSEC, which matters if you switched to Quad9 after Mullvad shut down its public DNS this month.

  • Fixes for a webserver spinning at 100 percent CPU, a lock held up to 300 seconds after a TCP worker fork, and a malformed password hash leaking memory on each login attempt.
  • Partial domain searches now find ABP-style (Adblock Plus syntax) entries.
  • The installer and update scripts no longer write into /etc/pihole as root, and the unneeded CAP_IPC_LOCK capability was removed.
  • Logs are now rotated by the system's daily logrotate rather than a nightly forced run.
  • Entries in dns.cnameRecords with invalid names or out-of-range TTLs are rejected, and requests with more than 64 headers are refused.

Why a DNS filter is worth keeping patched

Pi-hole sits in the path of every DNS lookup on your network, which is what makes it useful for blocking trackers and for spotting a compromised device calling home. It is also what makes its admin password worth protecting: an attacker who controls your resolver can redirect any domain. Keep Pi-hole updated, keep its admin page off the internet (no port forward, no remote management), and give it a password that is not used anywhere else. The same logic applies to the router in front of it. A router whose firmware you control is the second half of a private DNS setup, and our routers as the riskiest device of 2026 explainer covers why ISP gateways with vendor-managed firmware are the weak point.

One more monthly fee to kill

Renting your modem? That's $120+ a year.

Own it instead. It pays for itself in months. 90-day warranty and 30-day returns.

Pick your provider:

FAQ

Is my Pi-hole at risk if nobody else has admin access?

The four High advisories need an attacker who already has admin access or a shell on the host, so a single-user Pi-hole on a trusted network is at low risk from them. The debug-log advisory is different: it depends on who has a copy of a log you generated, not on who can reach your Pi-hole today.

Do I need to update if I never uploaded a debug log?

Yes. The release also fixes the High advisories, a webserver CPU spin, a memory leak on failed logins and several dnsmasq memory-safety issues. Updating takes a few minutes with pihole -up.

Which Pi-hole versions are fixed?

Core v6.6 and FTL v6.9, released November 11, 2026. The web interface stays at v6.6.1. The Docker image is tagged 2026.11.0.

Does this release have CVE numbers?

No. Pi-hole published GitHub Security Advisory (GHSA) identifiers and CVSS scores but no CVE numbers as of November 18, 2026.

Why did my regex filter stop matching after the update?

FTL v6.9 updated its regex engine. A bound written as {,n} now means {0,n}, deeply nested approximate groups are rejected, and a back-reference inside an unbounded repetition is rejected. Edit the pattern and test it with pihole-FTL regex-test.

Do I still need sudo installed for Pi-hole?

Core v6.6 switches its root-to-pihole privilege drop from sudo to setpriv, so sudo is no longer a requirement of Pi-hole itself. Admin commands such as pihole -up still have to be run as root.

Where do I report a Pi-hole security issue?

Through GitHub's security advisory process on the relevant Pi-hole repository, which is how the reporters credited in this release filed theirs. Do not post exploit details on the public forum.

Sources and how this article was reported

Advisory identifiers, severity scores, descriptions, the debug-log advice, the regex and ACL behavior changes and the update instructions come from Pi-hole's release post and update documentation, read on November 18, 2026. We did not read the individual GHSA advisory pages or the Docker upgrading guide, and we did not test the update on our own hardware for this article. The pihole setpassword and pihole -v commands are long-standing Pi-hole commands and were not re-tested for this article. We did not contact the Pi-hole project. ModemGuides sells refurbished modems and routers and publishes a Pi-hole setup guide.

USA-Based Modem & Router Technical Support Expert

Our entirely USA-based team of technicians each have over a decade of experience in assisting with installing modems and routers. We are so excited that you chose us to help you stop paying equipment rental fees to the mega-corporations that supply us with internet service.

Updated on

Leave a comment

Please note, comments need to be approved before they are published.