Software-update: Pi-hole Core 6.4 / Web 6.4.1 / FTL 6.5

Versie 6.4 van Pi-hole Core is uitgekomen. Ook zijn Pi-hole Web 6.4.1 en Pi-hole FTL 6.5 verschenen. Pi-hole is een advertising-aware dns- en webserver bedoeld om te draaien op een Raspberry Pi in het netwerk. Als op de router naar Pi-hole wordt verwezen voor dns-afhandelingen, zullen alle apparaten binnen het netwerk er automatisch gebruik van maken zonder dat er instellingen hoeven te worden aangepast. Vervolgens worden advertenties niet meer opgehaald, waardoor pagina's sneller laden. In potentie kan er ook malware mee buiten de deur worden gehouden. Voor meer informatie verwijzen we jullie door naar de uitleg en video's op deze pagina, deze handleiding van tweaker jpgview, of dit topic op ons forum. De releasenotes voor deze uitgave kunnen hieronder worden gevonden.

Pi-hole FTL v6.5, Web v6.4.1 and Core v6.4 Released!

As always, please read through the changelogs before updating with pihole -up

Don’t forget, you can use Teleporter to export your configuration. It can be found under the settings menu of the web interface or on the command line with pihole-FTL --teleporter

This release has also been tagged on Docker as 2026.02.0

Security fixes

Two security vulnerabilities in the web interface have been patched in this release.

Stored HTML Injection in Pi-hole Web Interface via Local DNS Records (CNAME/Hosts) in data-tag Attribute: fixed with d328f14Stored HTML Injection in Pi-hole Web Interface via X-Forwarded-For Header in Active Sessions Table: fixed with 1a0c6f4

Stored HTML Injection in Pi-hole Web Interface via Local DNS Records (CNAME/Hosts) in data-tag Attribute: fixed with d328f14

Stored HTML Injection in Pi-hole Web Interface via X-Forwarded-For Header in Active Sessions Table: fixed with 1a0c6f4

Performance improvements

Faster startup (FTL #2725): FTL now imports historical queries from the database asynchronously on startup. Previously, DNS resolution was blocked until the entire query history had been loaded into memory. Now, FTL begins accepting DNS queries immediately and imports history in a dedicated background thread. The garbage collector is held off until the import is complete to ensure data consistency.

Low-memory hardware optimizations (FTL #2757): A new database.forceDisk configuration option forces FTL’s in-memory SQLite3 database to live on disk instead of in RAM. This can notably reduce FTL’s memory footprint, which is beneficial on resource-constrained hardware such as older Raspberry Pi models. On NVMe-backed systems no measurable performance difference was observed, though some slowdown may be seen on slower storage.

Faster gravity updates (FTL #2710): Several cumulative efficiency gains have been applied to the main domain validation loop that runs during pihole -g. While each individual improvement is modest, they add up across every entry in your blocklists and allowlists:

A lookup table now validates domain characters using a single comparison per character, replacing multiple branching comparisonsIP address testing is short-circuited: IPv4 tests only run if the token starts with a digit, and IPv6 tests only run if a colon is present within the first 5 charactersThe unicode BOM check is now performed once per file rather than once per line

A lookup table now validates domain characters using a single comparison per character, replacing multiple branching comparisons

IP address testing is short-circuited: IPv4 tests only run if the token starts with a digit, and IPv6 tests only run if a colon is present within the first 5 characters

The unicode BOM check is now performed once per file rather than once per line

In testing with ~5 million domains across several lists, gravity update time dropped from ~27s to ~23s (roughly a 16% reduction in real time, and ~22% reduction in CPU time).

Source: Tweakers.net