Schwachstellen / CVE-2026-110858

kritisch

CVE-2026-110858

GitPython: GitPython 3.1.30 before 3.2.0 Command Injection via Remote.pull() Refspec

Veröffentlicht Geändert CWE 88
In der Trivy Database seit spätestens 24. Okt. 2026, 07:11 UTCWann der Eintrag vor diesem Build hinzukam, ist nicht erfasst.

Einstufung nach Quelle

Red Hat8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Trivys eigenes Label ist CRITICAL. Kritisch laut Red Hat.

Beschreibung

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.

Betroffene Pakete und behobene Versionen

QuellePaketBehoben in
Red Hatpython-gitpython, python3.12-gitpython, satellite/iop-vmaas-rhel9 und 1 weiterekein Fix angegeben
debian 11python-gitkein Fix angegeben
debian 12python-gitkein Fix angegeben
debian 13python-gitkein Fix angegeben
debian 14python-git3.2.1-1
echopython-git3.2.0
rapidfort debian 12python-git0:3.2.1-1
rapidfort debian 13python-git0:3.2.1-1
seal pip::Seal Security Databasegitpython, seal-gitpython3.1.37+sp999
Alle 13 Einträge aus 9 Quellen zeigen
QuellePaketBehoben in
Red Hatpython-gitpythonkein Fix angegeben
Red Hatpython3.12-gitpythonkein Fix angegeben
Red Hatsatellite/iop-vmaas-rhel9kein Fix angegeben
Red Hatsatellite/iop-vulnerability-engine-rhel9kein Fix angegeben
debian 11python-gitkein Fix angegeben
debian 12python-gitkein Fix angegeben
debian 13python-gitkein Fix angegeben
debian 14python-git3.2.1-1
echopython-git3.2.0
rapidfort debian 12python-git0:3.2.1-1
rapidfort debian 13python-git0:3.2.1-1
seal pip::Seal Security Databasegitpython3.1.37+sp999
seal pip::Seal Security Databaseseal-gitpython3.1.37+sp999

Referenzen

Vulnerability data compiled from the Trivy vulnerability database (trivy-db, Aqua Security, Apache License 2.0), which aggregates third-party advisories. CVE records are published by The MITRE Corporation under the CVE Terms of Use; CVE is a trademark of MITRE. This product uses data from the NVD API but is not endorsed or certified by the NVD. Severity, titles and advisory data from the GitHub Advisory Database (CC BY 4.0), Red Hat security data (CC BY 4.0) and the other sources linked on each entry. Entries may be summarised or re-formatted; the linked original is the authoritative record.