Quick answers
- Is CVE-2026-119335 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119335 being exploited in the wild.
- How severe is CVE-2026-119335?
- High severity, with a CVSS score of 7.8, published 30 October 2026.
- Which products and versions are affected?
- Pi-hole prior to 6.5.
- Is there a fix for CVE-2026-119335?
- Yes: fixed in 6.5. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119335 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-119335?
- Check whether you run Pi-hole at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 6.5
Technical details
The getFTLPID() function in advanced/Scripts/utils.sh insufficiently validates the /run/pihole-FTL.pid file, checking only that the first character is numeric rather than validating the entire contents. An attacker with code execution as the unprivileged pihole user can write a crafted arithmetic expression (e.g., "1+a[$(cmd)]") to this file, which is then evaluated as root when pihole subcommands execute arithmetic comparisons like [[ "$pid" -eq "-1" ]], allowing recursive Bash evaluation and command substitution with root privileges.
Affected products
- Pi-hole Pi-hole prior to 6.5
Timeline
- 2026-10-30: disclosed
- 2026-10-17: patched: Fixed in version 6.5, merged prior to disclosure