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

waiting for further signalsZero needs more public information before it can validate it.

GHSA-cq9w-mv93-mxh7 ↗

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 <= 6.5
fixed in 6.6
CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
ETK-2026-4210Zero's internal tracking ID, independent of the CVE number., no cve assigned
1h 20msince last run
12mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal +0hwaiting for further signals+0h40m
0
+1h
+2h

description

Pi-hole Core versions before 6.6 can incorporate an unescaped gravity database path into an SQL operation. An attacker able to set that path through the API could cause SQL statements, and potentially commands, to run as the pihole user.

mitigation

Upgrade Pi-hole Core to version 6.6 or later. Until upgraded, restrict access to the API and prevent untrusted users from changing gravity database path settings.

fixed in 6.6

check
no
exploit
no
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.
contextual
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
12m
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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-11 19:22Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-4210",
  "cve_id": null,
  "display_id": "ETK-2026-4210",
  "ghsa_id": "GHSA-cq9w-mv93-mxh7",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "SQL injection in Pi-hole Core gravity database handling",
  "summary": "Pi-hole Core versions before 6.6 can incorporate an unescaped gravity database path into an SQL operation. An attacker able to set that path through the API could cause SQL statements, and potentially commands, to run as the pihole user.",
  "mitigation": "Upgrade Pi-hole Core to version 6.6 or later. Until upgraded, restrict access to the API and prevent untrusted users from changing gravity database path settings.",
  "vendor": "other",
  "product": "other:pi-hole",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 6.5"
      ],
      "ecosystem": "other",
      "fixed_versions": [
        "6.6"
      ],
      "package_name": "pi-hole",
      "purl": null
    }
  ],
  "cwes": [
    89
  ],
  "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": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 11.538907233333333,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-11-11T19:22:05+00:00",
      "days": -0.08389491387731482,
      "is_lower_bound": true,
      "measured_at": "2026-11-11T21:22:53.648167+00:00",
      "url": "https://github.com/pi-hole/pi-hole/security/advisories/GHSA-cq9w-mv93-mxh7"
    }
  }
}

published 2026-11-11 20:12Z
last change 2026-11-11 21:19Z

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.