ETK-2026-4228Zero's internal tracking ID, independent of the CVE number.

validatingZero is analyzing and reversing it now.

GHSA-pj9m-9623-2g75 ↗

no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
other:pi-hole/FTL = 6.8; <= 6.5
fixed in 6.9, 6.6
CWE-78 Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
ETK-2026-4228Zero's internal tracking ID, independent of the CVE number., no cve assigned
–running
startingcurrent stage
timeline
0 = trigger signal
trigger signal +0h
0
+1h
+2h
+3h
+4h

description

Pi-hole FTL and Pi-hole Core are affected by unsafe handling of the configured gravity database path. An authenticated administrator able to change configuration and trigger a gravity update can execute operating-system commands as the pihole user.

Still under analysis: more detail becomes available as the pipeline runs.

mitigation

Update Pi-hole FTL to 6.9 and Pi-hole Core to 6.6 together. Until updates are installed, restrict administrative API access and limit who can modify the gravity-path configuration.

fixed in 6.9, 6.6

check
building now
exploit
not yet
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, high privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Run in progress: no artifact yet.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-11 19:21Z

this entry in the feed

GET /api/v1/feed/ETK-2026-4228

{
  "etk_id": "ETK-2026-4228",
  "cve_id": null,
  "display_id": "ETK-2026-4228",
  "ghsa_id": "GHSA-pj9m-9623-2g75",
  "euvd_id": null,
  "status": "in_pipeline",
  "anchor_state": "awaiting_cve",
  "title": "Authenticated SQL injection in Pi-hole FTL gravity handling",
  "summary": "Pi-hole FTL and Pi-hole Core are affected by unsafe handling of the configured gravity database path. An authenticated administrator able to change configuration and trigger a gravity update can execute operating-system commands as the pihole user.",
  "mitigation": "Update Pi-hole FTL to 6.9 and Pi-hole Core to 6.6 together. Until updates are installed, restrict administrative API access and limit who can modify the gravity-path configuration.",
  "vendor": null,
  "product": "other:pi-hole/FTL",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "= 6.8"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "6.9"
      ],
      "package_name": "pi-hole/FTL",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 6.5"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "6.6"
      ],
      "package_name": "pi-hole",
      "purl": null
    }
  ],
  "cwes": [
    78
  ],
  "cvss_score": 7.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": null,
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T19:21:46+00:00",
      "days": -0.1738049409375,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T23:32:02.788295+00:00",
      "url": "https://github.com/pi-hole/FTL/security/advisories/GHSA-pj9m-9623-2g75"
    }
  }
}

published 2026-11-11 23:21Z
last change 2026-11-11 23:30Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.