dbcve.org
Race ConditionWeakness · CWE-362

CVE-2026-44693

HIGH · 8.8 CVSS v3.1 Published 2026-06-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to version 6.6.1, Pi-hole FTL contains a race condition vulnerability in the HTTP session management subsystem, introduced with the v6.0 rewrite of the embedded CivetWeb-based web server. This issue has been patched in version 6.6.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Pi-hole FTL prior to version 6.6.1 contains a race condition vulnerability in the HTTP session management subsystem, stemming from the v6.0 rewrite of the embedded CivetWeb web server. This race condition in session handling could allow an attacker to potentially manipulate or hijack HTTP sessions due to improper synchronization in concurrent session operations.

MitigationUpgrade Pi-hole FTL to version 6.6.1 or later to patch the race condition vulnerability in the HTTP session management subsystem.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Pi-hole FTL is installed
    Run command: which pihole-FTL or systemctl status pihole-FTL
    Affected if Pi-hole FTL is not installed on the system
  2. Identify installed Pi-hole FTL version
    Run command: pihole -v or pihole-FTL version
    Affected if Version displayed is below 6.6.1
  3. Verify web interface is enabled
    Check /etc/pihole/setupVars.conf for WEB_PASSWORD or WEBINTERFACE=true, or check if lighttpd/civetweb service is running
    Affected if Web interface is enabled and version is below 6.6.1
  4. Check if HTTP sessions are in use
    Inspect active network connections on ports 80/443 or check if the admin interface is accessible
    Affected if Web interface is accessible and version is below 6.6.1

The environment is affected if Pi-hole FTL version is below 6.6.1 and the web interface is enabled/accessible, as the race condition exists in the HTTP session management of the embedded CivetWeb server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Pi-hole FTL to version 6.6.1 or later to patch the race condition vulnerability in the HTTP session management subsystem.

Recommended fix Moderate confidence

Pi-hole FTL version 6.6.1

  1. 1. Backup your current Pi-hole configuration and data
  2. 2. Update the Pi-hole repository: `pihole -up` or `sudo pihole -up`
  3. 3. Alternatively, manually update Pi-hole FTL by downloading version 6.6.1 from the official Pi-hole GitHub repository
  4. 4. Verify the installation completed successfully by checking the version: `pihole -v`
  5. 5. Ensure Pi-hole FTL is running: `sudo systemctl status pihole-FTL`
  6. 6. Test that the web interface and DNS resolution are functioning correctly
Caveat Review Pi-hole v6.6.1 release notes for any configuration changes or migration requirements from prior versions

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44693 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44693 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data