Critical-Severity Flaw in gitpython-developers GitPython Tracked as CVE-2026-110858
A newly published critical vulnerability in gitpython-developers GitPython carries a CVSS score of 9.2. Here is what is affected and how to respond.
Key points
- CVE-2026-110858 affects gitpython-developers GitPython.
- CVSS 9.2 (Critical).
- No exploitation confirmed yet.
A critical security flaw tracked as CVE-2026-110858 has been published in the National Vulnerability Database for gitpython-developers GitPython, with a CVSS base score of 9.2.
At a glance
- CVE
- CVE-2026-110858
- Product
- gitpython-developers GitPython
- CVSS
- 9.2 Critical
- Weakness
- CWE-88
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: GitPython from 3.1.30 before 3.2.0 contains a remote code execution vulnerability in Remote.pull() whose unsafe-option guard inspects only keyword arguments, not the positional refspec. Attackers controlling the refspec can supply --upload-pack=<command> to execute OS commands as the calling process over local-path or SSH transports.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Gitpython-Developers | GitPython | before 3.2.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-110858
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-110858?
CVE-2026-110858 is a CWE-88 vulnerability in gitpython-developers GitPython.
How severe is CVE-2026-110858?
It has a CVSS score of 9.2 Critical.
Is CVE-2026-110858 being exploited?
There is no public confirmation of exploitation at the time of publication.
