CVE-2026-114145

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

GHSA-83vg-56qc-22m7 ↗EUVD-2026-107557 ↗

no check availablenot proven exploitable
cve.orgpublic 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.2.0
fixed in >= 3.2.1
CWE-696 Incorrect Behavior Order
ETK-2026-1574Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:pypi/Gitpython
2h 38msince last run
11mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal −7.3dcve.org publicationwaiting for further signals+0.0d
−6d
−4d
−2d

description

GitPython before 3.2.1 can process a malicious submodule path before fully validating that it does not target repository metadata. An attacker may cause a Git hook to be written and later executed when an application passes attacker-controlled paths to create_submodule() and the destination can accept the write.

mitigation

Upgrade Gitpython to >= 3.2.1 or later.

fixed in >= 3.2.1

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
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-21 20:35Z
Δ 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-10-14 12:22Z
  2. 2026-10-21 20:35Z

this entry in the feed

GET /api/v1/feed/CVE-2026-114145

{
  "etk_id": "ETK-2026-1574",
  "cve_id": "CVE-2026-114145",
  "display_id": "CVE-2026-114145",
  "ghsa_id": "GHSA-83vg-56qc-22m7",
  "euvd_id": "EUVD-2026-107557",
  "status": "published",
  "anchor_state": "anchored",
  "title": "GitPython submodule path validation enables hook injection",
  "summary": "GitPython before 3.2.1 can process a malicious submodule path before fully validating that it does not target repository metadata. An attacker may cause a Git hook to be written and later executed when an application passes attacker-controlled paths to `create_submodule()` and the destination can accept the write.",
  "mitigation": "Upgrade Gitpython to >= 3.2.1 or later.",
  "vendor": "pip",
  "product": "GitPython",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 3.2.0"
      ],
      "ecosystem": "pip",
      "fixed_versions": [
        ">= 3.2.1"
      ],
      "package_name": "Gitpython",
      "purl": "pkg:pypi/Gitpython"
    }
  ],
  "cwes": [
    696
  ],
  "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": 10.622363366666667,
  "t0_at": "2026-10-21T20:35:06.548000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T12:22:57+00:00",
      "days": -7.341777175925926,
      "is_lower_bound": false,
      "measured_at": "2026-10-21T20:35:06.548000+00:00",
      "url": "https://github.com/gitpython-developers/GitPython/security/advisories/GHSA-83vg-56qc-22m7"
    }
  }
}

Anchor corroborated by the cve.org commit 7ad92194ca63.

published 2026-10-14 13:34Z
last change 2026-10-21 23:09Z

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.