{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50130 exists.","fix":"No fix has been published for CVE-2026-50130 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-50130 is a high-severity vulnerability in pi-hole, published on 14 Jul 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-50130 and fix it if it is affected.\n\nWhat it is: CVE-2026-50130 is a high-severity vulnerability in pi-hole, published on 14 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-50130 exists.\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-50130/ (Markdown: https://insights.sbomify.com/CVE-2026-50130/index.md)","id":"CVE-2026-50130","markdown":"https://insights.sbomify.com/CVE-2026-50130/index.md","name":"CVE-2026-50130","record":{"aliases":["GHSA-h8w9-qx2v-wrww"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Pi-hole DNS sinkhole","requires_auth":"low_privilege","summary":"An attacker with pihole user access can escalate to root by replacing the logrotate configuration file, which is then executed with root privileges.","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":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-282","name":"Improper Ownership Management"}],"description":"Pi-hole is a DNS sinkhole that protects devices from unwanted content without installing any client-side software. From 6.0 to 6.4.2, a user with code execution as the unprivileged pihole user can escalate to root by replacing /etc/pihole/logrotate. The replacement is laundered to root:root ownership by pihole-FTL-prestart.sh and then parsed as root by the daily pihole flush cron, executing firstaction shell as uid 0. This issue is fixed in version 6.4.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Pi-hole: Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate`","id":"CVE-2026-50130","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Fedify has an incomplete SSRF mitigation after GHSA-p9cg-vqcc-grcx: validatePublicUrl allows special-use IPv4 ranges","id":"CVE-2026-50131"},"packages":[],"prev":{"headline":"Mastodon: Persistent anonymous DoS via unhandled NoMethodError in MATH_TRANSFORMER","id":"CVE-2026-50129"},"products":["pi-hole"],"published":"2026-07-14","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":"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-16","vendors":["pi-hole"]},"summary":"An attacker with pihole user access can escalate to root by replacing the logrotate configuration file, which is then executed with root privileges.","url":"https://insights.sbomify.com/CVE-2026-50130/"}