External risk intelligence

Pi-hole FTL Unauthenticated WebUI and API Flooding Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.2)

CVE-2025-62165

Pi-hole is designed as a network-level advertisement blocker typically deployed within a private home or small office network for local DNS resolution. While the WebUI and API are network-accessible, they are intended for internal management and administration, making exposure to the public internet uncommon and contrary to standard deployment practices.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Pi-hole FTL, the core engine of the Pi-hole ad blocker, could allow unauthenticated users to overload the system through repeated requests to its web interface. This could degrade the performance of the WebUI and potentially impact the broader system's DNS service and storage capacity due to excessive logging. The issue is present in versions 6.0 through 6.7.

  • Unauthenticated requests can disrupt the ad blocker's web interface.
  • Leadership should remember this impacts a core network service.
  • Confirm relevance and exposure of this ad blocking technology.

Attack Path

How an attacker could exploit the issue

An attacker can target Pi-hole's core engine by sending numerous requests to the WebUI login page and API with invalid paths. This can overwhelm the system's processing and authentication, leading to a sluggish or unresponsive interface, and potentially impacting DNS services. Additionally, certain requests can rapidly expand log files, exhausting storage.

  • No authentication required to initiate attack.
  • Flooding with invalid requests triggers the vulnerability.
  • System slowdown, service interruption, and storage exhaustion.

Live Threat

Current exploitation, exposure, and threat context

Unauthenticated clients could overwhelm the Pi-hole WebUI and API with repeated requests to invalid paths. This may cause the WebUI to become unresponsive and impact the DNS service. Log entries generated by these requests could also exhaust storage on constrained devices.

  • WebUI and API availability.
  • Repeated invalid path requests.
  • Service disruption and storage exhaustion.

Operational Fix

Recommended remediation, mitigation, and detection steps

The Pi-hole FTL engine, used for ad and tracker blocking, is affected by a vulnerability that allows unauthenticated clients to overwhelm its WebUI and API. This can lead to significant CPU consumption and log file expansion, potentially impacting system responsiveness and storage. Identifying all instances of the affected Pi-hole versions, confirming their network exposure and criticality, and then engaging the responsible team for remediation is the crucial first step.

  • Own the issue by device or service owner.
  • Verify network exposure and impact.
  • Plan remediation with vendor coordination.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Pi-hole FTL?

Pi-hole FTL is the specialized backend engine that powers Pi-hole, a popular network-wide tool designed to block advertisements and trackers. It functions as a lightweight DNS server that processes queries, manages blocklists, and provides data for the web-based administrative dashboard. Users typically deploy it on low-power hardware, such as single-board computers, to manage DNS resolution and filter traffic across their entire local network.

What does CVE-2025-62165 mean for my system?

This vulnerability, classified as CWE-770 (Allocation of Resources Without Limits), allows unauthenticated users to overwhelm Pi-hole FTL by flooding the WebUI or API with invalid requests. Because the software does not limit the rate of these connections, the system must process excessive authentication attempts, which can cause high CPU usage. This can make the dashboard unresponsive and, in some cases, hinder the core DNS service that your network relies on.

How do these invalid requests trigger the system issues?

An attacker triggers this by sending a high volume of requests to invalid paths in the WebUI or API. This forces the system to consume CPU cycles for authentication logic. Furthermore, for certain invalid paths, the system generates a log entry for every request. If an attacker repeatedly targets these specific paths, the rapid accumulation of log data can exhaust available disk space, which is especially problematic for systems using constrained storage like SD cards.

Do I need to worry if my Pi-hole is not on the internet?

According to Halo Surface Signal, this vulnerability is considered unlikely to be exploited if your device is used as intended. Pi-hole is typically deployed within a private home or small office network for local management. Because the WebUI and API are designed for internal administration, they are usually not exposed to the public internet. If your instance is strictly internal, the risk is lower compared to instances directly reachable from outside your network.

When should I update my Pi-hole software?

You should update to version 6.7 or newer as soon as possible. Because this issue can impact both system performance and long-term storage health, confirming your current version is the first practical step. If you are running any version between 6.0 and 6.6, you are affected. Updating ensures that the necessary request-rate limiting is in place, protecting your device from being overwhelmed by unauthenticated traffic.

References