Stack Watch
Self-hosted update briefs — is it safe to update, or wait?
Disclaimer: Automated heuristics over public release notes and vulnerability databases (OSV / NVD). Can be wrong or incomplete. Always back up first and validate upgrades yourself. Stack Watch does not invent CVE IDs or issue counts. This is an MVP research project, not a live paid service.
Home / Pi-hole / v6.4

Pi-hole v6.4

SAFE

No breaking/security/wait signals detected in release notes heuristics.

Published: 2026-02-17T20:27:27Z · GitHub release

Summary of changes

## What's Changed - Remove wget from alpine dependencies by @darkexplosiveqwx in #6484 - Remove custom FTL FirewallD zone checks from debug log by @rdwebdesign in #6481 - Add Alpine 3.23 to test suite by @yubiuser in #6488 - Debug log - Add colors to gravity tables by @rdwebdesign in #6485 - Use configured location for web repo when updating or repairing by @rrobgill in #6470 - Add missing -g to the message in gravity recovery command by @rdwebdesign in #6513 - Don't install unused /usr/local/share/man/man5 by @darkexplosiveqwx in #6526 Full Changelog: v6.3...v6.4

Breaking changes

None detected by heuristics.

CVEs linked to this release

None linked from release notes or OSV fixed-in match.

Linked issues / PRs mentioned

7

Back up first

Always back up first. Stack Watch briefs are automated heuristics over public release notes and vulnerability databases. They can be wrong or incomplete. You are responsible for validating upgrades in your own environment. We never invent CVE IDs or issue counts — if a number is missing, it was not found.