CVE-2026-76221Public exploitNetwork attack vector

Code execution via option-name injection

Published Aug 19, 2026 · Updated Aug 20, 2026

Config injection in GitPython before 3.1.58 allows attackers to execute arbitrary commands via crafted git-config option names. In git/config.py, _assure_config_name_safe applies section-name checks only to section labels, while write_section writes option names verbatim into the config file, so names containing =, #, or spaces forge directives such as core.sshCommand or core.hooksPath. Reachability requires an application to pass attacker-influenced option names into GitPython's config writer, and code execution occurs on the next Git operation that honors the injected setting.

CVSS severity8.8
High
EPSS probability0.48%
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

Config injection in GitPython before 3.1.58 allows attackers to execute arbitrary commands via crafted git-config option names. In git/config.py, _assure_config_name_safe applies section-name checks only to section labels, while write_section writes option names verbatim into the config file, so names containing =, #, or spaces forge directives such as core.sshCommand or core.hooksPath. Reachability requires an application to pass attacker-influenced option names into GitPython's config writer, and code execution occurs on the next Git operation that honors the injected setting.

The record

CVE
CVE-2026-76221
Published
Aug 19, 2026
Updated
Aug 20, 2026
Vendor
GitPython Developers
Product
GitPython
Classifications
CWE-74, T1059.004
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 19, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 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.58

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitPython Developers · GitPythonversion=0 <3.1.58

Published CVSS scores

8.7VulnCheckCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
8.8VulnCheckCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-74Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
T1059.004Command and Scripting Interpreter Unix Shell

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