CVE
FTL denial of service in WebUI login and API paths
Affects Pi-hole FTL version 6 (from 6.0) with the embedded CivetWeb web server, before 6.7. No vendor rating is given, and the fix is 6.7.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H
- Exploited
- No known exploitation
- Fix
- Fixed in 6.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 6.7.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Pi-hole FTL, the core engine of the Pi-hole network ad and tracker blocker, is vulnerable from 6.0 through 6.7 to denial of service. An attacker can remotely, without logging in, flood the WebUI login page and invalid API paths to consume CPU, making the WebUI slow or unresponsive and possibly affecting DNS service, or fill storage such as an SD card with log entries.
Original description
Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, CivetWeb permits unauthenticated clients to flood the WebUI login page and API invalid paths without connection or request-rate limits. Repeated requests can consume substantial CPU in request processing and session authentication, making the WebUI sluggish or unresponsive and potentially affecting the wider system and DNS service. Requests to selected invalid or redirecting paths also generate a log entry for each request, allowing network traffic to expand logs and exhaust constrained storage such as an SD card, while other request forms consume CPU without producing a corresponding request log. This vulnerability is fixed in 6.7.
Who should check
Teams running Pi-hole FTL v6.0 through 6.6 with the embedded CivetWeb web server, especially Raspberry Pi installs with the web UI or API reachable on the network.
“Appears to be a problem on v6 (with the civetweb server incorporated)”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.2/10CVSS 9.2
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 6.7.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2025-62165 (Pi-hole FTL: WebUI (& API) DoS mechanism - Lack of rate limiting : Silent CPU consumption and/or Log file expansion), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2025-62165 (entry last updated 2026-11-17):
Affected:
- pi-hole FTL: from 6.0, fixed in 6.7
Fixed versions: 6.7.
Conditions (all must be true for the bug to be hit):
- Pi-hole FTL version 6 with the embedded CivetWeb web server (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-q6fm-xwxf-37r5)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2025-62165 is not listed as of cve.now's last read.
This KEV status is for CVE-2025-62165 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/pi-hole/FTL/security/advisories/GHSA-q6fm-xwxf-37r5
- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/c358cac3e6c55ce7e41dc00252c318e5a6eca0ef
- https://github.com/pi-hole/FTL/releases/tag/v6.7
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2025-62165
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2025-62165"}.Timeline
- CVE published
- Record last updated
- First seen by cve.now
Affected versions
- pi-hole FTL
From 6.0 · fixed in 6.7
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2025-62165
Is CVE-2025-62165 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The web UI and API lack rate limiting, so repeated requests can drive up CPU use silently, making the web UI unresponsive. Log files can also grow enough to exhaust storage such as an SD card.Source: github.com
Which versions are affected by CVE-2025-62165?
FTL: from 6.0 before 6.7.Source: cve.now feed data
Am I affected, and how do I check?
Pi-hole FTL versions from 6.0 up to but not including 6.7, when running the embedded CivetWeb web server. The installed version can be checked with the pihole -v command.Source: github.com
How do I fix CVE-2025-62165?
Upgrade Pi-hole FTL to version 6.7 or later, which is the fixed version listed for this vulnerability.Source: github.com