Root escalation via logrotate ownership laundering
Published Jul 14, 2026 · Updated Jul 14, 2026
Improper ownership management in Pi-hole 6.0 through 6.4.2 allows local users running as pihole to execute shell commands as root. The root-context pihole-FTL-prestart.sh hook changes a replacement /etc/pihole/logrotate file to root ownership without validating its contents. Code execution as the pihole user permits replacement and a service restart; the daily root cron then parses firstaction as uid 0.
Summary
What happened
Improper ownership management in Pi-hole 6.0 through 6.4.2 allows local users running as pihole to execute shell commands as root. The root-context pihole-FTL-prestart.sh hook changes a replacement /etc/pihole/logrotate file to root ownership without validating its contents. Code execution as the pihole user permits replacement and a service restart; the daily root cron then parses firstaction as uid 0.
The record
- CVE
- CVE-2026-50130
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Pi-hole
- Product
- Pi-hole
- Classifications
- CWE-282, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 6.0.0, < 6.4.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-h8w9-qx2v-wrww end-to-end proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo