Skip to content

Bump GitPython to 3.1.49 to fix CVE-2026-44244#81

Merged
miraladsk merged 1 commit into
mainfrom
osinjoku-patch-1
May 8, 2026
Merged

Bump GitPython to 3.1.49 to fix CVE-2026-44244#81
miraladsk merged 1 commit into
mainfrom
osinjoku-patch-1

Conversation

@osinjoku
Copy link
Copy Markdown
Contributor

@osinjoku osinjoku commented May 7, 2026

Summary

  • Bumps gitpython from 3.1.47 to 3.1.49 in requirements.txt.
  • Pulls in the upstream fix for CVE-2026-44244 (GitPython <=3.1.48).
  • This addresses a config-injection issue in GitConfigParser.set_value() where CR/LF in untrusted values can poison .git/config and set attacker-controlled core.hooksPath.

Security Context

  • Vulnerable versions may allow persistent repository config poisoning when caller-controlled values are passed into config_writer().set_value(...) without sanitization.
  • In affected workflows, this can redirect Git hook execution to attacker-controlled scripts during subsequent Git operations.
  • Upgrading to 3.1.49 removes exposure to this dependency-level issue in this service.

Scope of Change

  • Runtime dependency patch only (requirements.txt).
  • No application logic changes.

Validation

  • Verified diff only changes: gitpython==3.1.47 -> gitpython==3.1.49.
  • Version target matches the patched release published for CVE-2026-44244.

@osinjoku osinjoku changed the title Update requirements.txt Bump GitPython to 3.1.49 for CVE-2026-44244 May 7, 2026
@osinjoku osinjoku changed the title Bump GitPython to 3.1.49 for CVE-2026-44244 Bump GitPython to 3.1.49 to fix CVE-2026-44244 May 7, 2026
@miraladsk miraladsk merged commit 7ffa330 into main May 8, 2026
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants