CVE-2026-78678VulnerabilityPublished 4 Sep 2026Updated 26 Oct 2026

legit · GitPython: Incomplete unsafe_git_revision_options denylist omits --contents/-S, enabling arbitrary file read via

Affects legitSource GCVE Database

Authoritative record:CVE-2026-78678· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 1.2.0.post0_15 soon.

Data as of 26 Oct 2026, 19:12 UTC

CVSS 4.0 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

Patch: Available – fixed in 1.2.0.post0_15

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade legit to 1.2.0.post0_15.

Affected software

Product	Affected	Fixed in
Homebrewlegit`pkg:brew/legit`Other threats	Affected >=0.1.0 <1.2.0.post0_15	Fixed in 1.2.0.post0_15

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in GitPython version 1.2.0.post0_15 that addresses this vulnerability by updating the unsafe git revision options denylist. Users should upgrade to this fixed version or later. Until patched, avoid passing user-influenced revision strings containing options like --contents or -S to the blame methods. The vendor advisory recommends preferring an allowlist approach for blame options or at minimum adding these file-read options to the denylist.

Description

GitPython versions prior to 1.2.0.post0_15 contain a vulnerability in the Repo.blame() and Repo.blame_incremental() methods where an incomplete denylist of unsafe git revision options allows arbitrary local file reads. Specifically, the options --contents and -S, which cause git blame to output the contents of a specified file, are not blocked, enabling an attacker to read arbitrary files on the host system with the privileges of the running process.

Impact

An attacker able to control the revision argument to Repo.blame() or Repo.blame_incremental() can cause the application to read and disclose arbitrary local files with the privileges of the host process. This can lead to sensitive information disclosure, such as reading system files like /etc/passwd. There is no impact on integrity or availability, only confidentiality is affected.

Summary

The vulnerability arises because the denylist for unsafe git revision options in GitPython's blame methods only includes file-write options (--output/-o) but omits file-read options like --contents and -S. When these options are passed as the revision argument, they bypass the unsafe options guard and cause git blame to output the contents of arbitrary files. This leads to an arbitrary file read vulnerability where an attacker-controlled revision string can leak sensitive file contents in the blame output. The issue affects GitPython versions up to 1.2.0.post0_15, where the denylist is present verbatim. The vulnerability is distinct from previous advisories addressing output write options and is analogous to a separate archive read advisory. The recommended fix is to switch from a denylist to an allowlist of blame options or at minimum add --contents and -S to the denylist.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Oct 2026, 19:12 UTC

Technical details

References

Community reviews

Related threats