ZDF
Sign inSign up

Vulnerabilities

Security incident · GHSA-w8jc-g24h-crhw

GitPython command wrappers omit unsafe protocol and option checks

Published Oct 27, 2026 · catalog updated Oct 27, 2026 · GitPython command wrappers omit

Last checked Oct 27, 2026, 10 days ago.

Open the advisory

Exploitation likelihood is not on this record for GHSA-w8jc-g24h-crhw. A missing EPSS score is not a low risk. Compare GitPython command wrappers omit with the linked advisory before you change production.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (GitPython command wrappers omit).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
High7.5
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Version ranges on file
Affected products
pip GitPython

### Summary GitPython has spent 2022-2026 rolling out two reusable guards method-by-method: (raises for remote-helper URLs - CVE-2022-24439) and (raises for denylisted option spellings - CVE-2023-40267, CVE-2026-42215, CVE-2026-67323). Three wrapper methods that build a argv from caller-controlled values still have **neither**: 1. ** ** (git/cmd.py:1128-1143) - checks options (:1139-1141) but forwards the URL positional unchecked; no parameter exists. The same URL through raises . 2. ** ** (git/repo/base.py:895-936) - forwards / to with no guard; guarded sibling sits 12 lines up. Its exception handler additionally swallows every non-128 into , masking the injection. 3. ** ** (git/index/base.py:1092-1168) - forwards to twice (:1147, :1167); guarded sibling is 23 lines above. Verified unfixed on (2026-09-21), post-dating latest release 3.1.62 (2026-09-07) - all three sites re-verified today. ### Impact **Site 1 ( )** - RCE conditional on the victim git transport policy. The common 'probe first, then clone' pattern ( ) with an URL executes arbitrary commands when the victim git permits the ext transport: dynamically verified with (marker executed). git >= 2.38.1 stock config refuses the transport ( , rc 128) - GitPython adds no defense-in-depth and surfaces a bare . Environments on git < 2.38.1 are exposed with stock config - the exact population CVE-2022-24439 was scored against. **Sites 2/3** - latent argument-injection surface: caller kwargs flow 1:1 into the argv before operands and (cmd.py:1850 ), and (incl. / - the CVE-2023-40267 Windows mechanism) passes through unguarded. Today / expose no exec option, so we claim the missing-guard class (vendor-settled by CVE-2026-67323, which bundled archive/ls_remote/iter_commits/blame in one advisory), not direct RCE. ### Dynamic verification (today; GitPython main @ a54d159, git 2.55.0, Linux) | # | Call | Result | |---|---|---| | T1 | , stock config | git refuses (rc 128); **no from GitPython** | | T1b | same + victim con

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • pip GitPython<= 3.1.62

How to fix GHSA-w8jc-g24h-crhw

  • Upgrade

    GHSA-w8jc-g24h-crhw lists a fix boundary at 3.1.62. Compare the installed build with that boundary before you change production.

  • Version check

    Affected <= 3.1.62

  • Official advisories

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for GHSA-w8jc-g24h-crhw. A missing EPSS score is not a low risk. Compare GitPython command wrappers omit with the linked advisory before you change production.

Which versions are affected?

Compare what you have installed with GitPython <= 3.1.62. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-1287. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 27, 2026 · GitHub Advisory Database

    Detected

    ### Summary GitPython has spent 2022-2026 rolling out two reusable guards method-by-method: (raises for remote-helper URLs - CVE-2022-24439) and (raises for denylisted option spellings - CVE-2023-40267, CVE-2026-42215, CVE-2026-67323). Three wrapper methods that build a argv from caller-controlled values still have **neither**: 1. ** ** (git/cmd.py:1128-1143) - checks options (:1139-1141) but forw

  2. Oct 27, 2026 · GitHub Advisory Database

    Updated

    ### Summary GitPython has spent 2022-2026 rolling out two reusable guards method-by-method: (raises for remote-helper URLs - CVE-2022-24439) and (raises for denylisted option spellings - CVE-2023-40267, CVE-2026-42215, CVE-2026-67323). Three wrapper methods that build a argv from caller-controlled values still have **neither**: 1. ** ** (git/cmd.py:1128-1143) - checks options (:1139-1141) but forw

Sources

References

Freshness

Last verified in this catalog Oct 27, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • GitHub Advisory DatabaseOct 27, 2026