How many CVEs have patched check_unsafe_options?

2 published CVEs changed check_unsafe_options in gitpython-developers/GitPython, in 2 distinct patches totalling 48 changed lines, between 2026 and 2026.

What is the latest CVE that changed check_unsafe_options?

CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 980 to 1034 of git/cmd.py.

How does check_unsafe_options compare to the rest of gitpython-developers/GitPython?

gitpython-developers/GitPython has 18 CVEs with a located fix in total; 2 of them changed check_unsafe_options.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Gitpython Developers
Gitpython
Check_unsafe_options

RadicalNotion.AI

We do not sell or share your personal information.

Security Data

CWE Directory
CAPEC Directory
CNA Directory
CNA Leaderboard
CNA Report Cards
Vendor Directory
Patched Functions
Data Sources

Calculators

CVSS Calculator
CVSS 4.0
CVSS 3.1
CVSS 3.0
CVSS 2.0
Badge Builder

Platform

My Vulnerabilities
Insights
Notifications
Pricing

Learn

Guides
What is a CVE?
What is CVSS?
The CISA KEV catalog
What is EPSS?

Company

About
Blog
Careers
Contact
Demo

Account

Legal

Security
Privacy
Terms

RadicalNotion.AI

Security data

Weaknesses (CWE)The MITRE CWE weakness catalog
Attack Patterns (CAPEC)MITRE CAPEC attack patterns
CNAsNumbering authorities and report cards
VendorsVulnerabilities by vendor
Patched FunctionsWhere CVE fixes land in code

Tools

CVSS CalculatorScore CVSS 4.0, 3.1, 3.0 & 2.0
Badge BuilderEmbeddable SVG badges for READMEs

Resources

LearnSecurity guides
Data SourcesCVE data sources

About Blog Pricing Demo

Home
Patched Functions
Gitpython Developers
Gitpython
Check_unsafe_options

check_unsafe_options in gitpython-developers/GitPython: Patched by 2 CVEs

gitpython-developers/GitPython

Function

check_unsafe_options

Name: check_unsafe_options in gitpython-developers/GitPython: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

git/cmd.py

Last patched August 25, 2026

CVEs

That changed this function

Distinct patches

Backports counted once

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

check_unsafe_options in gitpython-developers/GitPython was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 48 lines in total.

gitpython-developers/GitPython has 18 CVEs with a located fix in total, so 11% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed check_unsafe_options, newest first, with the lines each fix touched.

GitPython before 3.1.59 Arbitrary File Read via TagReference.create
CVE-2026-78679 · lines 980–1034 · +5 −3 in 3 hunks
High · CVSS 7.1
EPSS 0.3%2026-08-25
GitPython before 3.1.51 Command Injection via option prefix abbreviation
CVE-2026-67325 · lines 964–1016 · +36 −4 in 3 hunks
High · CVSS 8.7
EPSS 2.2%2026-08-01

Get an alert when the next CVE fix lands in gitpython-developers/GitPython, with the patched functions.

Monitor GitPython CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

1executegit/cmd.py2 CVEs · 3 patches2023 to 2024
2_option_candidatesgit/cmd.py2 CVEs · 2 patches2026
3ls_remotegit/cmd.py2 CVEs · 2 patches2026
4polish_urlgit/cmd.py2 CVEs · 1 patches2026
5dict_to_slots_and__excluded_are_nonegit/cmd.py1 CVEs · 2 patches2024
6handle_process_outputgit/cmd.py1 CVEs · 2 patches2024
7_safer_popen_windowsgit/cmd.py1 CVEs · 2 patches2024
8_unpack_argsgit/cmd.py1 CVEs · 1 patches2026

Other hotspots in the repository

Functions in gitpython-developers/GitPython changed by the most CVE fixes.

_clone4 CVEs · git/repo/base.py execute2 CVEs · git/cmd.py blame_incremental2 CVEs · git/repo/base.py ls_remote2 CVEs · git/cmd.py blame2 CVEs · git/repo/base.py _option_candidates2 CVEs · git/cmd.py

All patched functions in gitpython-developers/GitPython

Frequently asked questions

Common questions about CVE fixes to check_unsafe_options.

How many CVEs have patched check_unsafe_options?: 2 published CVEs changed check_unsafe_options in gitpython-developers/GitPython, in 2 distinct patches totalling 48 changed lines, between 2026 and 2026.
What is the latest CVE that changed check_unsafe_options?: CVE-2026-78679 (GitPython before 3.1.59 Arbitrary File Read via TagReference.create), published 2026-08-25, changed lines 980 to 1034 of git/cmd.py.
How does check_unsafe_options compare to the rest of gitpython-developers/GitPython?: gitpython-developers/GitPython has 18 CVEs with a located fix in total; 2 of them changed check_unsafe_options.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

git/cmd.py on GitHub (opens in a new tab)
All patched functions in gitpython-developers/GitPython
Patched functions directory

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track gitpython-developers/GitPython CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing

On this page

Overview
CVEs that patched it
Other functions in these files
Other hotspots in the repository
FAQ
References