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

Pi-hole v6.4.1

UPDATE_WITH_CARE

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

Published: 2026-04-03T16:54:32Z · GitHub release

Summary of changes

## What's Changed - Remove additional ':' from debug log system time output by @yubiuser in #6551 - Remove readonly from piholeNetworkFlush.sh to avoid error message by @rdwebdesign in #6554 - Add antigravity index by @DL6ER in #6573 - Fix return status capture of FTL check_download exists by @yubiuser in #6572 - Remove misleading TODO comment for SetWebPassword by @10adnan75 in #6531 ## Security Advisories - GHSA-c935-8g63-qp74 – Local Privilege Escalation reported by @smittix ## New Contributors - @10adnan75 made their first contribution in #6531 - @Copilot made their first contribution in #6580 Full Changelog: v6.4...v6.4.1

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

6

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.