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

Pi-hole v6.4.3

UPDATE_WITH_CARE

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

Published: 2026-07-07T09:18:08Z · GitHub release

Summary of changes

## Security Fixes - pi-hole/pi-hole/security/advisories/GHSA-h8w9-qx2v-wrww — Local privilege escalation from pihole user to root via /etc/pihole/logrotate (High) reported by supperhellokitty20 ## What's Changed - Also hardcode the PID file location in utils.sh to prevent readonly variable warning by @PromoFaux in #6613 - Use awk to compare curl versions by @rdwebdesign in #6621 - Explicitly add gawk to APK dependencies by @yubiuser in #6622 - Prevent double error message output in gravity run with invalid file by @PromoFaux in #6607 - Replace pytest/tox with direct in-container BATS by @PromoFaux in #6598 - Add Fedora 44 and Ubuntu 26.04 LTS to tests by @darkexplosiveqwx in #6623 - Add gravity tests by @yubiuser in #6639 - Set BATS pretty output flag depending on the terminal and improve failure output by @yubiuser in #6644 …

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

14

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.