{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33727 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-33727 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-33727 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2026-33727 in the wild and no public exploit code.\n\nAffected product: pi-hole. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33727/ (Markdown: https://insights.sbomify.com/CVE-2026-33727/index.md)","id":"CVE-2026-33727","markdown":"https://insights.sbomify.com/CVE-2026-33727/index.md","name":"CVE-2026-33727","record":{"aliases":["GHSA-c935-8g63-qp74"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Pi-hole ad blocker","requires_auth":"high_privilege","summary":"A local privilege escalation allows attackers with pihole account access to execute code as root via compromised version files.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pi-hole","vendor":"pi-hole"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-269","name":"Improper Privilege Management"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Pi-hole has a Local Privilege Escalation (post-compromise, pihole -\u003e root).","id":"CVE-2026-33727","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"dd-trace-java: Unsafe deserialization in RMI instrumentation may lead to remote code execution","id":"CVE-2026-33728"},"packages":[],"prev":{"headline":"Cilium L7 proxy may bypass Kubernetes NetworkPolicy for same-node traffic","id":"CVE-2026-33726"},"products":["pi-hole"],"published":"2026-04-06","related":[{"cvss_score":9.1,"headline":"Pi-Hole AdminLTE Remote Code Execution","id":"CVE-2020-8816","kev_date_added":"2021-12-10","published":"2020-05-29"},{"cvss_score":9,"headline":"Pi-Hole AdminLTE Whitelist (now 'Web Allowlist') Remote Command Execution","id":"CVE-2025-34087","kev_date_added":null,"published":"2025-07-03"},{"cvss_score":8.8,"headline":"Pi-hole: Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate`","id":"CVE-2026-50130","kev_date_added":null,"published":"2026-07-14"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-11108","kev_date_added":null,"published":"2020-05-11"},{"cvss_score":8.8,"headline":"Pi-Hole 4.3 allows Command Injection.","id":"CVE-2019-13051","kev_date_added":null,"published":"2019-10-09"},{"cvss_score":8.6,"headline":"Pi-hole Blind Server-Side Request Forgery (SSRF) vulnerability can lead to Remote Code Execution (RCE)","id":"CVE-2024-34361","kev_date_added":null,"published":"2024-07-05"},{"cvss_score":7.8,"headline":"Command injection in n/a","id":"CVE-2020-12620","kev_date_added":null,"published":"2020-07-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["pi-hole"]},"summary":"A local privilege escalation allows attackers with pihole account access to execute code as root via compromised version files.","url":"https://insights.sbomify.com/CVE-2026-33727/"}