p PatchFirst

PatchFirst · Vulnerabilidades recientes

gitpython 3.1.59: vulnerabilidades conocidas

La comparación de gitpython 3.1.59 está incompleta. Revisa las coincidencias confirmadas a continuación.

RSS ↗
Filtrar vulnerabilidades
Borrar filtros

No se pudieron comparar 2 registros. Los resultados están incompletos.

Vulnerabilidades: 5

  1. CVE-2026-114145

    Alta · CVSS 7.5EPSS 0,26%Código de explotación públicoCorrección disponible

    GitPython validates a submodule's ".git" path only after cloning into it (RCE)

    GitPython is a python library used to interact with Git repositories. Prior to 3.2.1, create_submodule() in git/objects/submodule/base.py accepts an attacker-influenced submodule path such as .git/hooks and invokes _clone_repo() before safely rejecting the destination. In 3.1.x, _validate_repo_path() does not exist and the call succeeds silently, while in 3.2.0 and later affected revisions the check in git/index/base.py raises ValueError only after the clone has written to disk and does not remove the planted file. An attacker-controlled submodule can therefore place an executable post-checkout hook that a later Git operation executes. Exploi

    • Actualiza a 3.2.1
    Publicación Actualización
  2. CVE-2026-100689

    Alta · CVSS 8.7EPSS 0,4%Corrección disponible

    GitPython before 3.1.62 Path Traversal via gitmodules path

    GitPython before 3.1.62 does not validate the `path` field read from an untrusted .gitmodules file when updating submodules. While a prior fix (GHSA-hmq2-w58f-27jc) added Submodule._validated_name() to constrain the `name` field, and GitPython's own containment guard Submodule._to_relative_path() is applied in add() and move(), Submodule.update() derives the absolute checkout location from the raw `path` value without that guard. A .gitmodules entry containing directory traversal components (e.g., path = ../../../tmp/escaped) can therefore cause directories to be created via os.makedirs() outside the repository working tree, populated from th

    • Actualiza a 3.1.62
    Publicación Actualización
  3. CVE-2026-87819

    Alta · CVSS 8.7EPSS 0,52%Corrección disponible

    GitPython before 3.1.60 Denial of Service via ReDoS

    GitPython before 3.1.60 contains a regular expression denial of service vulnerability in Actor.name_email_regex that processes commit author and committer fields. Attackers can craft a commit object with a malformed author field containing an unterminated angle bracket to cause quadratic backtracking, exhausting CPU resources for over two minutes per commit access.

    • Actualiza a 3.1.60
    Publicación Actualización
  4. CVE-2026-87818

    Alta · CVSS 7.1EPSS 0,41%Corrección disponible

    GitPython 3.1.59 Local File Content Oracle via --no-index

    GitPython 3.1.59 fails to restrict the --no-index option in the high-level diff API, allowing attackers to read arbitrary filesystem paths as repository operands. Attackers can combine --no-index with -I/--ignore-matching-lines to create a content-dependent Boolean oracle, repeatedly querying local files to recover single-line secrets through distinguishable success or error responses.

    • Actualiza a 3.1.60
    Publicación Actualización
  5. CVE-2026-87817

    Alta · CVSS 8.7EPSS 0,4%Código de explotación públicoCorrección disponible

    GitPython before 3.1.60 Remote Code Execution via Git Directory Impersonation

    GitPython before 3.1.60 fails to properly validate the git directory location, allowing attackers to impersonate the git directory using tracked files like gitdir, commondir, and HEAD. Attackers can execute arbitrary code by placing a malicious pre-commit hook in the tracked hooks directory that executes when a victim calls index.commit() on a cloned or opened repository.

    • Actualiza a 3.1.60
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →