Pi-hole FTL is the core engine of the Pi-hole network-level advertisement and tracker blocker. Prior to 6.7, log_http_access in src/webserver/webserver.c writes attacker-controlled User-Agent content to the access log without output neutralization when debug.api is enabled. If an administrator configures files.log.webserver inside webserver.paths.webroot with a filename matching lua_server_page_pattern, an unauthenticated request can plant Lua markup in that log and a later request can cause CivetWeb to evaluate the log as a Lua server page. The resulting commands run as the pihole operating-system user and can access or modify pihole-owned configuration, credentials, databases, logs, and rendered interface content. When the log is not served through the Lua handler, the same unneutralized writer still permits log forgery and downstream log-parser injection. This issue is fixed in version 6.7.
CVE-2026-65964
This medium-severity CVE scores 6.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-127552 (ENISA EUVD)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 6.6
- EG Score
- 6.6MEDIUMlow confidence
- EG Risk
- 30EG Risk 30/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity66% × 45%Impact severity (EG Severity): CVSS 6.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0% × 40%No KEV listing, EG-KEV tier or EPSS when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.4%
- EPSS %ILE
- 38th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.6): severity, escalated by confirmed exploitation. This CVE's 6.6 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.6 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 17, 2026
Last Modified
November 17, 2026
Advisory Details (5)
Auto-updated Nov 17, 2026Log injection in webserver access-log writer chains to remote code execution via Lua-server-page evaluation · Advisory · pi-hole/FTL · GitHub
https://github.com/pi-hole/FTL/security/advisories/GHSA-g7v8-8q8f-hprpv6.7
Patch available: pi-hole/FTL v6.7
https://github.com/pi-hole/FTL/releases/tag/v6.7Pi-hole FTL v6.7
Fix merged in pi-hole/FTL PR #2936 on 2026-07-06 — awaiting tagged release
https://github.com/pi-hole/FTL/pull/2936Code review July 2026
Fix merged in pi-hole/FTL PR #2935 on 2026-07-05 — awaiting tagged release
https://github.com/pi-hole/FTL/pull/2935commit 07fe23439b64 (pi-hole/FTL)
Fix landed in pi-hole/FTL commit 07fe23439b64 — awaiting tagged release
https://github.com/pi-hole/FTL/commit/07fe23439b644fe47649690595fb647b0e76e367Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 6× in last 7d / 6× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
- 2026-11-17 23:29 UTCEchelonGraph re-scored
- 2026-11-17 22:32 UTCEchelonGraph re-scored
- 2026-11-17 22:03 UTCENISA EUVD ID recordedEUVD-2026-127552 · Source: ENISA EUVD
- 2026-11-17 21:31 UTCEchelonGraph re-scored
- 2026-11-17 21:08 UTCEchelonGraph re-scoredFirst assessed: 6.6 MEDIUM
- 2026-11-17 21:07 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-117 · CWE-94
Frequently asked(5)
What is CVE-2026-65964?
When was the CVE record for CVE-2026-65964 published?
Is CVE-2026-65964 actively exploited?
What is the CVSS score of CVE-2026-65964?
How do I remediate CVE-2026-65964?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65964
Is Your Infrastructure Affected by CVE-2026-65964?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.