Skip to main content
VulnerabilityPublished Updated

CVE-2026-44693: pi-hole FTL · Race Condition

Affects pi-hole FTLSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High : upgrade to 6.6.1 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 6.6.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade FTL and pi-hole/FTL to 6.6.1.

Affected software

ProductAffectedFixed in
pi-holeFTLAffected
  • <6.6.1
Fixed in
  • 6.6.1
GitHubpi-hole/FTLpkg:github/pi-hole/FTLOther threatsAffected
  • <6.6.1
Fixed in
  • 6.6.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Pi-hole FTL to version 6.6.1 or later, where this race condition vulnerability has been patched. No other mitigation guidance is provided or necessary as the issue is fixed in this official release.

Description

Pi-hole FTL versions prior to 6.6.1 contain a race condition vulnerability in the HTTP session management subsystem. This flaw was introduced with the version 6.0 rewrite of the embedded CivetWeb-based web server. The vulnerability allows concurrent execution using a shared resource with improper synchronization, potentially leading to high impact on confidentiality, integrity, and availability. The issue has been patched in version 6.6.1.

References

Community reviews

Loading reviews…