CVE-2026-78678Public exploitNetwork attack vector

Arbitrary file read via unblocked blame options

Published Aug 25, 2026 · Updated Aug 25, 2026

Argument injection in Repo.blame() in GitPython before 3.1.59 allows attackers to read arbitrary files from the host system. The revision-option guard checks unsafe_git_revision_options, but its denylist omits --contents and -S, so Git treats an attacker-controlled revision as a file-reading option and returns the selected file's lines in blame results. Exploitation requires a host application to pass a user-influenced revision to Repo.blame() or Repo.blame_incremental(), and disclosure is limited to files readable by that application's process.

CVSS severity6.5
Medium
EPSS probability0.24%
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

Argument injection in Repo.blame() in GitPython before 3.1.59 allows attackers to read arbitrary files from the host system. The revision-option guard checks unsafe_git_revision_options, but its denylist omits --contents and -S, so Git treats an attacker-controlled revision as a file-reading option and returns the selected file's lines in blame results. Exploitation requires a host application to pass a user-influenced revision to Repo.blame() or Repo.blame_incremental(), and disclosure is limited to files readable by that application's process.

The record

CVE
CVE-2026-78678
Published
Aug 25, 2026
Updated
Aug 25, 2026
Vendor
GitPython Developers
Product
GitPython
Classifications
CWE-88, CWE-200, T1005
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 25, 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=0 <3.1.59

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitPython Developers · GitPythonversion=0 <3.1.59

Published CVSS scores

6.5GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
CWE-200Exposure of Sensitive Information to an Unauthorized Actor
T1005Data from Local System

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