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.2

Pi-hole v6.4.2

UPDATE_WITH_CARE

Security-related language in release notes; update after a backup if you are affected.

Published: 2026-04-24T21:56:33Z · GitHub release

Summary of changes

## What's Changed - Wipe version file before creating a new one by @yubiuser in #6538 - Fix ownership permissions for containing directories in fix_owner_per… by @PromoFaux in #6589 - Remove reference to /usr/local/bin/COL_TABLE by @darkexplosiveqwx in #6594 - Skip apt cache update when pihole-meta is current by @PromoFaux in #6581 - Set versions in /etc/pihole/versions to null if script fails by @yubiuser in #6550 - Remove redundant touching of logfiles from systemd Service by @yubiuser in #6601 - Loosen requirements for local file access for gravity by @yubiuser in #6430 - Fix permission for *.etag files after gravity run by @yubiuser in #6353 - add logrotate to DEB and RPM dependencies by @darkexplosiveqwx in #6524 - Improve gravity error message including curl exit code and errormsg by @rdwebdesign in #6605 ## Security advisories - GHSA-6w8x-p785-6pm4 …

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

10

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.