CVE-2023-40267

GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from. NOTE: this issue exists because of an incomplete fix for CVE-2022-24439.

Published: 2023-08-11 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-40267 is rated Moderate Risk (59.4/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.35%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-40267

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-01 0.28% 0.35% +0.07%
2 2026-03-31 0.35% 0.28% -0.07%
3 2025-12-10 — 0.35% —

Full EPSS history (12 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-40267

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]

Weakness enumeration for CVE-2023-40267

GitHub Security Advisory for CVE-2023-40267

GHSA-pr76-5cm5-w9cj · Severity: critical · Ecosystem: pip — GitPython vulnerable to remote code execution due to insufficient sanitization of input arguments

OS Trackers for CVE-2023-40267

vendor priority summary link
alpine — CVE-2023-40267: 1 source package rows (py3-gitpython); 1 state rows across 1 repos (3.18-community); fixed 0, open 1. https://security.alpinelinux.org/vuln/CVE-2023-40267
debian not yet assigned CVE-2023-40267 not yet assigned priority: Debian including 1 source packages (python-git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2023-40267
redhat medium — https://access.redhat.com/security/cve/CVE-2023-40267
suse medium — https://www.suse.com/security/cve/CVE-2023-40267/
ubuntu medium CVE-2023-40267 medium priority: Ubuntu including 1 source packages (python-git), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 6, ignored 3, needs-triage 3. https://ubuntu.com/security/CVE-2023-40267

Affected software / configurations for CVE-2023-40267

Vendor Product Version Raw CPE
gitpython_project gitpython < 3.1.32 cpe:2.3:a:gitpython_project:gitpython:*:*:*:*:*:python:*:*

References for CVE-2023-40267

cvelogic Threat Intelligence