<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: pi-hole</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/pi-hole.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-119335: Pi-hole: Local privilege escalation from `pihole` user to root via CVE-2026-41489 fix bypass</title><link>https://vulnfeed.org/cve/CVE-2026-119335/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-119335/</guid><pubDate>Fri, 30 Oct 2026 20:17:08 +0000</pubDate><description>Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. Prior to 6.5, advanced/Scripts/utils.sh getFTLPID() attempts to validate the pihole-owned /run/pihole-FTL.pid file with expr &quot;${FTL_PID}&quot; : &quot;[^[:digit:]]&quot;, but this rejects only values whose first character is not a digit. An attacker with code execution as the pihole user can write a digit-prefixed arithmetic expression to the pihole-owned PID file. Root-run pihole subcommands then evaluate [[ &quot;$pid&quot; -eq &quot;-1&quot; ]], causing Bash to recursively evaluate array subscripts and execute command substitution as root. This bypasses the content-validation portion of the CVE-2026-41489 remediation while leaving its hardcoded PID-file path protection intact. This issue is fixed in version 6.5.</description></item><item><title>CVE-2026-119336: Pi-hole: arbitrary root file clobber / chmod / disclosure via updatecheck.sh cron following /etc/pihole/versions symlink</title><link>https://vulnfeed.org/cve/CVE-2026-119336/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-119336/</guid><pubDate>Fri, 30 Oct 2026 20:17:08 +0000</pubDate><description>Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. From 6.4.2 until 6.5, the root-run advanced/Scripts/updatecheck.sh cron job applies truncate -s 0 and chmod 644 to /etc/pihole/versions while following symbolic links in a directory owned by the pihole user. An attacker executing as pihole can replace that path with a symlink so the scheduled root operations truncate or create an arbitrary root-owned file, or race the operations so chmod makes a sensitive target world-readable without truncating it. This issue is fixed in version 6.5.</description></item></channel></rss>
