How severe is CVE-2022-24439?

CVE-2022-24439 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-24439?

CVE-2022-24439 affects the following packages: gitpython (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-24439?

Update gitpython to 3.1.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24439 is resolved across your whole dependency graph.

How do I detect CVE-2022-24439 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gitpython, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-24439 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-24439 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-24439, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-24439?

CVE-2022-24439 has an EPSS (Exploit Prediction Scoring System) score of 6.1%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-24439?

CVE-2022-24439 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-24439 published, and has it been updated?

CVE-2022-24439 was published on December 6, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2022-24439 — gitpython

HIGHFix: gitpython-developers/GitPython@2625ed9

CVE-2022-24439 is a high-severity (CVSS 8.1) Improper Input Validation vulnerability in gitpython. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for gitpython — see the affected versions and patch details below.

Remote Code Execution (RCE)

Also known asGHSA-hcpj-qp55-gfphPYSEC-2022-42992

Published

Dec 6, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

6.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍gitpython

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

All versions of package gitpython are vulnerable to Remote Code Execution (RCE) due to improper user input validation, which makes it possible to inject a maliciously crafted remote URL into the clone command. Exploiting this vulnerability is possible because the library makes external calls to git without sufficient sanitization of input arguments.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`gitpython`	all versions	3.1.30`pip install --upgrade 'gitpython==3.1.30'`

Affected Products

3 products · 5 configurations

debian linuxdebian

1 version

10.0

fedorafedoraproject

3 versions

363738

Application

gitpythongitpython_project

< 3.1.30

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

All versions of package gitpython are vulnerable to Remote Code Executio…

security.snyk.ioNVDDec 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gitpython, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update gitpython to 3.1.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-24439 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Across all supported releases of Red Hat OpenStack Platform the usage of a compromised GitPython API (clone_from()) is quite limited. The only people capable of exploiting this vulnerability are system administrators. For this reason, the impact has been downgraded to medium. The impact to Red Hat OpenStack Platform…

Product	Fixed in	Advisory
Red Hat Satellite 6.13 for RHEL 8	`python-gitpython-0:3.1.32-1.el8pc`	RHSA-2023:5931

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-24439 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works