Technical impact
The vulnerability stems from an improperly configured root‑run cron job that truncates and sets permissions on /etc/pihole/versions. When the cron script follows a symbolic link, an attacker who can write in the Pi‑hole directory can replace the target with a link to any file, causing an arbitrary file to be truncated or overwritten as root or making a sensitive file world‑readable. This allows a local attacker to create or corrupt root‑owned files and potentially expose confidential data.
Affected Systems
Pi‑Hole software versions from 6.4.2 up to 6.5, running on Linux systems where the updatecheck.sh cron job executes as root but operates on files owned by the pihole user. The vulnerability was addressed in the 6.5 release.
Risk and Exploitability
The CVSS score of 7.8 indicates a high severity vulnerability. The EPSS score is not available, so the likelihood of exploitation in the wild is uncertain, and the vulnerability is not listed in the CISA KEV catalog. The attack requires local write access to the /etc/pihole/ directory, making it a local privilege problem, but because the cron job runs as root it can elevate the damage once the symlink is in place.