Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-76218 high CVSS 7.5

Vulnerability in GitPython (CVE-2026-76218)

Summary

Vulnerability in GitPython (CVE-2026-76218). Successful exploitation can lead to full system takeover. Exploitable via allow_unsafe_options. Mitigation: upgrade to 3.1.58 or later.

Original description

The description as published by the source.

Summary

Repo.init() forwards **kwargs verbatim to git init with no unsafe-option guard and no allow_unsafe_options parameter. git init --template= copies /hooks/* into the new repo's .git/hooks, so an attacker-controlled template kwarg plants a hook that executes on the next git operation → arbitrary code execution. --template is already recognized as unsafe for clone (it is on unsafe_git_clone_options, and GHSA-6p8h-3wgx-97gf covers the clone path), but Repo.init is a distinct method that never received a guard and needs an independent fix.

Root Cause

Repo.init(path, mkdir, odbt, expand_vars, **kwargs) is a bare git.init(**kwargs) (git/repo/base.py:1435) with no check_unsafe_options and no allow_unsafe_options.

Impact

Arbitrary code execution (hook fires on next git op) at the privileges of the host process. Two preconditions raise attack complexity (AC:H): the app must forward a template= kwarg (KEY control) AND the attacker must stage an executable hook directory at a known path — the same profile GHSA-6p8h-3wgx-97gf accepted as HIGH for the clone path. Default allow_unsafe_options is irrelevant here because Repo.init has no guard at all.

Proof of Concept

# attacker stages /evil/hooks/post-commit (executable)
from git import Repo
Repo.init(path, template="/evil")
# next commit runs /evil/hooks/post-commit -> ACE

Attack Chain

  1. Entry: attacker stages /evil/hooks/post-commit (executable) and gets the app…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-76218 has been found in GitPython.
Attackers can target a specific entry point like allow_unsafe_options over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 7.5/10.
What to do: upgrade GitPython to 3.1.58 or later.
If unsure, ask your IT team or search "GitPython CVE-2026-76218" on the vendor's site.

CVE-2026-76218 (GitPython) — CWE-88 / CVSS v3 7.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: allow_unsafe_options / template / unsafe_git_clone_options / Repo.init
Patched: 3.1.58 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-88) exists in GitPython. Attackers reach the vulnerable code path via allow_unsafe_options.

📍 Affected scope

Check the vendor advisory for the affected versions of GitPython. Attack surface: allow_unsafe_options / template / unsafe_git_clone_options / Repo.init.

🔥 Severity

Severity: High (CVSS 7.5/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.1.58.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'GitPython' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'GitPython' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で GitPython を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade GitPython to 3.1.58

    ステージング環境で 3.1.58 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip GitPython
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.58"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details