# CVE-2026-33727: Pi-hole has a Local Privilege Escalation (post-compromise, pihole -> root).

> A local privilege escalation allows attackers with pihole account access to execute code as root via compromised version files.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-c935-8g63-qp74

## What is CVE-2026-33727?

CVE-2026-33727 is a medium-severity vulnerability in pi-hole, published on 6 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pi-hole is a Linux network-level advertisement and Internet tracker blocking application. Version 6.4 has a local privilege-escalation vulnerability allows code execution as root from the low-privilege pihole account. Important context: the pihole account uses nologin, so this is not a direct interactive-login issue. However, nologin does not prevent code from running as UID pihole if a Pi-hole component is compromised. In that realistic post-compromise scenario, attacker-controlled content in /etc/pihole/versions is sourced by root-run Pi-hole scripts, leading to root code execution. This vulnerability is fixed in 6.4.1.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2026-33727?

It affects 1 product.


Products: Pi-Hole Pi-Hole.

## How do I fix CVE-2026-33727?

No fix has been published for CVE-2026-33727 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33727 being exploited?

There is no known exploitation of CVE-2026-33727 in the wild and no public exploit code.

## Other vulnerabilities in pi-hole

- [CVE-2020-8816](https://insights.sbomify.com/CVE-2020-8816/): Pi-Hole AdminLTE Remote Code Execution (critical 9.1, exploited in the wild)
- [CVE-2025-34087](https://insights.sbomify.com/CVE-2025-34087/): Pi-Hole AdminLTE Whitelist (now 'Web Allowlist') Remote Command Execution (critical 9.0)
- [CVE-2026-50130](https://insights.sbomify.com/CVE-2026-50130/): Pi-hole: Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate` (high 8.8)
- [CVE-2020-11108](https://insights.sbomify.com/CVE-2020-11108/): File upload in n/a (high 8.8)
- [CVE-2019-13051](https://insights.sbomify.com/CVE-2019-13051/): Pi-Hole 4.3 allows Command Injection. (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33727 and fix it if it is affected.

What it is: CVE-2026-33727 is a medium-severity vulnerability in pi-hole, published on 6 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33727 in the wild and no public exploit code.

Affected product: pi-hole. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33727/ (Markdown: https://insights.sbomify.com/CVE-2026-33727/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33727
- OSV: https://osv.dev/vulnerability/CVE-2026-33727

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33727/
Summaries are generated and may contain mistakes; the official description above is the record.