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

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

GHSA-w8jc-g24h-crhw ↗

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.
pip GitPython <= 3.1.62
fixed in >= 3.2.0
CWE-1287 Improper Validation of Specified Type of Input
ETK-2026-286, no cve assigned
pkg:pypi/GitPython
19d 06h 57msince last run
7mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
trigger signal −21dwaiting for further signals−19d
−15d
−10d
−5d
0

description

GitPython before 3.2.0 does not consistently validate URLs and options passed to the ls_remote, merge_base, and IndexFile.move wrappers. An attacker who can control inputs to these APIs may cause unsafe Git transport handling, including command execution through ls_remote when the local Git configuration permits the transport, or pass unvalidated arguments to other Git commands.

mitigation

Upgrade GitPython to >= 3.2.0 or later.

fixed in >= 3.2.0

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
7m
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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-09-30 09:11Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-286",
  "cve_id": null,
  "display_id": "ETK-2026-286",
  "ghsa_id": "GHSA-w8jc-g24h-crhw",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "awaiting_cve",
  "title": "Unsafe Git argument handling in GitPython wrappers",
  "summary": "GitPython before 3.2.0 does not consistently validate URLs and options passed to the ls_remote, merge_base, and IndexFile.move wrappers. An attacker who can control inputs to these APIs may cause unsafe Git transport handling, including command execution through ls_remote when the local Git configuration permits the transport, or pass unvalidated arguments to other Git commands.",
  "mitigation": "Upgrade GitPython to >= 3.2.0 or later.",
  "vendor": "pip",
  "product": "GitPython",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.1.62"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        ">= 3.2.0"
      ],
      "package_name": "GitPython",
      "purl": "pkg:pypi/GitPython"
    }
  ],
  "cwes": [
    1287
  ],
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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": 7.060216716666667,
  "t0_at": null,
  "signals": {
    "trigger_signal": {
      "at": "2026-09-30T09:11:28+00:00",
      "days": -20.85814950769676,
      "is_lower_bound": true,
      "measured_at": "2026-10-21T05:47:12.138837+00:00",
      "url": "https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-w8jc-g24h-crhw"
    }
  }
}

published 2026-10-01 22:42Z
last change 2026-10-21 05:31Z

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.