# CVE-2026-44693: Pi-hole FTL: Unauthenticated Session Hijacking via Race Condition on Global Session Buffer

> An attacker can hijack user sessions in Pi-hole FTL via a race condition in the web server, leading to unauthorized access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-9ff5-f3v5-2xc7

## What is CVE-2026-44693?

CVE-2026-44693 is a high-severity vulnerability in pi-hole FTL, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

## Which versions are affected by CVE-2026-44693?


## How do I fix CVE-2026-44693?

No fix has been published for CVE-2026-44693 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44693 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44693 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44693 and fix it if it is affected.

What it is: CVE-2026-44693 is a high-severity vulnerability in pi-hole FTL, published on 10 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44693 exists.

Affected product: pi-hole FTL. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44693/ (Markdown: https://insights.sbomify.com/CVE-2026-44693/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44693
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44693
- OSV: https://osv.dev/vulnerability/CVE-2026-44693

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44693/
Summaries are generated and may contain mistakes; the official description above is the record.