CVE-2026-71304
8.8HighPublished 17 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-613
What an attacker gets
Authenticated attackers can maintain administrative access indefinitely by reusing expired session identifiers. This bypasses session timeout policies and prevents session invalidation.
Root cause
The check_client_auth function assigns a user_id to expired sessions before validating the expiration timestamp, allowing the session to be renewed.
Affected versions
Pi-hole FTL versions 6.0 through 6.6.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Fix & remediation
Upgrade to Pi-hole FTL version 6.7 or later. As an interim mitigation, manually revoke active sessions via the administrative interface or restart the FTL service to clear current sessions.
$ pihole checkout ftl v6.7AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.