Skip to content
Noroxi
NVD / CVE Program· CNA VulnCheck

CVE-2026-73621: GitPython before 3.1.56 Arbitrary File Truncation via Commit.count

MediumCVSS 5.3 · v4.0—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: gitpython-developers GitPython 3.1.56.

Low priority for now. Upgrade to gitpython-developers GitPython 3.1.56 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

GitPython before 3.1.56 contains an argument injection vulnerability in the Commit.count() method, which forwards keyword arguments to 'git rev-list' without the check_unsafe_options guard present in the sibling iter_items method. An attacker who can control options passed to Commit.count (e.g., via an application that forwards a user-supplied options dict) can supply output=<path>, causing 'git rev-list --output=<path>' to open and truncate the target file to zero bytes before revision parsing. This allows destruction/blanking of an arbitrary file at the process's privilege level (no content control, 0-byte truncation).

Published
Aug 13, 2026
Updated
Oct 24, 2026
EPSS
0.3% · 30th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · VulnCheck
5.3
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-73621

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for gitpython project records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
gitpython projectgitpython

Versions reported by the vendor

Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.

  • gitpython-developers GitPython

    • 3.1.56not affected
    • before 3.1.56affected · semver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • gitpython project gitpythonbefore 3.1.56

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-gitbefore 3.1.30-1+deb12u33.1.30-1+deb12u3
Debian:13python-gitbefore 3.1.44-1+deb13u13.1.44-1+deb13u1
Debian:14python-gitbefore 3.1.61-13.1.61-1
openSUSE:Leap 16.0python-GitPythonbefore 3.1.44-160000.4.13.1.44-160000.4.1
openSUSE:Tumbleweedpython-GitPythonbefore 3.1.59-2.13.1.59-2.1
PyPIgitpythonbefore 3.1.563.1.56
SUSE:Linux Enterprise Module for Python 3 15 SP7python-GitPythonbefore 3.1.34.1693646983.2a2ae77-150400.9.8.13.1.34.1693646983.2a2ae77-150400.9.8.1

Same product

gitpython project: all records

Other highest-scoring records for the same primary product.

  • CVE-2022-24439Remote Code Execution (RCE)
    41Plan
  • CVE-2026-42284GitPython: Unsafe option check validates multi_options before shlex.split transforms it
    39Monitor
  • CVE-2023-40267GitPython before 3.1.32 does not block insecure non-multi options in clone and clone_from.
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-73619Aug 13, 2026 · GitPython before 3.1.57 Arbitrary File Read via Repo.archive()
    28Monitor
  • ← EarlierCVE-2026-73620Aug 13, 2026 · GitPython before 3.1.57 Arbitrary File Overwrite and Read
    28Monitor
  • Later →CVE-2026-73622Aug 13, 2026 · GitPython before 3.1.55 Environment Variable Exfiltration via Remote.add()
    34Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
gitpython-developers GitPython3.1.56Vendor (CNA)
debian:python-git3.1.30-1+deb12u3 · Debian:12Package registry (OSV)
debian:python-git3.1.44-1+deb13u1 · Debian:13Package registry (OSV)
debian:python-git3.1.61-1 · Debian:14Package registry (OSV)
opensuse:python-GitPython3.1.59-2.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:gitpython3.1.56Package registry (OSV)
suse:python-GitPython3.1.34.1693646983.2a2ae77-150400.9.8.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-4228498 days apartGitPython: Unsafe option check validates multi_options before shlex.split transforms it
    39Monitor
  • CVE-2026-7867612 days apartGitPython before 3.1.59 Remote Code Execution via Config Injection
    37Monitor
  • CVE-2026-762206 days apartGitPython before 3.1.58 Command Execution via split_single_char_options
    34Monitor
  • CVE-2026-762186 days apartGitPython before 3.1.58 Remote Code Execution via Repo.init
    30Monitor
  • CVE-2026-736240 days apartGitPython before 3.1.54 Arbitrary File Overwrite via diff
    28Monitor
  • CVE-2026-762196 days apartGitPython before 3.1.58 Arbitrary File Overwrite via read-tree
    28Monitor

Not on record for this CVE: patch commit or PR link · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records