CVE-2026-44243Public exploitNetwork attack vector

Arbitrary file modification via unchecked reference paths

Published May 7, 2026 · Updated May 7, 2026

Path traversal in GitPython before 3.1.48 allows attackers to write, overwrite, move, or delete files outside a repository's .git directory. Reference creation, set_reference, rename, and delete APIs join untrusted ref names to repository paths without consistently validating that the resolved path remains within the repository boundary. Exploitation requires a consuming application to pass attacker-controlled ref names, after which files reachable with that process's permissions can be modified or deleted.

CVSS severity7.1
High
EPSS probability0.42%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Path traversal in GitPython before 3.1.48 allows attackers to write, overwrite, move, or delete files outside a repository's .git directory. Reference creation, set_reference, rename, and delete APIs join untrusted ref names to repository paths without consistently validating that the resolved path remains within the repository boundary. Exploitation requires a consuming application to pass attacker-controlled ref names, after which files reachable with that process's permissions can be modified or deleted.

The record

CVE
CVE-2026-44243
Published
May 7, 2026
Updated
May 7, 2026
Vendor
GitPython Developers
Product
GitPython
Classifications
CWE-22, T1565.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 7, 2026CVE publishedPublication date reported by the CVE source.
  2. May 7, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.1.48

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitPython Developers · GitPythonversion=< 3.1.48

Published CVSS scores

7.8GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:P
7.1NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
T1565.001Stored Data Manipulation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo