CVE-2026-50130

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 87% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this weekElevated
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
13.2%
KEV
Not listed

Published

July 14, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 14, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, github_commit.
github_release Patch Available

v6.4.3

Patch available: pi-hole/pi-hole v6.4.3

https://github.com/pi-hole/pi-hole/releases/tag/v6.4.3
github_commit Patch Available

commit 18002bf7c6bf (pi-hole/pi-hole)

Patch available: pi-hole/pi-hole v6.4.3 (contains commit 18002bf7c6bf)

https://github.com/pi-hole/pi-hole/commit/18002bf7c6bf382fe5861d01321f427019e1be89
github Patch Available🟡 PoC Available

Local privilege escalation from `pihole` user to root via `/etc/pihole/logrotate` · Advisory · pi-hole/pi-hole · GitHub

https://github.com/pi-hole/pi-hole/security/advisories/GHSA-h8w9-qx2v-wrww

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 21:07 UTCEG score recompute
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 09:35 UTCEG score recompute
  5. 2026-07-14 22:01 UTCEG score recompute
  6. 2026-07-14 22:00 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-50130?
CVE-2026-50130 is a high vulnerability published on July 14, 2026. 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…
When was CVE-2026-50130 disclosed?
CVE-2026-50130 was first published in the National Vulnerability Database on July 14, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-50130 actively exploited?
CVE-2026-50130 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-50130?
CVE-2026-50130 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-50130?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-50130, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-50130

Explore →

Is Your Infrastructure Affected by CVE-2026-50130?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs